> -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 16, 2008 3:19 AM > To: [email protected] > Subject: Re: documentation > > On Sun, Apr 13, 2008 at 11:44 AM, Nicolas Lalevée < > [EMAIL PROTECTED]> wrote: > > > > > Le 13 avr. 08 à 02:10, Jing Xue a écrit : > > > > On Fri, Apr 11, 2008 at 12:17:14PM -0600, Jean-Claude > Cerebro wrote: > > > > > > > I agree. > > > > > > > > In this case then, I would suggest we get a wiki that we can > > > > freely edit and the core ivyteam can pick and choose what they > > > > want to include into the main docs. Confluence is a > great option > > > > and codehaus uses this. > > > > > > > > > > There is a wiki for Ivy, as well as for any Apache project. 8-) > > > > > > http://wiki.apache.org/ivy/ > > > > > > > oops, I don't know why I didn't saw it, good point ;) > > > Maybe because we don't really use it. It seems some people > would be interested in contributing to an open form of > documentation as a wiki (which doesn't replace the official > reference documentation, which IMHO is better managed at the > same place as the sources). So maybe the problem is that we > need to initialize the effort. Maybe it's because people > aren't used to MoinMoin, or don't like it. I often see people > saying they prefer Confluence, I do prefer confluence too. > Since we have almost nothing on our current wiki, maybe we > could consider migrating to a confluence wiki, and see if > more people get involved?
My 2 cents... IMO, the choice of the wiki software is not the main concern. Some wiki languages are irritating, and it's also irritating that so many exist. But all of them are trivial and easily learned within a few minutes. Confluence is preferable because it can be extended with Java, but the big need we have here is committing text somewhere. I'd prefer to see a public-access Subversion branch for documentation. This would make it easier to accumulate changes and merge them into the reference docs. Although I think the reference docs could be organized more intuitively, at least you can find them if you know the XML schema. The biggest need is to add more content, cross-referencing, and completing the pages that end with "see tutorial". I do think a wiki would be good for collecting common techniques, patterns, and use-case stories. I would want to initialize the effort on the existing MoinMoin site unless someone sees a great advantage in doing otherwise. ----------------------------------------- ==================================================== This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you. ====================================================
