Re: Kafka TLP website move
You need to tell us HOW to create it, either as a CMS site or using svnpubsub! From: Jay Kreps jay.kr...@gmail.com To: infrastruct...@apache.org infrastruct...@apache.org Cc: dev@kafka.apache.org Sent: Monday, December 10, 2012 12:30 PM Subject: Re: Kafka TLP website move Ooops, wrong ticket: https://issues.apache.org/jira/browse/INFRA-5586 :-) -Jay On Mon, Dec 10, 2012 at 9:29 AM, Jay Kreps jay.kr...@gmail.com wrote: Hey guys, It's been a few weeks and we are still waiting on getting a top-level website url for Kafka. Tried just making it myself, but that didn't work: jkreps@minotaur:/www$ mkdir kafka.apache.org mkdir: kafka.apache.org: Permission denied Are we confused? Can anyone help? Here is the ticket: https://issues.apache.org/jira/browse/KAFKA-654 Thanks! -Jay
Re: Kafka TLP website move
Cool, makes sense. Let's go with SVN and svnpubsub then. The site subdirectory that we would published is https://svn.apache.org/repos/asf/kafka/site In the future if we switch to git we will just leave the site in svn and continue to use that for site updates. -Jay On Mon, Dec 10, 2012 at 10:15 AM, Ted Dunning ted.dunn...@gmail.com wrote: We have an SVN repo for the web site and a git repo for code. On Mon, Dec 10, 2012 at 10:13 AM, Jay Kreps jay.kr...@gmail.com wrote: 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 infrastructurehttp://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.comwrote: 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.comwrote: MS site or using svnpubsub
Re: Kafka TLP website move
Our experience with CMS has been good, btw. Consider as an option. You get a very simple mark-down based web site with browser editing if you like it. Works very well. On Mon, Dec 10, 2012 at 10:26 AM, Jay Kreps jay.kr...@gmail.com wrote: Cool, makes sense. Let's go with SVN and svnpubsub then. The site subdirectory that we would published is https://svn.apache.org/repos/asf/kafka/site In the future if we switch to git we will just leave the site in svn and continue to use that for site updates. -Jay On Mon, Dec 10, 2012 at 10:15 AM, Ted Dunning ted.dunn...@gmail.comwrote: We have an SVN repo for the web site and a git repo for code. On Mon, Dec 10, 2012 at 10:13 AM, Jay Kreps jay.kr...@gmail.com wrote: 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 infrastructurehttp://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.comwrote: 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.comwrote: MS site or using svnpubsub
