community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hindess <mark.hind...@googlemail.com>
Subject Re: [proposal] Use JIRA for proposing mentored projects
Date Wed, 10 Feb 2010 15:58:09 GMT

In message <4B72976F.9000205@apache.org>, Ross Gardler writes:
>
> [SNIP]
>
> For clarity, lets stick with "mentor" and "GSoC" since Harmony has
> already started doing this.

Ok. Thanks.

> (note there is still time for objections if people think I'm driing
> too hard in the wrong direction).

Agreed.  I'm happy to pull the data from Harmony JIRA and make it
available on a wiki if necessary.

Having had a conversation about potential projects with a couple of
Harmony developers, we've decided to use JIRA assignee to record the
committer that will mentor the project.  For Harmony, if there is no
assignee then there is no confirmed mentor.

Our intention would be to drop the gsoc label if no mentor is found for
the proposed project within the next few weeks.  Ross, is this okay with
you or would you rather we used a "gsoc_mentor_required" label, until
there was a confirmed mentor, in order to keep the project out of "your"
filter.

Historically and no doubt again this year, there will be cases were a
non-committer will be primary mentor with a committer as co-mentor.
In this case, the committer will be the assignee and the co-mentor
arrangement will be documented in the comments/description.

I wonder how other project will use the JIRA fields/labels and if it
makes sense to try to be consistent across projects.

Regards,
 Mark.



Mime
View raw message