I added a JIRA issue for adding recipes: https://issues.apache.org/jira/browse/BUILDR-28
Assaf On 1/22/08, Assaf Arkin <[EMAIL PROTECTED]> wrote: > > On 1/22/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > > Problem with wiki contents coming from non-committers is that they don't > > have a paper trail that enables Apache projects to package the > > documentation. > > So yes, it is nice to have user contributed documentation, and no, you > > can't > > include it in the distribution. > > > > Also note that you need to be careful with wiki contents that are part > > of > > the 'official' site. A PMC needs to make clear what is official and what > > is > > user generated content. The former is 'approved' and official for the > > ASF, > > the latter is, though under the supervision of the Buildr (P)PMC, not > > 'official ASF' documentation. > > > That's correct. If we had an open Wiki that anyone can add to, for legal > reasons, we would not be able to pull that into the official Buildr > documentation. I totally missed out on that before, that documentation is > still subject to copyright issues, not just the source code. So if you want > to contribute a recipe, and we want it to show up in the official > documentation, it would have to go through JIRA. > > It's possible to maintain two Wikis, which some projects do, one official > -- only committers can write to -- and one unofficial. Some projects use > that, and you'd put recipes and troubleshooting tips in the unofficial > Wiki. I prefer to include that in the official documentation as soon as it > shows up. > > So the best work around we found so far is to use Textile, which is as > easy to work with as any other Wiki markup. And creating/merging changes > against Textile files is actually easier than using a Wiki. Once the change > is committed, single rake task uploads it to the Web site. (It will only > show up the next day, when Apache synchronizes, but that's also true for > Wiki edits). > > Assaf > > > My $0.02 > > > > Martijn > > > > On 1/22/08, Thomas Marek < [EMAIL PROTECTED]> wrote: > > > > > > dhpeterson wrote: > > > > I vote +1 for a mini rake intro in the buildr guide. :) > > > > > > > > It would be very useful to better understand tasks, file tasks, rake > > > > > deps > > > > etc, and their relationship to buildr. I have reviewed the docs on > > the > > > rake > > > > site already but I didn't find them to be overly useful. > > > > > > > > I would also like to see some buildr "samples" - e.g. single app > > > projects, > > > > multi-app projects, building WARs and JARs, and building a custom > > ZIP > > > (for a > > > > headless app) which is something I have just managed to do. I would > > be > > > happy > > > > to contribute whatever I can. > > > > > > > > Regs, > > > > > > > > Dave > > > > > > > +1 > > > > > > Wouldn't it be great to have a wiki for creating such thing like > > intros > > > and receipts? > > > Does apache not provide wikis for their projects? > > > And assaf could merge the content with the svn docs? > > > > > > Regards, > > > Thomas > > > > > > > > > > > -- > > Buy Wicket in Action: http://manning.com/dashorst > > Apache Wicket 1.3.0 is released > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 > > > > > > -- > CTO, Intalio > http://www.intalio.com > -- CTO, Intalio http://www.intalio.com
