I concur (which I think may be unnecessary, but want to make clear we are not m the same page).
Mike On Mon, Aug 17, 2020 at 6:34 PM Yo-An Lin <yoanli...@gmail.com> wrote: > Hi Neil, > > I think you can give MSOUTH the permissions. I guess I have one time ever > uploaded these modules but I deleted them eventually. > > Thanks, > Yoan > > Neil Bowers <neil.bow...@cogendo.com>於 2020年8月17日 週一，23:07寫道： > >> >> >> >> >> >> >> >> >> >> >> >> >> Hi Mike and Yo-An, >> >> >> >> >> >> I’m one of the PAUSE admins. I’m tidying up distributions that have >> shared first-come ownership, since PAUSE tries now to not let this happen — >> it maintains the permissions profile on the lead module, regardless of who >> releases (in the past the releaser would get first-come on newly added >> modules). >> >> >> >> >> >> The Git distribution is one of these. Mike (MSOUTH) has the first-come >> permission on 12 modules in the distribution, and Yo-An (YOANLIN) has >> first-come on the other three, including the lead module, "Git". >> >> >> >> >> >> All releases of "Git" have been done by MSOUTH, so I’m not sure how >> YOANLIN ended up with first-come permissions on 3 of the modules, but >> doesn’t even have co-maint on the rest. Maybe YOANLIN was going to adopt >> the distribution, but didn’t get all the permissions. >> >> >> >> >> >> Who should I give all first-come permissions to? Looking at the history, >> I would guess MSOUTH, but thought I should check, since YOANLIN has >> first-come on the "Git" module itself. >> >> >> >> >> >> Cheers, >> >> >> Neil >> >> >> >> >> >> PS I’ve bcc’d Yo-An, since the YOANLIN account has the flag set to keep >> the email address secret. >> >> >> >> >> >> >> >> >> > >
