On Thu, Jun 16, 2011 at 1:40 AM, Graham Binns <gra...@canonical.com> wrote: > On 15 June 2011 14:25, Jonathan Lange <j...@canonical.com> wrote: >> It's also a mind-set thing: "how can I help land this patch?" rather >> than looking only for what needs to be fixed. >> >> I think a change like that would be good. > > I agree. We started the move away from "what's wrong with this > branch?" at the January Thunderdome and this seems like a good next > step (I think it's been mooted before, come to that). > >> I also think one blocker is that folk are less comfortable landing to, >> say, lazr.restful than they are to launchpad. I certainly am. > > This is a fair point - I'm largely in the same boat as far as > lazr.restful is concerned. > > To mitigate this, we should probably have a list of experts for each > sub-project. It's then the patch pilot's job to find an expert who has > the time to take a given domain-specific branch (this could also work > for individual parts of the LP tree, too: I wouldn't dare tackle > piloting Soyuz branch without input from bigjools or wgrant, for > example).
Well, we had a very similar worry raised when we reconfigured into squads: the world hasn't ended :). I think its fine, as a pilot, to ask around; I question the need for a manually maintained list of 'who to consult' : ignoring the overhead of such lists, I worry that it would tend to lessen the feeling of shared maintenance of these projects. Where the landing story is unclear or worrying, we should fix that - one low key fix is to make sure its in the README, by asking around the first time if its not already there. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
