On Wed, Jul 13, 2022 at 11:54:03AM +0200, Simon Josefsson via Gnulib discussion list wrote: > Bruno Haible <br...@clisp.org> writes: > > > Therefore I would now like to actually do it. > > Thanks for working on this, it is important! > > Maybe I am getting old, but one year seems like a fairly short period of > time. The list would be shortened with the following names if we used > two years: > > Daiki Ueno > Dmitry V. Levin > Eric Blake > Siddhesh Poyarekar > > So not radically different actually. It would be bad if this excercise > lead to less contributions. > > How about using the one-year time frame, but give the person 6 months of > time after an email notifying them about this situation to make another > contribution and thus stay as committer?
Looks like it has been a while since I pushed something into gnulib, but with this sort of 6-month notice, I'd definitely find reason for something ;) Meanwhile, I'm on board with the idea of pruning the list of write access to frequent contributors (even if I temporarily fail to meet that standard). It doesn't seem onerous to re-establish permissions if my situation changes to make it easier for me to contribute more direct patches again. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org