Justin Erenkrantz wrote:
On 2/10/06, Gregory (Grisha) Trubetskoy <[EMAIL PROTECTED]> wrote:
We could ask again, but last time the answer was no, and I tend to agree.
But I also understand that we have Solaris servers on which zones can be
created where we could run our own httpd.
httpd.zones.apache.org is available (someone on the httpd PMC will
have access). The standard *.apache.org setup is to have an almost
entirely static site that can be easily replicated to our backups
without the need for dynamic setups. Therefore, dynamic sites or
examples should run in a zone.
So we would have our own httpd instance in the zone, right?
But it always comes back to the same point - running a nice website takes
a lot of time and effort (possibly more than it takes to actually develop
mod_python), and until there is someone ready to create and maintain
content and run the site and the code on it, there is no point in going
there.
I would recommend piggy-backing off httpd.apache.org's site design as
much as possible for the 'here's the latest release of MP', 'where to
download MP', 'MP mailing lists', etc, etc. You can have a much more
complex and 'dogfood example' site off the zone - but that should only
be in 'support' of the basic materials available off httpd.apache.org.
Emulating the httpd.apache.org design would be my personal preference. I
like the idea of being consistent with our the parent httpd project,
plus it's a nice simple layout.
I'll spend a little time knocking up a test page this weekend.
Jim
