Thank you Julien. On Wed, Feb 8, 2012 at 1:00 PM, Julien Nioche <lists.digitalpeb...@gmail.com > wrote:
> The Nutch site is already based on svnpubsub. > > On 8 February 2012 12:40, Lewis John Mcgibbney > <lewis.mcgibb...@gmail.com>wrote: > >> Hi, >> >> Can anyone comment where we lie with this? >> >> I really don't have a clue. >> >> Thanks >> >> Lewis >> >> >> ---------- Forwarded message ---------- >> From: Joe Schaefer <joe_schae...@yahoo.com> >> Date: Wed, Feb 8, 2012 at 12:26 PM >> Subject: Mandatory svnpubsub migration by Jan 2013 >> To: Apache Infrastructure <infrastruct...@apache.org> >> >> >> [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER >> INQUIRIES TO infrastruct...@apache.org] >> >> FYI: infrastructure policy regarding website hosting has >> changed as of November 2011: we are requiring all websites >> and dist/ dirs to be svnpubsub or ASF CMS backed by the end of 2012. >> If your PMC has already met this requirement congratulations, >> you can ignore the remainder of this post. >> >> As stated on http://www.apache.org/dev/project-site.html#svnpubsub >> we are migrating our webserver infrastructure to 100% svnpubsub >> over the course of 2012. If your site does not currently make >> use of this technology, it is time to consider a migration effort, >> as rsync-based sites will be PERMANENTLY FROZEN in Jan 2013 due >> >> to infra disabling the hourly rsync jobs. While we recommend >> migrating to the ASF CMS [0] for Anakia based or Confluence based >> sites, and have provided tooling [1] to help facilitate this, >> we are only mandating svnpubsub (which the CMS uses itself). >> >> svnpubsub is a client-server system whereby a client watches an >> svn working copy for relevant commit notifications from the svn >> server. It subsequently runs svn up on the working copy, bringing >> in the relevant changes. sites that use static build technologies >> that commit the build results to svn are naturally compatible with >> svnpubsub; simply file a JIRA ticket with INFRA to request a >> migration: any commits to the resulting build tree will be >> >> instantly picked up on the live site. >> >> >> The CMS is a more elaborate system based on svnpubsub which >> provides a webgui for convenient online editing. Dozens of >> sites have already successfully deployed using the CMS and >> are quite happy with the results. The system is sufficiently >> flexible to accommodate a wide variety of choices regarding >> templating systems and storage formats, but most sites have >> standardized on the combination of Django and Markdown. Talk >> to infra if you would like to use the CMS in this or some other >> fashion, we'll see what we can do. >> >> >> NOTE: the policy for dist/ dirs for managing project releases is >> similar. We have setup a dedicated svn server for handling this, >> please contact infra when you are ready to start using it. >> >> >> HTH >> >> >> [0]: http://www.apache.org/dev/cms >> [1]: >> https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/ >> >> >> >> >> -- >> *Lewis* >> >> > > > -- > * > *Open Source Solutions for Text Engineering > > http://digitalpebble.blogspot.com/ > http://www.digitalpebble.com > http://twitter.com/digitalpebble > > -- *Lewis*
