-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC 0071] Retired Committers Amendment #71
Conversation
Meta topic: Albeit
in my experience it would be better to directly amend. git keeps the audit logs anyway. |
Bikeshedding mode: past or former both sound better to me than retired. Retired makes me thinks of retirees, i.e. old people who stopped working. |
The README already states:
This might be sitting firmly on the fence of "substantial change". The original RFC being relatively thin in contents (and rightly so), this does change what is definitely arguably a portion of it. This is probably a situation where when there is doubt, prefer sending an RFC so the full process can be followed. ¯\_(ツ)_/¯ |
A nice thing that @grahamc mentioned was that neither of those can have an honor designation like the former word emiritus. An example is someone returning from retirement, and they're an esteemed person. |
This RFC is now open for shepherd nominations. I nominate myself. |
I'm not particularly attached to the team name of #55, and this RFC sounds sensible to me. |
I'd also want to nominate the author of the RFC this amends @tilpner,
and I guess @alyssais. You can probably tell that the time commitment
for this one is super low, you really could comment a yes/no 😁
Nomination accepted. FWIW: I think trying to follow Latin grammer rules
in English is silly -- there's a reason we don't say "octopodes",
following the rules for the original Greek -- but the accessible English
point stands.
I'm in favour of accepting the RFC.
|
We've accepted the nominations for shepherds @lheckemann @tilpner @alyssais, and our leader is @tilpner. |
Everyone has already pre-approved on this RFC. Perhaps the shepherds can comment we could move to FCP? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, please go ahead to FCP. |
Cool, motion for FCP with a disposition to merge. |
Co-authored-by: Jörg Thalheim <[email protected]>
Rendered