contributions

Jordan Mantha mantha at ubuntu.com
Tue May 13 23:11:08 BST 2008


On Tue, May 13, 2008 at 2:48 PM, Scott Kitterman <ubuntu at kitterman.com>
wrote:

> On Tuesday 13 May 2008 17:22, Nicolas Valcarcel wrote:
> > I think i haven't explain myself as i should. The thing was that:
> developer
> > A uploaded a package on the past release circle, then a merge was
> publiched
> > on MoM, a contributor take the merge, work on it and upload the debdiff
> to
> > launchpad reporting the bug as it needs to be, the developer A commented
> on
> > that bug report, so we can be sure that he knows about the contributor
> > working on that merge, then developer B work on that merge and upload it
> by
> > himself without noticing the bug report and contributor's work.
> > That, on the side of the contributor, being a new one, is a really bad
> > thing because he wanted to be his work on the repos, but not only it
> isn't
> > there, it has been done and uploaded by someone else.
> > DaD's comments were a good feature to avoid such things, if contributor
> > left a comment in there, the developer B could see it and work on
> another
> > merge.
> >
> I think I got that and agree it's unfortunate.  The contributor certainly
> has
> my sympathy.  I completely get the frustration.  I just don't know what
> can
> be done that isn't already planned.
>
> A strict check with the last uploader rule would likely have solved this,
> but
> the community rejected that approach last time it was discussed.
>
>
I too agree that it's unfortunate. However, I don't think it's something
people should be getting too upset about (people make mistakes) and I don't
think ping-last-uploader is a proper solution to the issue, for various
reasons.

My feeling is that the best way to help make sure this kind of thing doesn't
happen is to have *one*, canonical place to track merges. Launchpad bugs
seems to be the best way we have of doing that currently. Basically, file a
merge bug if you're going to be working on a merge and *all* people working
on merges, including MOTU sponsors, should be looking *first* to see if
somebody has already filed a bug before working on it.

-Jordan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20080513/71f8f4a4/attachment.htm 


More information about the Ubuntu-motu mailing list