Given Noel's message included below, we can even go for
wiki.apache.org/${subproject} instead of
wiki.apache.org/logging-${subproject}. Both options should result in
the same behavior wrt notifications. Craig McClanahan objected against
the first option, fearing name classes but apparently that is not a
problem because each subproject of Logging Services will have its own
Wiki in either case.Anyway, given that we already have a positive vote for the first option, let's go with that if you like. In other words, please submit your request, the one we just voted for, to infrastructure@ at the time of your convenience.
To: "Jakarta Project Management Committee List" <[EMAIL PROTECTED]> Subject: RE: Decision Needed Regarding Wiki Date: Wed, 7 Jan 2004 12:21:28 -0500
The notification address is really the primary issue. A single notification address would allow the use of a single wiki. Less work for infrastructure and less interwiki linking. However, the downside is more traffic on a single mailing list, resulting in people tuning out.
The Wiki URL is quite simple:
wiki.apache.org/$WIKI/$PAGE
where $PAGE may have multiple path components. Notification is associated with the $WIKI component, which does not support multiple path components. We could have:
wiki.apache.org/jakarta/commons/collections
but that would be a wiki named jakarta and a page named commons/collections. Therefore, any change would result in a message to the jakarta wiki notification address. If we had:
wiki.apache.org/jakarta-commons/
then changes to any of the pages could go to the notification address associated with that Wiki.
Henri Yandell wrote:
> All I know is that I get pissed off when setting up a link > of [ReleasePlan] is not allowed because some other project > has already chosen that name.
Understood. The Wiki Farm supports pages like:
wiki.apache.org/jakarta/commons/collections/ReleasePlan wiki.apache.org/jakarta-commons/collections/ReleasePlan
So you're covered either way. The primary difference is notification. On this issue, we seem to have two opposing perspectives. Martin Cooper wrote:
> The wikis can be changed by anybody, not just committers. I don't feel as > much of a need to keep an eye on people who have been voted in by the PMC > as I do any old Tom, Dick or Harry messing with the wikis.
whereas, Erik Hatcher wrote:
> My main interest is in having page updates being mailed to a project > specific list so that content could be monitored. Having content > changes for all projects go to a central list is not a good solution > to me - I would not want to be on that e-mail list.
We need to resolve this issue. For example, we seem to have an emerging consensus for:
wiki.apache.org/jakarta - shared community pages, PMC pages,
wiki.apache.org/jakarta-$product - product specific pages
However, to where to we send the change notices? And do we allow projects that don't want their own wiki to use the jakarta wiki? Again, the question is where to send notification messages, and we need to resolve this issue.
Suggestions?
--- Noel
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
