Re: Perl Modules in GitHub

[Jerry D. Hedden]

That just what I'm looking for, Leon.  Would you please add me to that
organization (jdhedden) so that I can add the dual-life modules I have to
it?  Thanks.

On Tue, Mar 29, 2016 at 10:07 AM, Leon Timmermans  wrote:

> On Tue, Mar 29, 2016 at 5:21 AM, Jerry D. Hedden 
> wrote:
>
>> I maintain server Perl modules on CPAN:
>> http://search.cpan.org/~jdhedden/  Some of the modules are part of the
>> core Perl distribution; some are my own.  I want to add them to GitHub.  Is
>> there preferred organization, account, methodology for doing this?  I would
>> think there is a better way than just putting them under my own GitHub
>> account, particularly as this would complicate matters if the time should
>> come when someone else would need to take over their maintenance.
>>
>
> AFAIK the perl group is not meant as a community development platform
> (most obviously perl/perl is only a mirror), but more as communication to
> the outside world The Perl Toolchain gang is quite functional at what it's
> trying to do, but I don't think think that enlarging that umbrella is a
> good idea organizationally. I do think it may be a good idea to have an
> organization for non-toolchain dual-life modules (in fact, I just took the
> liberty of creating exactly such an organization).
>
> Leon
>
>

Re: Perl Modules in GitHub

[Aristotle Pagaltzis]

Hi Jerry,

* Jerry D. Hedden  [2016-03-29 05:25]:
> Is there preferred organization, account, methodology for doing this?

not really.

> I would think there is a better way than just putting them under my
> own GitHub account,

The current situation is the same as with all other parts of the Perl
ecosystem: whatever worked for whoever showed up to do the work. With
the vast majority of CPAN modules that live on GitHub, that means they
live under their maintainer’s personal account.

Some CPAN authors have set up personal GitHub Organisations to put their
modules into so they can hand out admin access.

You can hand out commit bits to repos in your personal account to other
GitHub users, mind.

AFAIUI the diffference with a GitHub Org is that you can also hand out
administrative access to its repos (and the org itself) at the GitHub
level.

That’s why the Perl Toolchain Gang org exists, as mentioned by BooK.

> particularly as this would complicate matters if the time should come
> when someone else would need to take over their maintenance.

The history of the project can be grabbed by anyone, that is the whole
point of using a DVCS after all.

The only real issue is bug tracking, because it is usually centralised.

If you use GitHub Issues to manage tickets, then the bug tracker cannot
be taken over by a new maintainer without action on your part. (You can
move the repository from your account to another, which will carry over
its issues (and wiki content, if you use that). That will require your
active participation.)

If you use RT.cpan, the PAUSE admins can reassign permissions, so that
takeovers can happen without your involvement. You can turn off GitHub
Issues in a repository if you wish issues to be reported otherwise. But
note that you cannot turn off pull requests at the time of this writing.

So in practice modules maintained under a personal account are not that
problematic. The only serious problem is in case the maintainer got run
over by a bus and nobody else can log into their GitHub account.

Regards,
-- 
Aristotle Pagaltzis // 

Re: Perl Modules in GitHub

[Leon Timmermans]

On Tue, Mar 29, 2016 at 5:21 AM, Jerry D. Hedden  wrote:

> I maintain server Perl modules on CPAN:
> http://search.cpan.org/~jdhedden/  Some of the modules are part of the
> core Perl distribution; some are my own.  I want to add them to GitHub.  Is
> there preferred organization, account, methodology for doing this?  I would
> think there is a better way than just putting them under my own GitHub
> account, particularly as this would complicate matters if the time should
> come when someone else would need to take over their maintenance.
>

AFAIK the perl group is not meant as a community development platform (most
obviously perl/perl is only a mirror), but more as communication to the
outside world The Perl Toolchain gang is quite functional at what it's
trying to do, but I don't think think that enlarging that umbrella is a
good idea organizationally. I do think it may be a good idea to have an
organization for non-toolchain dual-life modules (in fact, I just took the
liberty of creating exactly such an organization).

Leon

Re: Perl Modules in GitHub

[Philippe Bruhat (BooK)]

On Mon, Mar 28, 2016 at 11:46:32PM -0500, Dave Rolsky wrote:
> On Mon, 28 Mar 2016, Jerry D. Hedden wrote:
> 
> >Okay, I see that GitHub allows me to create organizations which I presume is 
> >what you're referring to as groups.
> >Are there existing organizations for which adding the core Perl Modules 
> >(threads, threads::shared, etc.) would be appropriate?
> 
> There's this one - https://github.com/Perl
> 
> I'm not sure who controls it, but it looks official-ish. It might be nice to
> have a central Perl organization on GitHub. It could make it easier to share
> ownership of modules.

Depending on the modules, there's also https://github.com/Perl-Toolchain-Gang

-- 
 Philippe Bruhat (BooK)

 Even when the words are true, they may not speak the truth.
(Moral from Groo The Wanderer #70 (Epic))

Re: Perl Modules in GitHub

[Dave Rolsky]

On Mon, 28 Mar 2016, Jerry D. Hedden wrote:


Okay, I see that GitHub allows me to create organizations which I presume is 
what you're referring to as groups.
Are there existing organizations for which adding the core Perl Modules 
(threads, threads::shared, etc.) would be appropriate?


There's this one - https://github.com/Perl

I'm not sure who controls it, but it looks official-ish. It might be nice 
to have a central Perl organization on GitHub. It could make it easier to 
share ownership of modules.



Cheers,

-dave

/*
http://VegGuide.org   http://blog.urth.org
Your guide to all that's veg  House Absolute(ly Pointless)
*/

Re: Perl Modules in GitHub

[Dean Hamstead]

My bad on terminology. 

Dean 

On 2016-03-29 14:30, Jerry D. Hedden wrote:

> Okay, I see that GitHub allows me to create organizations which I presume is 
> what you're referring to as groups. 
> 
> Are there existing organizations for which adding the core Perl Modules 
> (threads, threads::shared, etc.) would be appropriate? 
> 
> On Mon, Mar 28, 2016 at 11:23 PM, Dean Hamstead  wrote:
> 
> Github allows you to create "groups" which can own modules. 
> 
> You can then add people to those groups as you see fit. 
> 
> Dean
> 
> On 2016-03-29 14:21, Jerry D. Hedden wrote: 
> I maintain server Perl modules on CPAN:   http://search.cpan.org/~jdhedden/  
> Some of the modules are part of the core Perl distribution; some are my own.  
> I want to add them to GitHub.  Is there preferred organization, account, 
> methodology for doing this?  I would think there is a better way than just 
> putting them under my own GitHub account, particularly as this would 
> complicate matters if the time should come when someone else would need to 
> take over their maintenance.
 

Re: Perl Modules in GitHub

[Jerry D. Hedden]

Okay, I see that GitHub allows me to create organizations which I presume
is what you're referring to as groups.

Are there existing organizations for which adding the core Perl Modules
(threads, threads::shared, etc.) would be appropriate?


On Mon, Mar 28, 2016 at 11:23 PM, Dean Hamstead 
wrote:

> Github allows you to create "groups" which can own modules.
>
> You can then add people to those groups as you see fit.
>
>
>
>
>
> Dean
>
>
>
>
> On 2016-03-29 14:21, Jerry D. Hedden wrote:
>
> I maintain server Perl modules on CPAN:
> http://search.cpan.org/~jdhedden/  Some of the modules are part of the
> core Perl distribution; some are my own.  I want to add them to GitHub.  Is
> there preferred organization, account, methodology for doing this?  I would
> think there is a better way than just putting them under my own GitHub
> account, particularly as this would complicate matters if the time should
> come when someone else would need to take over their maintenance.
>
>

Re: Perl Modules in GitHub

[Dean Hamstead]

Github allows you to create "groups" which can own modules. 

You can then add people to those groups as you see fit. 

Dean

On 2016-03-29 14:21, Jerry D. Hedden wrote:

> I maintain server Perl modules on CPAN:   http://search.cpan.org/~jdhedden/  
> Some of the modules are part of the core Perl distribution; some are my own.  
> I want to add them to GitHub.  Is there preferred organization, account, 
> methodology for doing this?  I would think there is a better way than just 
> putting them under my own GitHub account, particularly as this would 
> complicate matters if the time should come when someone else would need to 
> take over their maintenance.
 

Perl Modules in GitHub

[Jerry D. Hedden]

I maintain server Perl modules on CPAN:   http://search.cpan.org/~jdhedden/
 Some of the modules are part of the core Perl distribution; some are my
own.  I want to add them to GitHub.  Is there preferred organization,
account, methodology for doing this?  I would think there is a better way
than just putting them under my own GitHub account, particularly as this
would complicate matters if the time should come when someone else would
need to take over their maintenance.