RE: [mylyn-dev] mentoring contributions, tips for patches

["Mik Kersten" <mik@xxxxxxxxxxx>]

Nothing has changed about our policy with respect to commenting on bug
reports, that policy is still captured on our communication guidelines and
remains the same as it was a year ago.  

  http://wiki.eclipse.org/Mylyn_Contributor_Reference#Communication

I'm not sure how that was implied so let me know if I should update any of
the corresponding wiki sections.  What has changed is that when a mentored
contributor is given multiple directions, they can defer to their mentor.
The mentor will be responsible for aligning the comments on the bug report
with the way that the contributions should be managed in order to meet the
process and priorities (e.g. ensuring that any API changes are tested,
consider performance).  This is very similar to how we have run the summer
of code and helps manage contributions and it has worked very well there.
For contributors interested in earning commit rights, mentors should also be
proactive in helping find areas of contribution that are relevant to the
project and community.  

Mik

> -----Original Message-----
> From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Eugene Kuleshov
> Sent: Monday, November 26, 2007 9:40 PM
> To: Mylyn developer discussions
> Subject: Re: [mylyn-dev] mentoring contributions, tips for patches
> 
> Mik,
> 
>   Does that imply that non-mentors (whatever that means) should not be
> commenting on the bug reports?
> 
>   regards,
>   Eugene
> 
> 
> Mik Kersten wrote:
> > As discussed during our conference call last week, I have taken a
> first pass
> > at listing mentors for frequent Mylyn contributors.  There have been
> some
> > problems with crossing signals from committers, which can cause
> wasted
> > effort for contributors.  In addition, the volume of user feedback
> and
> > patches has increased to the point where we have to further
> streamline our
> > process in order to support the enhancements coming in as patches
> without
> > overly starving the key fixes and improvements that we have scheduled
> for
> > 2.x and 3.0.
> >
> > Committers: please take a look at the following list and review or
> request
> > changes.  We should update this whenever we see frequent
> contributions from
> > someone.  In general, the areas that the individual is contributing
> in
> > should correspond to the committers' area of ownership.
> >
> >   http://wiki.eclipse.org/index.php/Mylyn#Mentors
> >
> > Contributors: please note that I have added a shortlist of tips on
> how to
> > get your patches applied in a timely manner.
> >
> >   http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Tips
> >
> > Cheers,
> >
> > Mik
> >
> 
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev