On 27-Apr-08, at 11:56 AM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
> When should users go to the JIRA project and when to the wiki?
Those should be collapsed too and just put in the wiki.
OK, I just edited the project description to redirect people over to
Confluence. Can we disable
Jason van Zyl wrote:
> When should users go to the JIRA project and when to the wiki?
Those should be collapsed too and just put in the wiki.
OK, I just edited the project description to redirect people over to
Confluence. Can we disable the creation of new issues for MNGFAQ?
Benjamin
Just move all the old issues (even closed ones) and then the old issue
numbers should redirect.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 27, 2008 11:31 AM
To: Maven Developers List
Subject: Re: Organization of JIRA projects
On 27-Apr-08, at 8
On 27-Apr-08, at 8:11 AM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
I don't think evangelism is the right name
I agree, from a user's perspective the name might be a little
cryptic. The name of the other project "Maven Repository
Maintenance" sounds more descriptive.
The problem n
Jason van Zyl wrote:
I don't think evangelism is the right name
I agree, from a user's perspective the name might be a little cryptic. The
name of the other project "Maven Repository Maintenance" sounds more
descriptive.
So that uses can edit and add FAQ entries
Do you refer to the wiki
On 27-Apr-08, at 6:46 AM, Benjamin Bentmann wrote:
Hi,
this thread is somehow extending the discussion about "Where to
create JIRA
issues for Maven documentation?" [0] and seeks to clarify the intended
target JIRA project for new issues, especially those projects listed
in the
category "M
Hi,
this thread is somehow extending the discussion about "Where to create JIRA
issues for Maven documentation?" [0] and seeks to clarify the intended
target JIRA project for new issues, especially those projects listed in the
category "Maven Admin".
For example, the recent issue MNG-3551 is abo
