I am confused. The CMS documentation says this: * * *Instead of developing versioning support and a notification scheme into a database driven CMS, Apache's subversion infrastructure<http://svn.apache.org/>was chosen as the central data store for everything. The fact that the web interface to the CMS interacts with the subversion repository in a LAN environment, combined with the lightning-fast SSDs that serve as l2arc cache for the underlying FreeBSD ZFS filesystem, eliminates virtually all subversion network/disk latency. Subversion continues to scale past 1M commits to deliver high performance to Apache developers, as well as to our internal programs that rely on it.* How do the ASF's git projects maintain their websites if both website options require SVN? Should we just have a separate repository for the site that is in SVN (currently they are in the same repository)? Basically the project voted to move to git, so I don't want to make any choices that block that.
-Jay On Mon, Dec 10, 2012 at 9:53 AM, Joe Schaefer <joe_schae...@yahoo.com>wrote: > No, you may not stick with a manual process. If the > CMS doesn't suit you (there is no requirement to use > markdown- other cms sites use html), you must use > svnpubsub. There is no gitpubsub and there are no > plans to write one. > > > ------------------------------ > *From:* Jay Kreps <jay.kr...@gmail.com> > *To:* Joe Schaefer <joe_schae...@yahoo.com> > *Sent:* Monday, December 10, 2012 12:50 PM > > *Subject:* Re: Kafka TLP website move > > The CMS sounds like it requires some kind of markdown format. Our site is > in HTML, so that won't work. > > svnpubsub sounds like it requires svn. We are trying to move to git, so > that probably isn't good either. > > Is it possible to stick with the manual update process we had for the > incubator site? > > Thanks! > > -Jay > > On Mon, Dec 10, 2012 at 9:32 AM, Joe Schaefer <joe_schae...@yahoo.com>wrote: > > MS site or using svnpubsub > > > > >
