Do we have to stick to -dev and -commits could we not have a -wiki or is
that just going over the top?
I guess the emails will have suitable subject string or from address that
can be used to filter the mail. For all the lucky people that have decent
mail clients.
As long as that is the case then I have no strong preference.
--
Martin
"Cliff Schmidt" <[EMAIL PROTECTED]>
2006-09-07 23:43
Please respond to qpid-dev
To: [email protected], [EMAIL PROTECTED]
cc:
Subject: Re: Re: wiki vote
Sure -- I can do this (and I'll point to what I did afterwards).
But first, where would you all like the diffs to go when someone makes
a non-insignificant change/addition to a wiki page? to the -dev list
or the -commits list?
If you want to make this list really just be discussion and are afraid
of lots of wiki updates being noisy, we could put it on -commits. But
if you think the wiki updates *are* the conversation and that people
who don't want to monitor code changes might want to follow wiki
updates, then we could have it go to -dev.
Personally, I would go for -commits, but I think either choice is
reasonable.
Any strong preferences out there?
Cliff
On 9/7/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
>
> Cliff, I have been off-line but it looks like MoinMoin is the desired
> chose. There is
> Confluence content but I think lets just go MoinMoin and we work out
> what is needed
> to convert the content.
>
> Can you do the required to get it set up.
>
> Carl.
>
> Alan Conway wrote:
> > There appears to be consensus for moinmoin - what's the next step? I
> > have some stuff I'd like to write up.
> >
> > On Wed, 2006-09-06 at 15:50 -0700, Cliff Schmidt wrote:
> >
> >> Personally, I'd start a formal vote thread and compare numbers only
if
> >> consensus isn't obvious from this discussion. I guess we'll find
that
> >> out soon enough...
> >>
> >> Cliff
> >>
> >> On 9/6/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> >>
> >>> Thanks, Cliff. I guess this means we need to vote on which wiki we
> >>> prefer, so we can submit the request? Assuming that's the case,
> >>> here's my vote for MoinMoin.
> >>>
> >>> --steve
> >>>
> >>> On Sep 6, 2006, at 6:07 PM, Cliff Schmidt wrote:
> >>>
> >>>
> >>>> BTW,
> >>>> To get a wiki project home page set up requires either an email or
a
> >>>> jira submission (probably the latter, but I don't recall right now)
to
> >>>> the infrastructure folks. After that, any registered user (to
prevent
> >>>> wiki spam) can add whatever pages they like..
> >>>>
> >>>> I'll find out exactly what is required to set this up by the time
you
> >>>> guys pick which one you want to use. I don't know of any good docs
on
> >>>> this yet. I checked the usual place (apache.org/dev/) and didn't
see
> >>>> it.
> >>>>
> >>>> Cliff
> >>>>
> >>>> On 9/6/06, Cliff Schmidt <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>> On 9/5/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> >>>>>
> >>>>>> Hi all, it would be nice if we could get a Qpid wiki up and
running
> >>>>>> under the Apache Incubator. There are some Qpid design notes we'd
> >>>>>> like to start putting together but we don't yet have a place to
put
> >>>>>> them.
> >>>>>>
> >>>>>> I looked through the website, but I don't pretend to know the
> >>>>>>
> >>>>> proper
> >>>>>
> >>>>>> steps for getting a wiki or project website started -- Cliff,
> >>>>>>
> >>>>> can you
> >>>>>
> >>>>>> help out here? I personally prefer MoinMoin over Confluence, but
I
> >>>>>> realize I'm probably in the minority here.
> >>>>>>
> >>>>> I think it's up to you guys to decide whether to use the
Confluence
> >>>>> wiki or MoinMoin. I believe these are the two options that ASF
> >>>>> infrastructure folks offer. See examples at
http://wiki.apache.org
> >>>>> and http://cwiki.apache.org. Most projects at the ASF use the
former
> >>>>> (MoinMoin), but there are a couple who have asked to use
Confluence.
> >>>>>
> >>>>> Cliff
> >>>>>
> >>>>>
> >>>
> >
> >
>
>
>
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.
