You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benjamin Bentmann <be...@udo.edu> on 2008/04/27 15:46:19 UTC

Organization of JIRA projects

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 about the contents of the central
repository and should have been reported under a different JIRA project. But
where? For me as a newbie it could have been "Maven Repository Maintenance"
or "Maven Evangelism".

Also, the projects "maven-upload-applications" and "maven-upload-requests"
look quite similar to me.

Might it be more useful to host all these projects as components in a single
JIRA project about "Maven Central Repository"?

Next up, I am wondering about the purpose of "Maven FAQ" (MNGFAQ) and its
relationship to the FAQs over at Confluence. Can somebody shed some light on
that?

Do we really need to link to MPA on the Maven project site? I believe PMCs
know quite well where to look for the project but why should we point the
ordinary user to it? IMHO, that's adding more confusion.


Benjamin


[0]
http://www.nabble.com/Where-to-create-JIRA-issues-for-Maven-documentation--td16254652s177.html


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Organization of JIRA projects

Posted by Jason van Zyl <ja...@maven.org>.
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 the creation of new issues for MNGFAQ?
>

Done. I copied the Maven permission scheme for MNGFAQ and then removed  
the permission to create new issues.

>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

Three people can keep a secret provided two of them are dead.

-- Unknown 




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Organization of JIRA projects

Posted by Benjamin Bentmann <be...@udo.edu>.
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 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: Organization of JIRA projects

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Just move all the old issues (even closed ones) and then the old issue
numbers should redirect.

-----Original Message-----
From: Jason van Zyl [mailto:jason@maven.org] 
Sent: Sunday, April 27, 2008 11:31 AM
To: Maven Developers List
Subject: Re: Organization of JIRA projects


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 now is history, if we can alias projects then we can start  
using the more appropriate name. Not sure if JIRA will do project  
redirects.

>> So that uses can edit and add FAQ entries
>
> Do you refer to the wiki or the JIRA project? I mean, everybody can  
> signup for a wiki account and extend the FAQs, right? If so, then I  
> still don't understand the purpose of the MNGFAQ project. When  
> should users go to the JIRA project and when to the wiki?
>

Those should be collapsed too and just put in the wiki.

>> You referring to the one link off the confluence landing page   
>> referring to the ITs?
>
> No, I meant
> http://maven.apache.org/issue-tracking.html
> and the section "Maven Project Administration". The majority of  
> people visiting this page are usually Non-PMCs and don't need to  
> know about MPA. The less JIRA projects we offer to select, the  
> simplier the task to choose the right one.
>

I don't think that hurts anything and if committers on the project  
want to see what the PMC is up to I think that's fine.

>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

A language that doesn't affect the way you think about programming is  
not worth knowing.

-- Alan Perlis




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Organization of JIRA projects

Posted by Jason van Zyl <ja...@maven.org>.
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 now is history, if we can alias projects then we can start  
using the more appropriate name. Not sure if JIRA will do project  
redirects.

>> So that uses can edit and add FAQ entries
>
> Do you refer to the wiki or the JIRA project? I mean, everybody can  
> signup for a wiki account and extend the FAQs, right? If so, then I  
> still don't understand the purpose of the MNGFAQ project. When  
> should users go to the JIRA project and when to the wiki?
>

Those should be collapsed too and just put in the wiki.

>> You referring to the one link off the confluence landing page   
>> referring to the ITs?
>
> No, I meant
> http://maven.apache.org/issue-tracking.html
> and the section "Maven Project Administration". The majority of  
> people visiting this page are usually Non-PMCs and don't need to  
> know about MPA. The less JIRA projects we offer to select, the  
> simplier the task to choose the right one.
>

I don't think that hurts anything and if committers on the project  
want to see what the PMC is up to I think that's fine.

>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

A language that doesn’t affect the way you think about programming is  
not worth knowing.

-— Alan Perlis




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Organization of JIRA projects

Posted by Benjamin Bentmann <be...@udo.edu>.
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 or the JIRA project? I mean, everybody can signup 
for a wiki account and extend the FAQs, right? If so, then I still don't 
understand the purpose of the MNGFAQ project. When should users go to the 
JIRA project and when to the wiki?

> You referring to the one link off the confluence landing page  referring 
> to the ITs?

No, I meant
  http://maven.apache.org/issue-tracking.html
and the section "Maven Project Administration". The majority of people 
visiting this page are usually Non-PMCs and don't need to know about MPA. 
The less JIRA projects we offer to select, the simplier the task to choose 
the right one.


Benjamin 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Organization of JIRA projects

Posted by Jason van Zyl <ja...@maven.org>.
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 "Maven Admin".
>
> For example, the recent issue MNG-3551 is about the contents of the  
> central
> repository and should have been reported under a different JIRA  
> project. But
> where? For me as a newbie it could have been "Maven Repository  
> Maintenance"
> or "Maven Evangelism".

We only need one. The Maven Repository Maintenance doesn't appear to  
have any issues in it except one. So I moved it over to Maven  
Evangelism and removed the Maven Repository Maintenance project. I  
don't think evangelism is the right name but there is only one project  
now dealing with the correction of project metadata.

>
>
> Also, the projects "maven-upload-applications" and "maven-upload- 
> requests"
> look quite similar to me.
>

I did the same thing and collapsed them into "maven-upload-requests".

> Might it be more useful to host all these projects as components in  
> a single
> JIRA project about "Maven Central Repository"?
>

Sure, we can make a single project and put the metadata correction and  
upload requests in that projects as components.

> Next up, I am wondering about the purpose of "Maven FAQ" (MNGFAQ)  
> and its
> relationship to the FAQs over at Confluence. Can somebody shed some  
> light on
> that?
>

So that uses can edit and add FAQ entries, which they do. The wiki is  
meant to be the collection point, and one of us is supposed to edit  
and move to a document for the site.

> Do we really need to link to MPA on the Maven project site? I  
> believe PMCs
> know quite well where to look for the project but why should we  
> point the
> ordinary user to it? IMHO, that's adding more confusion.
>

You referring to the one link off the confluence landing page  
referring to the ITs?

>
> Benjamin
>
>
> [0]
> http://www.nabble.com/Where-to-create-JIRA-issues-for-Maven-documentation--td16254652s177.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

Simplex sigillum veri. (Simplicity is the seal of truth.)




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org