Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Identify approaches to resolve conflicts

未关闭
#11 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
35/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
停滞
领域
content

调研方向

阅读 issue 中链接的冲突解决准备工作,然后选择三种冲突类型中的一种,并根据优先级和有用性对列出的方案和问题进行排序。添加你认为缺失的任何策略,并将最终排序后的列表作为评论发布到你的 planner 中的 issue 上。

由索引模型根据 Issue 内容生成。

描述

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Module-Data-Groups Submit:Issue
Learning Objectives
  • Identify appropriate steps to resolve a conflict
Why are we doing this?

We looked at conflict resolution in the prep work for this week's sprint. How we resolve a conflict will often depend on what the conflict is about. Consider the following types of conflict and choose one.

  • A technical disagreement about how to write the code for a well-understood task.
  • The manager wants you to work faster but with a smaller team by rushing.
  • A competitive and ambitious person wants you to look bad so they can get a promotion instead.

Sort the following list of approaches or questions into priority and usefulness. Add your own strategies to this list.

  • Don’t let your emotions control you.
  • Paraphrase what the other person said, confirming your understanding and showing empathy.
  • Each conflict is an opportunity.
  • Find out what facts the other person knows.
  • What do they want? Relatively few people have hidden agendas.
  • What do you want? Assert your points clearly without being too shy.
  • What is their general attitude and approach?
  • What possible solutions to this conflict might exist?
  • Agree on part of the solution if you can’t agree on all of it.
  • Build a network of people to support your resilience and perhaps mediate the conflict.
  • Communicate clearly before there is a conflict.
  • Be assertive enough to make your point.
  • Escalate the topic to someone more senior to arbitrate.
  • Keep away from the other person and find your own solution without them.
  • … add your own strategies.
Maximum time in hours

0.5

Submission & Review
  • Add your final order on a comment on this issue in your planner
主要语言
JavaScript
星标
1
派生
327
平均合并
3 天 7 小时
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CodeYourFuture/Module-Data-Groups 的其他 Issue

查看 CodeYourFuture/Module-Data-Groups 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。