So there would be 2 wikis?  One for official documenation (confluence)
and one for community based documentation (current)?

To me the current Shale website is a bit overwhelming with
information.  I like the idea of moving all of the getting started
docs to confluence and organizing them by subproject.  We just need a
prominent link on the main page to direct users to.  The "Getting
Started" link seems to be a growing trend and its the first thing I
look for when I start with a new technology.

-1 for separate confluence wikis for each version.  I think we can add
version-appropriate notes where needed and keep stuff in one wiki.
Maybe separate sections for each version if there are major
installation gotchas but definitely not a separate wiki.  For release
plans, I definitely think a separate page for each version would be
fine.

Sean

On 8/9/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
Confluence as documentation is excellent.   We've moved all of the
Apache Podling Cayenne's documentation to Confluence over the last
year or so.

Just be aware that infrastructure frowns on using Confluence for
anything other than a static website (or document) generator (for
example, using it as a general purpose wiki)  because of technical
issues with Confluence.

On 8/9/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
>
> On Aug 8, 2006, at 7:00 PM, Wendy Smoak wrote:
>
> > The space naming convention would probably give us SHLx___
> >
> > Do we want to have just one space, and use it like we use Moin, or do
> > we want to push most of the project docs to the wiki?
>
> I don't know anything about Confluence so I can't comment on its
> usability or features, but I *love* the idea of using a wiki for
> doc.  It's so much easier to contribute to.
>
> > In the second case we might want SHLxDEV for our notes on how to use
> > Maven and Subversion for various things, and another one for docs that
> > get exported and included in the distribution.
>
> I'm ok with that so long as we don't make it too hard for people to
> know where to contribute or look for info.
>
> Greg
>
>

Reply via email to