A more patient counter than I reports:

if I count from http://jira.codehaus.org/secure/BrowseProjects.jspa#all
taking relevant projects from "Maven 2 Plugins", "Maven Admin" and "Maven
Technologies" categories, I get 61 projects



On Sun, Dec 28, 2014 at 6:20 PM, Benson Margulies <[email protected]> wrote:
> On Sun, Dec 28, 2014 at 6:07 PM, Jake Farrell <[email protected]> wrote:
>> Hey Benson
>> What is the exact number and would an import of existing issues be needed or
>> will the project be taking care of that migration?
>
> I did a count and came up with 46. I've asked for help in rendering
> that number precise.
>
> The Maven dev list is currently mulling over the technology of
> migration; if we can come up with a way to do it for ourselves, I
> think we're willing. At one extreme, there was some discussion of
> working at the SQL level, which, I think, would at least involve
> collaboration.
>
>  Can all the maven jira
>> projects share a common group of project admins, contributors, etc or is
>> each unique?
>
> I believe that the answer is that they will all club together. All the
> Maven plugins are products of the Maven PMC, we don't have any
> fine-grained access control for anything else, so I don't see why we'd
> need it for JIRA.
>
> Do all the notifications for each project go to the same
>> mailing list?
>
> Ditto here, but, I've added dev@maven to this thread so that others
> can participate.
>
>
>>
>> Thanks
>> -Jake
>>
>>
>> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies <[email protected]>
>> wrote:
>>>
>>> Dear Infra,
>>>
>>> For historical reasons, the Maven project has a host of JIRA projects
>>> at codehaus. This is not an ideal situation for many reasons.
>>>
>>> In the past, discussions on moving onto ASF infrastructure have
>>> founded on the sheer number: dozens. Infrastructure didn't feel that
>>> they could support that many project, and the Maven project felt that
>>> it would be very difficult to combine all of the many per-maven-plugin
>>> JIRA projects into a single project with many components.
>>>
>>> It seems to me that much has changed since the last time that this
>>> subject was explored, so I felt that it was worth re-opening the
>>> discussion. Could the existing main JIRA support a large influx of
>>> low-activity projects? Or would infra consider a separate instance?
>>>
>>> Thanks,
>>> benson
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to