Very cool. Thanks for setting this up Assaf -Shane
On Tue, Aug 19, 2008 at 5:39 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > The community WIki is now up and running: > > http://cwiki.apache.org/confluence/display/BUILDR/Index > > Assaf > > > On Mon, Aug 18, 2008 at 8:49 PM, Shane Witbeck <[EMAIL PROTECTED]> > wrote: > > It's sounds as if you're advocating moving everything to Confluence. Why > not > > just link to the wiki for community contributions initially and move > > existing stuff over where it makes sense? > > > > -Shane > > > > > > On Mon, Aug 18, 2008 at 8:26 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > > > >> On Mon, Aug 18, 2008 at 2:55 PM, Alex Boisvert <[EMAIL PROTECTED]> > >> wrote: > >> > I'd like both: a wiki to manage the website (I'm OK with CLAs) and a > >> > sandbox where people can do whatever they want. > >> > > >> > I'd like the website to be decoupled from the current documentation so > >> it's > >> > possible to quickly update things like news, download, etc. And I > like > >> the > >> > fact that documentation is managed together with the source-code and > that > >> it > >> > can produce good-looking HTML, and PDF documents. It would be good > to > >> > have documentation for various Buildr versions on the website at some > >> point. > >> > >> Sandbox, definitely. (I'll keep annoying Matthieu, but it will > >> happen, no worries) > >> > >> Documentation is a bit tricker, ideas welcome. Right now we use > >> Textile, processed through two separate templates. One templates > >> converts each page to create the site, the other template merges all > >> the pages together to create one long HTML, which is then converted > >> into PDF. It's probably possible to do from Confluence, but it would > >> be painful. > >> > >> The news section is manually edited, the download links are > >> automatically generated. The text is kept in raw form (Textile) in > >> the source directory, and is part of the source distribution, so it's > >> subject to the same lifecycle: each release has its own documentation. > >> > >> Downsides to this setup: harder to change the documentation, has to be > >> done via patches, and very hard to push updates in real time (right > >> now, site only updated during release). > >> > >> Assaf > >> > >> > > >> > alex > >> > > >> > > >> > On Mon, Aug 18, 2008 at 12:04 PM, Assaf Arkin <[EMAIL PROTECTED]> > wrote: > >> > > >> >> I did some reading over the weekend [1], and want to add a bit of > >> >> context. There are two types of Wiki spaces. We can have both, but > >> >> they're used differently. > >> >> > >> >> A Wiki space can be open to the general public, all you need to do is > >> >> login and make a change. This is great for supplemental info, tips & > >> >> tricks, whiteboard discussions, impromptu edits, etc. It's separate > >> >> from the main site and official documentation. > >> >> > >> >> The second type of space is open only to editors who have a CLA with > >> >> Apache. Anyone can sign a CLA [2], so this won't limit who can > >> >> contribute, but it takes a few days to get your account, so it's not > >> >> as useful for ad hoc edits. > >> >> > >> >> On the other hand, because all editors have a CLA, we can use the > >> >> second type to generate the Web site (see Martijn's email for more > >> >> details). > >> >> > >> >> Assaf > >> >> > >> >> > >> >> [1] http://cwiki.apache.org/CWIKI/ > >> >> [2] http://www.apache.org/licenses/#clas > >> >> > >> >> > >> >> On Mon, Aug 18, 2008 at 9:42 AM, Martijn Dashorst > >> >> <[EMAIL PROTECTED]> wrote: > >> >> > cwiki *is* confluence. The other wiki option is moinmoin, through > >> >> > wiki.apache.org iirc. > >> >> > > >> >> > What you see on cwiki.apache.org are the *exported* wiki sites > >> through > >> >> > the autoexport plugin. For several projects, including Wicket > >> >> > (http://wicket.apache.org) this exported site is transfered to the > >> >> > www/ infrastructure. > >> >> > > >> >> > e.g.: http://cwiki.apache.org/WICKETxSITE is transfered to > >> >> > http://wicket.apache.org > >> >> > > >> >> > This is documented here: > >> >> http://wicket.apache.org/writing-documentation.html > >> >> > > >> >> > Martijn > >> >> > > >> >> > On Mon, Aug 18, 2008 at 5:50 PM, Shane Witbeck < > >> [EMAIL PROTECTED]> > >> >> wrote: > >> >> >> Is cwiki the only choice we have? For instance, I think > Atlassian's > >> >> >> Confluence is available for free to open source projects. I > haven't > >> used > >> >> >> cwiki but I have used Confluence so I'm not sure how they compare. > >> >> >> > >> >> >> -Shane > >> >> >> > >> >> >> > >> >> >> On Wed, Aug 13, 2008 at 4:45 PM, Assaf Arkin <[EMAIL PROTECTED]> > >> wrote: > >> >> >> > >> >> >>> On Wed, Aug 13, 2008 at 7:43 AM, Shane Witbeck < > >> >> [EMAIL PROTECTED]> > >> >> >>> wrote: > >> >> >>> > It seems a community supported wiki would benefit a lot of > people > >> >> using > >> >> >>> > buildr. I'm not sure how this works in the apache.org realm > but > >> are > >> >> >>> there > >> >> >>> > plans to eventually have a wiki? > >> >> >>> > >> >> >>> 1. guilt buildr-dev into catching up with the rest of the > civilized > >> >> >>> world and adding a Wiki. > >> >> >>> 2. cwiki.apache.org would give us a space if we just ask for it. > >> >> >>> 3. ? > >> >> >>> 4. Profit! > >> >> >>> > >> >> >>> > > >> >> >>> > I think a wiki would lower the barrier for people to contribute > >> >> >>> > code/patterns/extensions for Buildr. > >> >> >>> > > >> >> >>> > -Shane > >> >> >>> > > >> >> >>> > >> >> >> > >> >> > > >> >> > > >> >> > > >> >> > -- > >> >> > Become a Wicket expert, learn from the best: > >> http://wicketinaction.com > >> >> > Apache Wicket 1.3.4 is released > >> >> > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > >> >> > > >> >> > >> > > >> > > >
