Add Mesa development process guidelines#3135
Conversation
Expanded CONTRIBUTING.md with detailed information about Mesa's development philosophy, contribution workflow, and best practices for proposing and implementing features. This addition aims to help contributors understand when to open issues, discussions, or PRs, and outlines the stages of problem alignment, design, and implementation.
|
This is extremely helpful, especially the emphasis on problem alignment As a contributor, this makes expectations much clearer and reduces the No missing pieces from my side — this will definitely save time for both |
|
|
||
| ### When to open what | ||
| - **Small enhancements or bug fixes**: Opening an issue or directly a PR is often great. | ||
| - **Larger features or uncertain scope**: Open a [Discussion](https://github.com/mesa/mesa/discussions) first. This helps align on the problem and approach before investing significant effort. |
There was a problem hiding this comment.
In my view issues are a tracker for tickets / TODO items, discussions are for broader exploration where the problem/solution isn’t yet clear
There was a problem hiding this comment.
hmmm, that is not how they are used.
There was a problem hiding this comment.
Before discussing how they are currently used, how do you think they should be used?
Another separation is Issues are for concrete stuff, Discussions for more vague stuff
|
Merging for now, we can always make revisions in the future. |
Expanded CONTRIBUTING.md with detailed information about Mesa's development philosophy, contribution workflow, and best practices for proposing and implementing features. This addition aims to help contributors understand when to open issues, discussions, or PRs, and outlines the stages of problem alignment, design, and implementation.
3 participants
Update: now available at https://github.com/mesa/mesa/blob/main/CONTRIBUTING.md#mesa-development-process
Expanded CONTRIBUTING.md with detailed information about Mesa's development philosophy, contribution workflow, and best practices for proposing and implementing features. This addition aims to help contributors understand when to open issues, discussions, or PRs, and outlines the stages of problem alignment, design, and implementation.
If used correctly, this should save a lot of time and increase the success rate of getting features in Mesa adopted.