Gregory (Grisha) Trubetskoy wrote:
>
> I'll see about devoting some time to this in the near future - we need
> to solve the site issue...

I have no problem doing the site maintenance. We just need to make a
decision on the infrastructure. Here are the issues as I see them, with
possible alternative solutions.

1. Content repository
a. In our current repository:
/httpd/mod_python/site/whatever
b. Under the apache /httpd/site repository:
/httpd/site/trunk/lib/mod_python
(This would require mod_python committers getting commit
privileges for /httpd/site).

2. Website
a. http://www.modpython.org
(We'd need a mechanism to update the site from the repository.
This could be as simple as a cron job on modpython.org to grab the
current content from the svn repository once a day).
b. httpd://httpd.apache.org/mod_python
(If we use the /httpd/site repository and build infrastructure,
the website gets updated automatically).

c. Other? Perhaps modpython.apache.org?


3. Site design
a. httpd.apache.org design (and tools)
b. Current modpython.org design
c. All new design.

4. Online html-docs
a. www.modpython.org
b. httpd.apache.org

5. Location of the faq, which is dynamic content and cannot be
accomodated under http://httpd.apache.org.
a. modpython.org
b. other?

6. mod_python@modpython.org mailing list archive
a. modpython.org/pipermail
b. other location?


I'd suggest we leave 4, 5 and 6 as is, since that infrastructure is in
place and works. What we need is a way to keep have website content in
subversion, and a mechanism for updating the host.

Jim

> Grisha
>
>
> On Sat, 18 Mar 2006, Justin Erenkrantz wrote:
> 
>

[ Post a follow-up to this message ]