Fwd: Mandatory svnpubsub migration by Jan 2013

[Kevan Miller <ke...@gmail.com>]

Begin forwarded message:

> From: Joe Schaefer <jo...@yahoo.com>
> Subject: Mandatory svnpubsub migration by Jan 2013
> Date: February 8, 2012 7:26:48 AM EST
> To: Apache Infrastructure <in...@apache.org>
> Reply-To: private@geronimo.apache.org
> Reply-To: Joe Schaefer <jo...@yahoo.com>
> 
> [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER
> INQUIRIES TO infrastructure@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/
> 

Re: Mandatory svnpubsub migration by Jan 2013

[Kevan Miller <ke...@gmail.com>]

On Feb 9, 2012, at 8:54 AM, Forrest Xia wrote:

> Thank you for this information. 
> 
> My home network is a little bit slow to open the urls, whatever, some questions first in my mind first, what's the impact to our geronimo web site? will need to move https://svn.apache.org/repos/asf/geronimo/site/ to another server to use svnpubsub?
> 
> Any impact to our documentation system - confluence?

Forrest,
One minor point, please don't cross-post to public and private mailing lists… Not a big danger, here, but it's a good habit to avoid… In general cross-posting can lead to somebody saying something "private" on a "public" mailing list… Plus, there's no reason for any discussions on this topic to be on private@… The original email went to private@ to insure the PMC had appropriate awareness.

I think the websites do a pretty good job of explaining things… In general, all website content needs to be in svn. Content will no longer be sync'ed from people.apache.org. As Joe's email mentions, we can continue to use Confluence (though some migration/reconfiguration will be required). However, Confluence is likely to be an uphill battle (at some point, infra is going to stop supporting Confluence). We may well be better off using CMS. At a minimum, we definitely need to investigate/discuss moving to CMS.

--kevan

Re: Mandatory svnpubsub migration by Jan 2013

[Kevan Miller <ke...@gmail.com>]

One other thing -- use infrastructure@apache.org mailing list if we need any help from infra -- I'm sure Joe has plenty to keep him busy…

--kevan

Re: Mandatory svnpubsub migration by Jan 2013

[Forrest Xia <fo...@gmail.com>]

Thank you for this information.

My home network is a little bit slow to open the urls, whatever, some
questions first in my mind first, what's the impact to our geronimo web
site? will need to move https://svn.apache.org/repos/asf/geronimo/site/ to
another server to use svnpubsub?

Any impact to our documentation system - confluence?

On Thu, Feb 9, 2012 at 12:28 AM, Kevan Miller <ke...@gmail.com>wrote:

>
>
> Begin forwarded message:
>
> > From: Joe Schaefer <jo...@yahoo.com>
> > Subject: Mandatory svnpubsub migration by Jan 2013
> > Date: February 8, 2012 7:26:48 AM EST
> > To: Apache Infrastructure <in...@apache.org>
> > Reply-To: private@geronimo.apache.org
> > Reply-To: Joe Schaefer <jo...@yahoo.com>
> >
> > [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER
> > INQUIRIES TO infrastructure@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/
> >
>
>


-- 
Thanks!

Regards, Forrest