nixos/rfcs
1
0
Fork 0
mirror of https://github.com/NixOS/rfcs.git synced 2025-12-20 07:51:18 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clarify the role of the co-author

Browse source
This commit is contained in:
zimbatm 2017-03-05 20:37:06 +00:00
parent d70b98a9b1
commit 3972bd9064
1 changed files with 12 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

19
rfcs/0000-rfc-process.md
View file

@ -88,14 +88,19 @@ 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 "co-author" ## Role of the "co-author"
To goal for assigning a "co-author" to the RFC is multifold. The main To goal for assigning a "co-author" is to help move the RFC along.
responsability is to make themselves available for to the author to move the RFC
along. It means keep a closer connection with them, talk and help resolve The co-author should:
ongoing issues and add credence to the proposal. The co-author doesn't necessarily * be available for discussion with the main author
have to agree with all the points of the RFC but should generally be satisfied * respond to inquiries in a timely manner
that the proposed additions are a good thing for the community. * help with fixing minor issues like typos so community discussion can stay
on design issues
The co-author 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