mirror of
https://github.com/NixOS/rfcs.git
synced 2025-11-08 19:46:12 +01:00
First stab at defining the buddy responsibilities
This commit is contained in:
parent
254918a364
commit
08b081acec
1 changed files with 9 additions and 0 deletions
|
|
@ -94,6 +94,15 @@ rubber stamp, and in particular still does not mean the feature will
|
||||||
ultimately be merged; it does mean that in principle all the major
|
ultimately be merged; it does mean that in principle all the major
|
||||||
stakeholders have agreed to the feature and are amenable to merging it.
|
stakeholders have agreed to the feature and are amenable to merging it.
|
||||||
|
|
||||||
|
### Role of the "buddy"
|
||||||
|
|
||||||
|
To goal for assigning a "buddy" to the RFC is multifold. The main
|
||||||
|
responsability is to make himself available for to the author to move the RFC
|
||||||
|
along. It means keep a closer connection with him, talk and help resolve
|
||||||
|
ongoing issues and add credence to the proposal. The buddy doesn't necessarily
|
||||||
|
have to agree with all the points of the RFC but should generally be satisfied
|
||||||
|
that the proposed additions are a good thing for the community.
|
||||||
|
|
||||||
# Drawbacks
|
# Drawbacks
|
||||||
[drawbacks]: #drawbacks
|
[drawbacks]: #drawbacks
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue