Re: CPAN - making first-come permissions on OpenGuides consistent

2020-08-29 Thread Dominic Hargreaves
On Sat, Aug 29, 2020 at 10:13:17AM +0100, Neil Bowers wrote:
> Hi Dominic,
> 
> Are you happy for me to give Bob Walker first-come permissions on all 
> packages in the OpenGuides distribution?
> 
> If you’d rather keep the first-come permissions yourself, that is fine, and 
> I’ll make that change instead.

I don't really mind either way. Bob is much more involved day to day but I'm
still a stakeholder (and FWIW hold other assets such as the project
domain name - there's probably a different discussion to be had about
that).


If it's a case of wanting to make some change either way for consistency
then feel free to give the permissions to Bob.

Cheers
Dominic


Re: CPAN - making first-come permissions on OpenGuides consistent

2020-08-29 Thread Neil Bowers
Hi Dominic,
> I don't really mind either way. Bob is much more involved day to day but I'm
> still a stakeholder (and FWIW hold other assets such as the project
> domain name - there's probably a different discussion to be had about that).

I’ve just transferred the first-come permissions to Bob.

You now have co-maint permissions on all modules, so you’re still able to do 
releases.

If things change in the future, Bob will now be able to either grant co-maint 
to someone, or transfer the first-come permissions. Until now you would have 
had to coordinate, since you had shared ownership.

Thanks,
Neil


Re: CPAN - making first-come permissions on OpenGuides consistent

2020-08-29 Thread Neil Bowers
Hi Dominic,

Are you happy for me to give Bob Walker first-come permissions on all packages 
in the OpenGuides distribution?

If you’d rather keep the first-come permissions yourself, that is fine, and 
I’ll make that change instead.

Cheers,
Neil


CPAN - making first-come permissions on OpenGuides consistent

2020-08-08 Thread Neil Bowers
Hi Dominic,

I’m one of the PAUSE admins; I’m working on making the ownership (the 
first-come permission) of CPAN distributions consistent. PAUSE tries to do this 
automatically now, but there are historical cases that need a bit of gardening.

You released OpenGuides between 2004 and 2010, and have the first-come 
permission on the lead module (OpenGuides), and most of the other modules. So 
according to policy, you would get first-come on all packages.

But Bob Walker (copied on this email) has done all releases since 2012, 
including this year, so I wonder if it would make more sense to give Bob 
first-come permissions on all packages? You would retain co-maint on all 
packages. This would make it possible for Bob to manage all permissions, for 
example to give other people co-maint, and also to hand it on, should that time 
come.

If you’re happy with this, I can make the changes for you. Is that ok?

Cheers,
Neil