Our Triage Process
The Community Engineering team, along with others in Chef engineering, have been working to triage issues that come in on our open source projects.
Part of that process includes identifying and categorizing issues and assigning them to milestones. Those milestones are general targets and do not, repeat, do not mean that they'll be addressed for any particular release. What the milestones do is provide a backlog to work from for those release points. At this time, we've got to three main milestones (the names of which are subject to change). They are "Accepted Major", "Accepted Minor", and "Help Wanted".
The "Accepted Major" milestone is intended for features with breaking changes or with a very large scope.
"Accepted Minor" covers work that we, as Chef Engineering, want to implement or resolve - though PRs from the community for features or bugs with this milestone are welcome and encouraged!
The final milestone is "Help Wanted" which covers bugs or feature requests that we'd like to have implemented in Chef, but fall below the priority level for features or bugs in the previous two milestones.
Features or bugs can move between milestones (especially as feedback is added to existing issues or there are multiple reports or requests for a particular bug or feature).
The "Help Wanted" milestone is where we really want your help. If you have bugs or features you'd like to see that are in this milestone, we are counting on the community to help us deliver these. You can find all the "Help Wanted" milestone issues for the Chef project with a simple search.
We Want Your Help
If you are looking for a place to start getting familiar with the Chef code base, fixing some bugs off that list can definitely be a great start. We've also been tagging issues with a relatively narrow scope or ones that we felt have basic implementations with the "Easy" label. There are a handful of issues that fall into the "Easy" label and "Help Wanted" category.
So, head on over to GitHub, fork the Chef project, and help us out with one of these issues:
- chef daemon mode not recognizing new json_attributes
- cookbook upload fails if there is a brace in the cookbook path
- git resource Errno::EIO on windows
- Chef can't remove apt packages if they don't exist in a repo
- OSX User provider blows up if group is removed before user
- Debian service resource is not idempotent when priority is specified
If you need help getting started, reach out to me or one of the other Community Engineering team on the Chef Developer mailing list or in IRC and we'll do what we can to help you get started. Or stop on in to Chef Developer Office Hours - Monday's and Wednesday's at noon Pacific, 3 PM Eastern.Want more great reading? Check out my reading list!