I can help tagging JIRA's for Mahout, but I expect poor compliance by most
committers. If we have a default tag of "unknown", then just having a few
people interested in helping can triage issues pretty quickly. JIRA has
good bulk editing capabilities which would make this pretty easy to do.
On
I propose that we should be working with projects to encourage them to
"tag" issues in JIRA that are suitable for various types of
introductory activities. So, for example, we might have:
- mentor (indicating that this is a fairly major task for which a
mentor is available)
- entry (indicating tha
COM \approx DOM?
On Thu, Dec 3, 2009 at 3:13 PM, Ross Gardler wrote:
> I wonder why we are getting so many of these. I've only ever seen one
> or two incorrectly classified issues on projects. Is there something
> about the name of our tracker that makes people think it's the right
> place?
>
> R
2009/12/2 Kathey Marsden :
> Gert Vanthienen wrote:
>>
>> Next to the options mentioned, another option to consider might be
>> JIRA: for tracking/ranking incoming proposals, we could just create an
>> issue per proposal and use comments on the issue (where we can set the
>> "viewable by" field for
2009/12/2 Kathey Marsden :
> Gert Vanthienen wrote:
>>
>> Next to the options mentioned, another option to consider might be
>> JIRA: for tracking/ranking incoming proposals, we could just create an
>> issue per proposal and use comments on the issue (where we can set the
>> "viewable by" field for
I wonder why we are getting so many of these. I've only ever seen one
or two incorrectly classified issues on projects. Is there something
about the name of our tracker that makes people think it's the right
place?
Ross
2009/12/3 Bertrand Delacretaz (JIRA) :
>
> [
> https://issues.apache.org/
On Thu, Dec 3, 2009 at 2:16 AM, Bertrand Delacretaz
wrote:
> Hi,
>
> Looks like "Community Development" is the default project if you go to
> https://issues.apache.org/jira/secure/CreateIssue!default.jspa, so
> we're bound to get lots of issues that are meant for other projects...
>
> What should
Hi,
Looks like "Community Development" is the default project if you go to
https://issues.apache.org/jira/secure/CreateIssue!default.jspa, so
we're bound to get lots of issues that are meant for other projects...
What should we do about that? Can an invalid default project be set in JIRA?
-Bertr