<br><br><div class="gmail_quote">On Tue, May 13, 2008 at 3:26 PM, Scott Kitterman <<a href="mailto:ubuntu@kitterman.com">ubuntu@kitterman.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Tuesday 13 May 2008 18:11, Jordan Mantha wrote:<br> <br> > My feeling is that the best way to help make sure this kind of thing<br> > doesn't happen is to have *one*, canonical place to track merges. Launchpad<br> > bugs seems to be the best way we have of doing that currently. Basically,<br> > file a merge bug if you're going to be working on a merge and *all* people<br> > working on merges, including MOTU sponsors, should be looking *first* to<br> > see if somebody has already filed a bug before working on it.<br> <br> </div>Personally I'd find a file a bug first rule very demotivating.  One more rule<br> to convince me to spend my time on other things.</blockquote><div><br>Contributors already have to file a bug so I figured it'd be easiest for them. A comment on MoM (when that works) would also suffice, IMO. The point being, people need a place to check to see if somebody else is working on a merge and people *especially* need to be checking.<br> <br>-Jordan<br><br>P.S. The idea of me having to wait for somebody else's OK just to do a merge, even though I'm a MOTU/Core Dev, is very demotivating.<br></div></div>