(moving to main dev list as scope has increased)
On 29/03/2007, at 12:28 AM, Jason van Zyl wrote:
On 28 Mar 07, at 9:03 AM 28 Mar 07, Brett Porter wrote:
On 28/03/2007, at 10:35 PM, Jason van Zyl wrote:
No, please don't fragment even more our documentation situation.
We have the stuff in SVN, Confluence users spaces and developer
works spaces. The autoexport could easily be setup with the space
we have if it isn't already.
This documentation is already in its own space, so it's low
impact. I believe it is not currently editable by users, and only
a couple of pages. This does no harm to the current situation, and
gives us the opportunity to try it out.
Reasons I believe cwiki is a better choice:
- autoexport is already configured. No work to do.
- We have a greater level of access than we do at codehaus.
- No banner ads.
- It's back on the apache.org domain.
I don't see any downside...
Other then the severe one one of fragmenting our documentation. Do
what you like.
On 28/03/2007, at 11:16 PM, Emmanuel Venisse wrote:
We'd can use the codehaus wiki for our dev/design pages and for
users pages we'd can use the cwiki with the autoexport and the
maven css to include the content in our site.
I think it would be good to do it for our other products, so we'd
can create easily cookbooks, but this ML isn't the place to discuss
it ;)
Similar to what Emmanuel suggested, how about we move *all* the
current spaces to cwiki, avoiding any further fragmentation, and in
fact removing the current fragmentation between the apache site and
the codehaus confluence, as well as getting all of the above benefits?
Before biting the bullet we can do a trial with this single SCM page.
What do folks think?
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
