Move inactive maintainers to emeritus status #43
Conversation
The TOC approved a requirement that maintainers that have not been active in over three to six months be move to emeritus status. These maintainers have not been active in over one year. hyperledger/toc#32 Signed-off-by: Ry Jones <[email protected]>
ryjones
requested review from
awrichar,
shorsher,
nguyer and
peterbroadhurst
as code owners
|
Hey @ryjones. I understand the idea behind the new policy. What changes with the "emeritus status" though? Is the maintainer still able to approve and merge code? Also, does this policy apply at the repo level or the project level? Alex has been very active in other parts of the project. This particular repo just hasn't had a lot of activity in it in general. In fact, it hasn't had a commit in the last six months. So if we're applying the new rule at the repo level, I guess all the maintainers would now be emeritus? If it's at the project level, Alex is still very active and I don't think his status should be changed. |
|
Hi @nguyer - in that case it would be better to have a single maintainers file in the main repo, with the other repos pointing to it. Here is an example. |
|
Sounds good. I have some FireFly repo "housekeeping" like this on my list to do at some point, and I will do that at the same time. |
|
@nguyer I didn't answer your first question. Emeritus maintainers are no longer able to vote in the TOC election, or merge code. |
The TOC approved a requirement that maintainers
that have not been active in over three to six
months be move to emeritus status.
These maintainers have not been active in over
one year.
hyperledger/toc#32
Signed-off-by: Ry Jones [email protected]