-
Notifications
You must be signed in to change notification settings - Fork 126
Home
Devkit2 is currently in a "Developer Preview" state. There are still many things that need to be implemented/fixed before it can be released, but we wanted to get development on Devkit back out in public as quickly as possible. Please read below for particular areas where we need the most help.
WIP - This will be laid out in more detail later with an overview of the major upcoming development milestones.
For now, the priorities are roughly:
- stabilize the new apis
- make the install process as smooth and user friendly as possible
- update all the documentation
- support future updates
- facilitate easy communication and shared development with the community
- migrate all the devkit1 addons to support devkit2
To facilitate fixing as many issues as possible, we are going to implement some light structure for issue tracking, including a detailed tagging system to help keep things organized. Issues with solid reproductions (platform info, commands, necessary files/code, etc) will be prioritized and 'stale' issues (no repro, no contact from OP or other users) will be closed.
Everyone should contribute to the issue list if they have information - adding extra details, additional reproductions, or just sharing insight is extremely helpful. Additionally, everyone should feel free to help with curating the issue list and submitting patches for them. If you are tackling an issue, consider commenting about your progress so others don't duplicate your effort.
For the moment we are adopting the AngularJS Commit message format as a whole. This will make our commits easy to quickly understand and will allow automatically generating change logs.
NOTE: this will almost certainly be amended/replaced soon
There will be a help wanted page on this wiki that lists particular priorities for the current development cycle. Contributing patches for these topics will be the most effective way to move Devkit2 forward.
The requirements for contributing to Devkit2 are the same as for the original devkit release - please review the information there to sign the necessary CLAs.
We will do our absolute best to review pull requests and get fixes merged in to the current codebase. Pull requests that are concise, well-documented, and relevant to the current development targets are the most likely to get merged in. All commit messages must follow the correct format - see the 'Commit Message Policy' section above for details.