contributions

Nicolas Valcarcel nvalcarcel at ubuntu-pe.org
Tue May 13 22:22:32 BST 2008


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.

On Tue, May 13, 2008 at 8:18 AM, Scott Kitterman <ubuntu at kitterman.com>
wrote:

>  On Monday 12 May 2008 20:51, Nicolas Valcarcel wrote:
> > Hi,
> >     Since hardy i have notice that some times contributions are not
> taking
> > into account, mostly on merges. For MOTUs and core devels is not needed
> to
> > file a bug since it's only needed to upload the package, but some times,
> a
> > contributor, which need to file a bug, upload his debdiff and ask for
> > sponsorship, make the work for nothing, becase one developer (no one in
> > special) work on that merge and upload it. I think is not fair, and
> > discourage for new contributor, so i think it lack for a common process
> > where this things doesn't happen.
>
> I appreciate your problem.  I remember such things happening in the past
> too.
> It's unfortunate when such things happen, but I don't know what can be
> done
> to prevent it completely.  MOTU are supposed to check bugs when they do a
> merge.
>
> Ideally we'll have the new merged (pun intended) MoM and DaD up soon so
> there
> is one place to go for merge information that can include comments about
> what
> people are working on.  That should help too.
>
> From our IRC discussion, I gather you had discussed the merge with the
> previous uploader, but that the MOTU that uploaded his own merge
> (apparently)
> did not.  While there is no rule requiring people to check with the last
> uploader, I still think it is generally a good idea (particularly early in
> the release cycle when there is no great rush to get merges uploaded).
>  That
> might have avoided the problem in this case.
>
> I think we have sufficient process in place (MOTU should check bugs before
> uploading a merge to see if there are other fixes that should be included)
> or
> coming (single source of merge information with comments) to minimize this
> problem.  I don't think we'll ever eliminate it completely.
>
> Scott K
>
> --
> Ubuntu-motu mailing list
> Ubuntu-motu at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20080513/ec4c352e/attachment-0001.htm 


More information about the Ubuntu-motu mailing list