You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some fields missing from the current proposal template, compared to what is specified in the governance document.
Proposal
I suggest a few changes to the proposal template to bring it in line. I also added some clarifying changes based on current practice. I felt the easiest way to visualize the suggested changes was through a pull request, so check it out here: #26. (Is there no way to reference a PR from an Issue? I guess it makes sense...you can do it the other way around.)
The text about posting bugs to the Daemo repo, I believe, was something that had consensus. However, please correct me if I'm wrong. This division does help the Bugs ops team know what they have clearance to work on. Note that if this is accepted, we'll need to change the Daemo repo issue template as well to include the text about submitting security problems via email.
Implications
Short-term: would bring all proposals in official accordance with the governance docs.
Use comments to share your response or use emoji 👍 to show your support. To officially join in, add yourself as an assignee to the proposal. To break consensus, comment using this template. To find out more about this process, read the how-to.
The text was updated successfully, but these errors were encountered:
There are some fields missing from the current proposal template, compared to what is specified in the governance document.
Proposal
I suggest a few changes to the proposal template to bring it in line. I also added some clarifying changes based on current practice. I felt the easiest way to visualize the suggested changes was through a pull request, so check it out here: #26. (Is there no way to reference a PR from an Issue? I guess it makes sense...you can do it the other way around.)
The text about posting bugs to the Daemo repo, I believe, was something that had consensus. However, please correct me if I'm wrong. This division does help the Bugs ops team know what they have clearance to work on. Note that if this is accepted, we'll need to change the Daemo repo issue template as well to include the text about submitting security problems via email.
Implications
Short-term: would bring all proposals in official accordance with the governance docs.
Contact info
@michael Bernstein on Slack
Use comments to share your response or use emoji 👍 to show your support. To officially join in, add yourself as an assignee to the proposal. To break consensus, comment using this template. To find out more about this process, read the how-to.
The text was updated successfully, but these errors were encountered: