L.S., For the main website, I would set that up as a separate project in the sandbox for now so Eric and Lukasz can start working things out there. The big difference with the documentation is that there's probably no need to ever cut a release for that project, rather just update the pages and publish the new site contents, so I guess it will end up being a separate project when we move it out of the sandbox anyway.
For the documentation project, I do agree that commits in github forks would be a good way to propose patches. Especially when adding new files or images or moving things around a lot, those commits are usually a lot easier to pick up and apply. As long as there are JIRAs to back those changes, the real communication is still passing by the developer list where everyone can follow along. There's one other difference though - when people attach a patch to a JIRA issue, they have to select a radio button that says: "Grant license to ASF for inclusion in ASF works (as per the Apache License §5) Contributions intended for inclusion in ASF products (eg. patches, code) must be licensed to ASF under the terms of the Apache License. Other attachments (eg. log dumps, test cases) need not be." If they just point us at a github fork commit, there's no way for them to select that button. Would we have to ask them to attach the patch anyway so they can explicitly grant the license to ASF to include the code or how should we be handling this? Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Fri, Oct 22, 2010 at 4:23 PM, Guillaume Nodet <[email protected]> wrote: > Actually, if you plan to propose patches on the existing > servicemix-documentation project (and not start a new project), you can use > github commits (from your own fork of servicemix-documentation) as patches > referred to by JIRA issue (instead of attaching the diff file to JIRA). > > > On Fri, Oct 22, 2010 at 15:58, Eric Johnson <[email protected]>wrote: > >> Will do. >> >> On Friday, October 22, 2010, Guillaume Nodet <[email protected]> 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 <[email protected]> wrote: >> > >> >> On Friday 22 October 2010 9:27:43 am Guillaume Nodet wrote: >> >> > On Fri, Oct 22, 2010 at 15:19, Daniel Kulp <[email protected]> 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 <[email protected]> >> 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 [email protected] >> Blog http://documentingit.blogspot.com/ >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
