Some changes to DevTools need feedback from the team and community to reach a consensus. In such a case you should use this repository to discuss the change proposal.
The DevTools RFC process aims to be lightweight and focused on conversations. Therefore opening a DevTools RFC is as easy as opening an issue in this repository to discuss the proposal.
The DevTools RFC team will be ultimately responsible for accepting or rejecting a change proposal, but the discussion is open to everybody.
The list of RFCs currently under discussion can be found at: Active RFC List.
Previously reviewed RFCs:
- Create an issue with the "proposal" label
- Get people's attention. Some options:
- Send an email to dev-developer-tools
- Post on Slack or on #devtools at irc.mozilla.org
- mention relevant peers in the issue
- Gather feedback by discussing in the issue
Each week the DevTools RFC team will attempt to review some set of open RFC issues. Reviewed RFCs will also be mentioned in the weekly DevTools team meeting (see archives for devtools-weekly-meetings).
The team will send an email a few days prior to the review meeting to dev-developer-tools to announce which RFCs are likely to be reviewed, and encourage peers to comment if needed.
After a proposal has been discussed and the related issue is ready to be closed, the DevTools core team will label the issue either as accepted or rejected, and will add a comment that summarizes the decision.
If an accepted RFC is actionable, it should have an owner who will represent the feature and its progress. This can be the RFC author, but it's not necessary.