I'll throw in a free copy of PDL-2.008...

If I can't get an admin fix, I would like to request ownership of
PDL::Slatec from a non-responsive owner.

--Chris

On Tue, Jan 20, 2015 at 5:15 PM, Chris Marshall <devel.chm...@gmail.com>
wrote:

> ...bump...
>
> Releasing another PDL developers release on the way to PDL-2.008.
> Still need help from PAUSE admins to make me a co-maintainer on
> PDL::Slatec.
>
> Thanks,
> Chris Marshall (PDL-2.008 Release Manager)
>
> On 1/12/15, David Golden <x...@xdg.me> wrote:
> > It's sort of secret knowledge among Perl toolchain maintainers.
> > "x_authority" is a custom CPAN META key, but PAUSE now respects it (and
> has
> > for a couple years, I think).
> >
> > Google found this blog post about it:
> > https://jawnsy.wordpress.com/2011/02/20/what-is-x_authority/
> >
> > And I opened a ticket about it, too:
> > https://github.com/andk/pause/issues/140
> >
> > David
> >
> >
> > On Mon, Jan 12, 2015 at 10:49 AM, Chris Marshall <devel.chm...@gmail.com
> >
> > wrote:
> >
> >> Thanks for the tip, David.  The current PDL permissions has been around
> >> for a long time (and seemed good at the time).  It would be nice to have
> >> this cleaned up and made more sane.  Do you have some refs/docs for this
> >> including which versions of perl might be supported...
> >>
> >> --Chris
> >>
> >>
> >> On Mon, Jan 12, 2015 at 10:37 AM, David Golden <x...@xdg.me> wrote:
> >>
> >>> FYI, a strategy that works well for bigger team projects is to assign
> >>> primary permissions to one ID, and then add an "x_authority" field to
> >>> META.json like "cpan:YOURIDHERE".  When PAUSE sees that field, it makes
> >>> any
> >>> *new* modules get primary permissions assigned to that ID and existing
> >>> comaintainers get added as comaintainers of the new module.  It helps
> >>> avoid
> >>> fragmenting the primary ownership over time if different maintainers
> are
> >>> involved in releasing.
> >>>
> >>> David
> >>>
> >>>
> >>> On Sun, Jan 11, 2015 at 11:00 AM, Chris Marshall
> >>> <devel.chm...@gmail.com>
> >>> wrote:
> >>>
> >>>> We're preparing for a PDL-2.008 release this month.  Our current
> >>>> developers release shows that in assigning permissions for PDL release
> >>>> to me (the current PDL release manager) we missed a couple.
> PDL::Slatec
> >>>> is owned by the pseudo author PERLDL.  Would one of the PAUSE admins
> >>>> please add me (CHM) as a co-maintainer of PDL::Slatec so that our
> releases are
> >>>> no longer UNAUTHORIZED?
> >>>>
> >>>> Thanks in advance,
> >>>> Chris
>

Reply via email to