Re: Vote on Confluence/MoinMoin/Static Site

[Steve Vinoski]

I abstain from the vote.

I know for a fact that MoinMoin can do everything Confluence can do,  
including the GUI editor and website exporting and PDF conversion. It  
can do pretty much anything you want, in fact, given how easy it is  
to extend it and all the macros and plugins available for it.  
However, and unfortunately, Apache chooses to run MoinMoin 1.3.4 for  
whatever reason, whereas the current version is 1.5.5. I therefore  
find it difficult to endorse something that Apache doesn't seem to  
want to fully support. (Granted, I may be misjudging here, but I'm  
only stating what I see. Also, I'd be happy to pitch in and get them  
to 1.5.5 if they'd like my help.)

I can't endorse Confluence, either, because it's a commercial  
product, and I don't think an open source project should be directly  
using a commercial product for such a critical element. As I said  
before, I'm surprised Apache even allows it, as IMO it shows  
favoritism to a particular commercial vendor. Would we be allowed to  
use the SocialText wiki instead, which is also available both  
commercially and as open source? I bet not.

--steve

On Sep 26, 2006, at 8:28 PM, John O'Hara wrote:

People are voting for that they know here - shock!

Logic:
MoinMoin is nice.
Confluence is a lot like MoinMoin.
We're using JIRA and Confluence and JIRA go well together (both from
Atlassian).
Maintaining static web pages is v. silly -- Apache are using  
Forrest and
Confluence exports; its proven.
The Confluence GUI editor beats MoinMoin hands down - its actually   
pleasant
to use.  And there's wiki markup too.

Seems to me, that personal preferences for one or the other aside,  
using
Confluence has more going for it.

Therefore I vote: + 1 Confluence for both.

John

On 26/09/06, Alan Conway <[EMAIL PROTECTED]> wrote:

+1 for moinmoin as developer wiki

abstain for static website and doc, I don't know enough about it with
either wiki.

On Tue, 2006-09-26 at 08:57 -0400, Rajith Attapattu wrote:
> +1 for Continue to use MoinMoin as a wiki and use xml/html for  
static
> website
>
> Can you export documentation in confluence in html/pdf format.
> I would assume that when we ship a release we want to send some
> documentation along.
> If we use xml/html for static website we could send the  
documentation
part
> of it along with the build.
>
> Regards,
>
> Rajith
>
> On 9/26/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> >
> > +1 Confluence for both
> >
> > [+1 ] Use Confluence both for wiki and static website. This will
retire
> > MoinMoin from our project.
> > [ ] Continue to use MoinMoin as a wiki and use xml/html for  
static
website
> > [ ] Use MoinMoin for the wiki and introduce Confluence but  
only for
the
> > static site
> >
> > Regards,
> > Marnie
> >
> >
> >
> >
> > This communication is for informational purposes only. It is not
intended
> > as an offer or solicitation for the purchase or sale of any  
financial
> > instrument or as an official confirmation of any transaction. All
market
> > prices, data and other information are not warranted as to
completeness or
> > accuracy and are subject to change without notice. Any  
comments or
> > statements made herein do not necessarily reflect those of  
JPMorgan
Chase &
> > Co., its subsidiaries and affiliates.
> >
> > This transmission may contain information that is privileged,
> > confidential, legally privileged, and/or exempt from  
disclosure under
> > applicable law. If you are not the intended recipient, you are  
hereby
> > notified that any disclosure, copying, distribution, or use of  
the
> > information contained herein (including any reliance thereon) is
STRICTLY
> > PROHIBITED. Although this transmission and any attachments are
believed to
> > be free of any virus or other defect that might affect any  
computer
system
> > into which it is received and opened, it is the responsibility  
of the
> > recipient to ensure that it is virus free and no  
responsibility is
accepted
> > by JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for
> > any loss or damage arising in any way from its use. If you  
received
this
> > transmission in error, please immediately contact the sender and
destroy the
> > material in its entirety, whether in electronic or hard copy  
format.
Thank
> > you.
> >
> >