The incubator-general list has pointed out several areas where we should improve our online presence. I will be traveling tomorrow - could folks jump in and help make these adjustments ASAP? (If we can complete them soon and get a green light to put graduation on the Board's Wednesday agenda, then we'll be in a very good position for Wayne and me when presenting Allura at ApacheCon in a few weeks).
See http://markmail.org/message/rghh5epojmgplb2e for my response where I mention all the things I think we can & should change. Can we make all those changes, and then respond on that thread when complete? For our doc hosting, I was thinking we could just configure apache on forge-allura.a.o to serve /p/allura/docs from a static directory instead of sending it through to the allura webapp. Automated publishing of our docs is currently on a SourceForge-internal jenkins job. We should remove that, and set up the current/old docs location to redirect to the new. If time allows automated publishing for the new location could be done as part of the deploy.sh cron job on forge-allura, but that's secondary to actually just moving the docs. I am not sure how to make http://incubator.apache.org/allura redirect. I believe the source is http://svn.apache.org/repos/asf/incubator/allura/site/ but it's using a CMS system. May have to do some research or ask around if there's a way to not use the CMS and redirect. At a minimum I suppose it should be possible to make it the page be nothing but a single link. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
signature.asc
Description: OpenPGP digital signature
