WoW: Goals and refinement process

Owned by Sander Jansen
Last updated: Mar 11, 2024 by Catalina Dumbraveanu (Deactivated)
2 min read

DRAFT

This page describes the process of establishing clear goals and agreeing on these open source community goals, as an open source community, on the steps and the way we collaborate to achieve the community goals.
Goals can be both collective and individual, for everyone to be in sync with what is going on in the community.

Collective goals will be refined with the group and there will be an alignment on how the collaboration will happen, according to the steps below.
For individual goals the group will be informed of the scope and progress, and consulted about the technical solution, if needed.


1. Make sure we have clear goals and everyone in the open source community knows what we (the open source community) are working on.

  • last week of each quarter the refinement sessions are used to inspect what was achieved in the quarter that is ending and to discuss the goals for the quarter that is about to start
  • goals need to be clear & measurable (clear acceptance criteria to prevent confusion)
  • goals will be tracked using the Roadmap: Planned Features · Roadmap (github.com)
  • each goal will be discussed by the relevant community members, and broken down into high level steps; tasks can be created/linked under the goal
  • availability of the community members will be shared, and an agreement will be made on how the members will collaborate to achieve the goals

2. Refine the tasks needed to acheive the goals

  • during each refinement session the community members look at the goals and align on the next tasks to be worked on
  • technical solution is discussed
  • in case of disagreements regarding the technical approach, a discussion will be created, as described at point 3. below

3. Discussions & decisions

  • discussions can take place in the github tickets, or a separate discussion can be created, if needed, and linked to the ticket that triggered it
  • questions, remarks, risks can be shared by anyone
  • maintainers will make a decision, considering all the input, and the decision will be communicated under the task/discussion
  • when the maintainers cannot come to an agreement, the possible approaches will be shared in the TSC, where a decision will be made