Habari + Apache
Chris J. Davis
To get this done, there are a couple of features that need to be added to the system, as plugins.
1. Take this list and make a wiki entry from it!
2 . output html of every page in the system
3. Preserve the URLs that are in use currently on this site -- This includes file downloads that live at places like /foo/foundation/pdf.pdf
It is a short list, but an important one I think. Anyone can throw in, in whatever way they can. This will be a code sprint like none we have done before, since getting Apache.org running on our software will be a validation of all the work you the community have done, as well as a ringing validation of our community model.
Whatever happens, I think it is pretty amazing that the ASF is looking to us to help run the most important site they have. I am extremely proud of what we have accomplished over the last 3 years!
We still need to think about how long the code sprint should last, etc but right now I think we need to gauge interest and passion from the community, which means you!
Chris
chrisjdavis
Apache will be using Habari to create and manage the content, not
serve it. It will be exported as static flat html files and served
that way. I have some ideas on how this could work, so when we have
someone with some energy to help out with it, we'll talk.
Rich Bowen
In the specific case, there's two reasons:
1) It's because the Apache website exists in a mirror network and so
it's useful to have something static that you can rsync around.
2) It's because the ASF lives and dies by subversion, and there needs
to be a workflow whereby versions can be put in svn and diffed and
reverted, and all that good stuff.
In the general case, much greater scalability can be achieved by
exporting static content and serving that, rather than having to hit
the database thousands of times per second for content that only
changes, at best, a few times a day.
On Nov 6, 2009, at 15:40 , chrisjdavis wrote:
> Someone asked on IRC for more info about the static export.
>
> Apache will be using Habari to create and manage the content, not
> serve it. It will be exported as static flat html files and served
> that way. I have some ideas on how this could work, so when we have
> someone with some energy to help out with it, we'll talk.
--
Rich Bowen
rbo...@rcbowen.com
Michael C. Harris
> The ASF is looking for a CMS to move the www site and our hat has been
> thrown into the ring.
[snip]
> We still need to think about how long the code sprint should last, etc but
> right now I think we need to gauge interest and passion from the community,
> which means you!
Sounds interesting, if it happens, I'd definitely try to turn up and help.
--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari
rick c
the implementation would result in some handy features for Habari.
I'd be willing to help out.
Rick
djeckhart
I've been lurking at the fringes of the project for a while, and I
think it's time to join the fray. I'd be glad to help in whatever way
I can.
Michael C. Harris
> I've been lurking at the fringes of the project for a while, and I
> think it's time to join the fray. I'd be glad to help in whatever way
> I can.