geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan" <>
Subject plugin community site (was Re: [CONSENSUS] Default plugin site)
Date Fri, 25 Aug 2006 21:12:31 GMT
OK this is great feedback.  Until your note I was reacting to Dain's
suggestion from a strictly technical point of view.  I can see now
that his (and your) main concern was to properly associate the
community site with the main project site, which I am definitely in
favor of.

To make this happen we would need to get superadmin privs to an
installation of Joomla 1.0.10 running on Joomla
is open source (GPL) and prereqs Apache HTTP with PHP and MySQL.  So
here is my proposed plan of action:

1.)  Open a request with Apache infra to install Joomla at
2.)  Create a temporary redirect from to
3.)  Publicize the URL (not the one)
4.)  Work with infra to complete the Joomla install
5.)  Migrate the content from to
6.)  Remove the temporary redirect created in step 2
7.)  Take the site offline

Working it this way will allow us to achieve our objectives and
meanwhile continue developing the community site in parallel.  It
strikes me that this approach is very similar to the plan we had for
getting Confluence setup for our project.  Thanks to Hernan's and
Jason's and others' persistence that effort is now a success, which
encourages me.


Best wishes,

On 8/25/06, Jacek Laskowski <> wrote:
> On 8/25/06, Dain Sundstrom <> wrote:
> > If it is intended to run on apache hardware, then why not use
> >
> I don't think it's a requirement to run on ASF hardware, but a natural
> solution - the closer the better.
> All in all, your proposal is the best I've seen lately. Easy to
> remember and noone would think it's hosted outside the project. I like
> it so much that it's going to be profoundly hard to convince me to use
> something else. Thanks Dain!
> Jacek
> --
> Jacek Laskowski

View raw message