Skip to content

Latest commit

 

History

History
28 lines (19 loc) · 4.71 KB

ROADMAP.md

File metadata and controls

28 lines (19 loc) · 4.71 KB

wasmCloud Roadmap and Vision

The wasmCloud roadmap vision is now outlined in our documentation site. Please visit the roadmap page for more information. Additionally, active work in progress and the status of new features is tracked using a GitHub project called wasmCloud Roadmap.

Roadmap Process

wasmCloud roadmaps are planned quarterly (every three calendar months) in the first community meeting of the quarter. If there is a holiday conflict or a majority of maintainers and contributors will be absent from a community meeting, then the roadmap session can be postponed to the following Wednesday. The purpose of the planning session is to review the previous quarter's roadmap for successes and areas of improvement, as well as to plan initiatives for wasmCloud contributors in the following quarter. It is strongly recommended that a wasmCloud organization maintainer leads the roadmapping session as they are responsible for understanding all areas of the project.

The process for wasmCloud quarterly planning starts with one or more wasmCloud Org Maintainers volunteering or being assigned to be the planners. The maintainer should then follow the process below:

  1. Create a GitHub Discussion at https://github.com/wasmCloud/wasmCloud/discussions (e.g. wasmCloud#3813) for community comments, requests and discussion. This should be the primary feedback mechanism for bringing in work for the next quarter. Optionally, if there is a high level goal of a roadmap (e.g. revamp documentation, add support for a new language) communicate that goal in the GitHub discussion.
  2. Schedule the community meeting and set the primary agenda item to be DISCUSSION: wasmCloud QX Roadmap (e.g. https://wasmcloud.com/community/2024/10/02/community-meeting)
  3. Before the community meeting, compile feedback from the GitHub discussion into GitHub issues to track individual action items. Issues should be placed on the wasmCloud Roadmap project with the work stage of Now, applicable roadmap category of Documenatation, New Feature, or Improvement, and the applicable quarter e.g. Q4 2024.
  4. In the wasmCloud Roadmap GitHub project, create a New View that selects each issue from the current quarter, and name the roadmap QX XXXX e.g. Q4 2024.
  5. During the community meeting, review created issues from the discussion. At least 15 minutes of the community meeting should be left available for additional discussion for items that did not make it onto the GitHub discussion.
  6. After the community meeting, finalize the Roadmap by outlining the high level initiatives and the GitHub project on the wasmCloud Roadmap page, which serves as a place that onlookers can see the outcomes of the planning session.

What goes on the Roadmap?

wasmCloud roadmaps are a projection of the communities priorities, requests and feedback. Only issues that are completable in the three month period should go on the roadmap, and if they are longer efforts should be broken down into smaller increments. No issue is too small to go on the wasmCloud roadmap. There is no limit to the amount of tasks that can be put on the roadmap, but each quarterly planning session should review if too much was put on the previous roadmap.

Roadmap features are generally divided into the following categories:

  1. Documentation: Issues that improve documentation either on the website or in READMEs around the project
  2. New Feature: Features that will provide additional functionality in wasmCloud, wasmCloud SDKs or CLIs.
  3. Improvement: Fixes for existing bugs, developer experience rough edges, or rounding out an existing feature

Quarterly roadmaps are not committments to completing all work on the roadmap, but they are indicative of the priorities of the project. Features that are requested from wasmCloud community members and maintainers that are categorizable as good-first-issues (in that they can be completed by developers new to the project) are highly encouraged, as are features that can be completed by the individual proposing them.

If you have any concerns with roadmap planning or the process, please reach out to any of the wasmCloud organization maintainers or send a message in Slack. If you are a wasmCloud maintainer and you'd like to lead a roadmapping session, please reach out to the organization maintainers.