I apologize for muddling svnpubsub and the cmd On Mar 13, 2013, at 12:19 PM, Jason van Zyl <ja...@tesla.io> wrote:
> > On Mar 13, 2013, at 12:09 PM, Daniel Kulp <dk...@apache.org> wrote: > >> >> On Mar 13, 2013, at 9:18 AM, Jason van Zyl <ja...@tesla.io> wrote: >> >>> Sadly it was forced upon us it seems. And I don't believe it's a rant to >>> comment on a tool that is hard to use and detracts from productivity >>> especially given how much other work there is to do. It's hard to use tools >>> like this home grown CMS, given the prevalence of great tools like Github >>> pages where you don't even have to think about it. It's amazing that to >>> this day at Apache projects are given little choice over the tools they use. >>> >>> The model at Eclipse is more reasonable where there is infrastructure >>> provided and if you want to leverage that you are free to do so. But you >>> have webspace and want to use something different then you can because >>> ultimately it is the project that is responsible for their website. I think >>> it's great that base services are offered but I don't think it's great to >>> force people to use a tool that no one else in the world uses. I believe it >>> adds zero value to the project, it's only made creating documentation more >>> painful, we've really had tons of problems with syncing and 4/5th of the >>> commit logs are now related to the website. It's unfortunate, much like the >>> situation where we had to wait years to use Git. The infrastructure here is >>> dictated in many cases which is not an optimal model IMO. >> >> Umm…. No one in Apache is forcing the CMS on anyone. > > Just quoting Benson about the choice issue. I don't ever remember any > discussion it just seemed to start happening and I remember mention of a CMS. > >> The only requirement is that your website must be stored in subversion >> someplace. It can be in your projects main svn tree someplace or infra has >> setup a separate repo that can be used. This really is no "different" than >> a directory someplace other than it's backed by an SCM. How the project >> populates that SVN space is completely up to the project. The CMS is just >> one way of accomplishing that. Confluence + the exporter tool + buildbot >> is one. Directly editing .html files with emacs is another. A maven >> build from buildbot is another. That's completely up to the project to >> decide. > > Do you like the Confluence setup? That seems the easiest of solutions where > you edit a page and the site is updated eventually. > >> >> Dan >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder & CTO, Sonatype > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > Our achievements speak for themselves. What we have to keep track > of are our failures, discouragements and doubts. We tend to forget > the past difficulties, the many false starts, and the painful > groping. We see our past achievements as the end result of a > clean forward thrust, and our present difficulties as > signs of decline and decay. > > -- Eric Hoffer, Reflections on the Human Condition > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
