Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Mail-Followup-To: apreq-dev@httpd.apache.org
To: apreq-dev@httpd.apache.org
From: Joe Schaefer <joe+gmane@sunstarsys.com>
Subject: Re: Issues with CPAN releases
Date: 23 Jun 2004 09:18:18 -0400
Lines: 31
Message-ID: <877jtypg4l.fsf@gemini.sunstarsys.com>
References: <87brjcv5bk.fsf@gemini.sunstarsys.com>
 <8A67C6CA-C3DF-11D8-856D-000A95972D84@kineticode.com>
 <87wu20gzok.fsf@gemini.sunstarsys.com> <87eko7goln.fsf@gemini.sunstarsys.com>
 <40D940AA.3080809@stason.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mail-Copies-To: never
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Sender: news <news@sea.gmane.org>

Stas Bekman <stas@stason.org> writes:

> Joe Schaefer wrote:

[...]

> > Anybody here have access to the APML account?  I'll try to
> > get in touch with Jim about transferring ownership to APML.
> 
> I think that would be Doug.

Who is the current pmc@ chair for the modperl project?  IMO 
that person should *always* have access to the APML account. 

> CPAN really should move to group accounts,  not only because of perms,
> but also because of confusion that it creates if users go to the
> developer's CPAN dir for the latest release, when someone else has
> done the release. we already take turns to do releases and it's
> confusing. Moreover cpan-testers emails arriving to the person who did
> the release, instead of the list where the group supports the module.

+1, however 99% of CPAN are individually-maintained packages,
so we should take it upon ourselves to reorganize things around 
the ASF.  How about putting a simple LWP script on cvs.apache.org
that automates the PAUSE upload?  We can also ask infra to set up an 
apml unix group and make the script accessible only to those groupmembers
(thus keeping the APML password protected from non-apml users).


-- 
Joe Schaefer