Thank you, that is what I wanted to hear!
--
Vlad
> Either approach is acceptable. I think it's really up to your company
> how they want to manage it and whether they want an "official" company
> account or not.
>
> For example, at MongoDB, where I work, I set up a company account and
> have the PAUSE email address go to a mailing list that goes to the
> Perl engineering team. The password credentials are shared among the
> team for redundancy and because we have a high degree of trust.
>
> That sort of casual approach may or may not work for Oracle.
>
> Regards,
> David Golden
> PAUSE Admin for IDs
>
>
> On Mon, Jul 7, 2014 at 10:23 AM, Vladimir Marek
> <vladimir.ma...@oracle.com> wrote:
> > Hi,
> >
> > My name is Vladimir Marek and I work for Oracle Corporation as a
> > sustaining engineer. Recently I started to maintain Perl in Oracle
> > Solaris. In Oracle Solaris we ship several modules (like for example
> > perlgcc) we would like to upload to CPAN or update it if it is already
> > there. I would like to ask whether you would recommend creating a PAUSE
> > "company" account so it would be "invisible" if the maintainer in Oracle
> > changes or should I rather register under my civil name and pass the
> > ownership of "my" modules to anyone working on them later?
> >
> > Thank you
> > --
> > Vlad
>
>
>
> --
> David Golden <x...@xdg.me> Twitter/IRC: @xdg
