I tend to think that it would be helpful if we could setup the wiki spaces for Maven (the tool, not the over-arching umbrella project) in the following ways:
1. separate content areas for 2.0.x, 2.1.x, 2.2.x, etc. 2. each content area should be setup to look like a developer-oriented website for Maven 3. eventually, we should setup a sync process to mirror these developer-oriented sites to a subsection of the main Maven site In other words, it would be great if we could map the content in the wiki directly into the static maven website in some way, and use it to drive developer-oriented content like design discussions, architecture, etc. Ideally, the categories in this dev-subsite should mirror those in jira, confluence, etc. Once we've achieved this uniformity, we should look at ways to monitor it so it doesn't get out of hand again, and actively maintain that category list. That's just some initial thoughts. This stuff looks good for a starting point, Jason, but can we reorg it to be more version-centric? Sort of like a Home that says "Choose your Maven version" then displays the stuff you have now in the Taxonomy section under a new Maven 2.1.x section or something... Thanks for the good work. -john On 5/22/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 22 May 07, at 8:19 PM 22 May 07, Barrie Treloar wrote: > On 5/23/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> Sorry, just assume the devs knew where it was. We point at the user >> space as that's what people can edit but I will try to organize the >> user space in the same way as the dev space so that we can easily >> move documents between the two. But the user space needs some >> cleanup. Upon taking a gander it appears to be a mish mash of every >> single Maven sub project which is kind of confusing. I'll address >> that in another email. > > While we are talking "house keeping" cleanups, it might be handy to do > the same with Jira. > > Maybe cobble together something in the wiki about the steps for > initiating a maven plugin in the sandbox (along with appropriate Jira > changes) and promotion out of the sandbox (with appropriate Jira > changes). > If you want to cobble something together for this page: http://docs.codehaus.org/display/MAVEN/Maven+Sandbox I'll add it while I'm working on it the next few days. I'm just going to clean stuff up before we start serious 2.1.x discussions as it's impossible to glean anything decent so you have a couple of days before I move on to other things. > At the moment I am finding it difficult to locate where to raise > defects for shared and sandbox plugins, and I have a vague feeling > that some newly promoted plugins may not yet have Jira projects. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- John Casey --- Maven Developer (http://maven.apache.org) --- Blog: http://www.ejlife.net/blogs/buildchimp
