Hi everyone, I am late on this subject for a number of personal reasons, however I'd like to present the PMC with this plan to migrate tiles web site to svnpubsub.
We must take into account the deadline of Dec 31st, all necessary migration requests for be filed at infra before that date. Then we must publish using svnpubsub. We should also automate that publication by using the maven svnpubsub plugin, although the automation aspect is not actually a blocker at Dec 31st. ======== Analysis ======== There are actually two websites that we should migrate to svnpubsub: 1. the distribution website at http://www.apache.org/dist/tiles/. 2. the maven website at http://tiles.apache.org/ (which includes 4 parts, tiles-site, tiles-autotag, tiles-request and tiles-parent); Concerning 1., I've already committed the currently distributed files to https://dist.apache.org/repos/dist/release/tiles on Dec 3. We just need to file the request for infra to take it into account and get the mailer config set up, as Daniel Shahaf pointed out. Concerning 2., we need to host the website itself in one or several parts inside our svn tree at http://svn.apache.org/repos/asf/tiles/. Then we file a request for infra to map the selected subdirectories to the web. So we need to decide on the layout of the website in SVN. I've been reviewing where other projects have hosted their site. The most common location seems to be site/publish (myfaces, avro, cassandra), other choices include site(couchdb), site/site(cocoon), site/trunk/docs(tomcat), infra/websites/production/camel/content(camel)... Of special interest to us is the umbrella TLP Ant, which is hosting ant at site/ant/production, ivy at site/ivy/production, ivyde at site/ivyde/production. So the most popular choice is to host the production website somewhere in the site subdirectory. Otherwise everyone is doing it differently. This is a complication to us because the site directory is already hosting our "main" website. Then we also have to consider updating our release process (http://tiles.apache.org/framework/dev/release.html). We're currently using the following spaces: - for staging distribution artefacts: /www/people.apache.org/builds/tiles/ - for distributing artefacts: /www/www.apache.org/dist/tiles/ - for publishing the website: /www/tiles.apache.org (including subdirectories tiles-request, tiles-autotag, framework and subdirectories for past versions) I'd also like to take the opportunity to introduce a staging location for the website before voting. =============== Proposed layout =============== My personal choice would go for the following layout, similar to cassandra's: /site/ /doap_Tiles.rdf /forms/ /KEYS /pom.xml /publish/ (*) /src/ /staging/ (*) (*) The new directory site/publish would contain the publishable version of the website. The new directory site/staging would be branch (as in svn copy) of site/publish, and would be the eventual target of the maven svnpubsub plugin in the various projects (site, framework, request, autotag). The release process would be modified as follows: - updating the index and the download pages: xdoc/index.xml and apt/download.apt, would happen in the staging directory before the vote. - after the vote, we would just have 2 operations to perform: committing the new artefacts to dist.apache.org and svn merge staging into publish. Please share your thoughts on this proposition. If nobody commented before Dec 25, I will then proceed with the above plan in order to meet the deadline of Dec 31. Thank you all for your attention. Nick.
