Will do. On Friday, October 22, 2010, Guillaume Nodet <gno...@gmail.com> wrote: > Well, we actually already have a sandbox opened to committers ? I did not > remember it was set up like that. > > Eric, feel free to create your own tree in the servicemix sandbox and hack > at will there ! :-) > > On Fri, Oct 22, 2010 at 15:38, Daniel Kulp <dk...@apache.org> wrote: > >> On Friday 22 October 2010 9:27:43 am Guillaume Nodet wrote: >> > On Fri, Oct 22, 2010 at 15:19, Daniel Kulp <dk...@apache.org> wrote: >> > > On Friday 22 October 2010 9:10:01 am Guillaume Nodet wrote: >> > > > Dan, Given Eric is not a committer, I don't see any other way if he >> > > > wants to get started. >> > > >> > > Create a sandbox open to all Apache committers. Several projects have >> > > them, >> > > including CXF, Maven, etc... Trivial to setup. >> > >> > Right, good idea. Do you know how to set that up ? With the new ldap >> > permissions, i'm not quite sure how the svn permissions is set up now. >> >> No ldap needed, just edit the asf-authorization-template file. The CXF >> entry: >> >> [/cxf] >> @cxf = rw >> >> [/cxf/sandbox] >> @committers = rw >> >> >> >> > > What I was trying to suggest was to see if scalate can get stuck into >> the >> > > CMS >> > > there somehow instead of the Perl templating thing they have now. I >> > > THINK you would still be able to use the "svn checked out" type form, >> > > but for others, you could just use the web frontend and not bother with >> > > svn checkouts, >> > > commits, etc.... Was just a thought. That said, I don't know how >> > > "ready" >> > > it is yet. Possibly something to investigate later. >> > >> > Yeah, the svn based is really one of the important thing imho. It makes >> it >> > way easier to submit patches. Also, from what i read, the CMS is bound >> to >> > markdown atm, >> >> Well, it associates file extensions with a process to run somehow. If you >> edit a file with extension "mdtext", it uses the Perl thing, but it >> supposedly >> can be extended for a bunch of other things. See: >> >> http://www.staging.apache.org/dev/cms.html#templating >> >> >> Dan >> >> >> >> > I actually did not really understand where the value was, but >> > I may have missed something. It looks to me that scalate is way more >> > powerful. >> > >> > > Dan >> > > >> > > > On Fri, Oct 22, 2010 at 15:00, Daniel Kulp <dk...@apache.org> wrote: >> > > > > On Friday 22 October 2010 8:40:35 am Eric Johnson wrote: >> > > > > > Would it make sense to start a github project >> > > > > >> > > > > Only if you want your next board report to say SMX collaboration is >> > > > > happening >> > > > > at GitHub. Hint: that won't go over well. >> > > > > >> > > > > > and start hacking together a >> > > > > > scalate version of the static site incorporating the design ideas >> > > >> > > being >> > > >> > > > > > offered? (I suggest scalate because the Apache infrastructure >> team >> > > > > > is deprecating Confluence due to lack of maintenance on the >> static >> > > > > > site >> > > > > >> > > > > export >> > > > > >> > > > > > plug-in.) >> > > > > >> > > > > What MAY actually be an interesting idea is to approach INFRA and >> ask >> > > >> > > for >> > > >> > > > > some >> > > > > details on the new CMS. It supposedly has a pluggable >> > > > > template/markup system, but I don't know how "pluggable" it really >> > > > > is (like is a JVM allowed). >> > > > > All the content would be in SVN so folks could contribute that way >> or >> > > >> > > use >> > > >> > > > > the >> > > > > web gui thing, it supports stagin-- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
-- Principle Technical Writer Phone (781) 280-4174 Skype finnmccumial E-Mail emjohn...@fusesource.com Blog http://documentingit.blogspot.com/
