Ask Bjoern Hansen wrote:
On Wed, 12 Mar 2003, Stas Bekman wrote:


What should we call the repository?  I have Apache::DBI under the
"Apache/"  directory.  Should we just have the others go there too?
That would make sense, no?

Let's call it 'modperl-modules'? 'Apache' could do too, but then we will have things like Apache/Apache/Peek... modperl-modules/Apache/Peek reads better.


No, we would just have Apache/Peek. :-)

Ah, no, it should be Apache-Peek, regardless what the top level dir is. Apache/Apache-Peek or modperl-modules/Apache-Peek. not Apache/Peek as I've suggested before.


Also if some of the modules will have separate lifes for mp1 and mp2. It'll be:

Apache-Peek-1.0
Apache-Peek-2.0

or similar.

We can make an alias so they also can be checked out as
modperl-modules/Apache/*.


However there are a few Doug's modules which aren't strictly mod_perl: GTop
and Sys::Signal (which are looking for a new home), but I guess these can go
into the same dir.


Hmn, that's an argument for making it modperl-modules/*.

Robert and I will consider if we want to make a top level directory
for "CPAN modules" too, I think.  We can make it easy to use with
CVS aliases and groups, so don't worry about that.  :-)

As I pointed out in the reply to Robert (to explain my reasoning):


I've suggested 'modperl-modules', so it'll fit well with repositories from cvs.apache.org's hierarchy, which has modperl, modperl-2.0, modperl-docs.
I'm thinking here about developer's convenience (mine ;). The easiest would be to have it hosted at cvs.apache.org, but as ask correctly pointed out, getting commit access to new people is not simple at all.


__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to