Noel J. Bergman wrote:
Allen Gilliland wrote:
I think it's worthwhile to wonder what exactly we need/expect
to publish on an official ASF site
For $TLP.apache.org, we expect static text that can be maintained (for now)
in source control, and can be mirrored to multiple servers.
http://tomcat.apache.org/
it appears to me that they probably accomplish everything on that site
using plain old static html.
Exactly. But see http://cocoon.zones.apache.org/. Were there similar zones
for Tomcat, Jetspeed, Roller, et al, I might expect to find their services
being displayed.
i don't see any reason why the Roller project page shouldn't follow
that same basic convention and stick with static content to server
up the official ASF project page for Roller.
+1
it seems better to me if we just leave rollerweblogger.org alone
Or move it to roller.zones.apache.org. At some point, we might even like to
use Roller to publish official ASF blogs, e.g., project announcements, press
releases, etc. --- I do want to differentiate that from personal blogs,
since we have established that such won't be happening on ASF
infrastructure.
It definitely makes sense to setup something like
roller.zones.apache.org if we really are going to get other people using
it, but EOLing a domain is so hard that I don't see the benefit to try
and move everything off of rollerweblogger.org. At the very least I
assume dave will still want to keep the blogs currently there in tact.
Is there a reason we couldn't use blogs.apache.org if we were actually
going to user Roller as the ASF blogging site?
-- Allen
--- Noel
