Bazaar

Bazaar

 




Wiki Tools

  • Find Page
  • Recent Changes
  • Page History
  • Attachments

Differences between revisions 43 and 44
Revision 43 as of 2010-11-02 16:55:19
Size: 3418
Editor: vila
Comment: Fix typo
Revision 44 as of 2010-11-08 07:03:09
Size: 3523
Editor: vila
Comment: Next round
Deletions are marked like this. Additions are marked like this.
Line 44: Line 44:
|| 15 Nov w46 || poolie ||
|| 22 Nov w47 || spiv ||
|| 29 Nov w48 || jam ||
|| 6 Dec w49 || vila ||

PatchPilot is the Bazaar community scheme to ensure that patches are not ignored or lost in traffic. When people want to improve something in Bazaar, we help them get their patch up to the right standard to land it.

The current pilot is listed in the IRC channel topic of #bzr on irc.freenode.or for easy reference.

Tips for pilots:

  • When you're piloting, put some concentrated effort into helping people have a good and satisfying experience contributing to Bazaar. Just how you do that is up to you.
  • Send a brief mail before and/or after your stint, to say what you're going to do or what you did, and how it worked out. If you have feedback on the review system or the process, speak up.
  • You're not obliged to deal with all the open patches. We appreciate what you do.
  • You can prioritize whichever you think best achieves the goal of helping people enjoy getting things done in Bazaar. That might be the newest ones, neglected patches, easy patches, or those from new contributors.
  • You can also choose to pick up patches and get them in yourself, by writing tests or fixing things up, or to teach/ask/encourage the original submitter to do these things. Do try to at least explain to the contributor what you're going to do.
  • You can ask (cajole) others to do reviews.
  • You can keep working on patches you're involved with when your stint ends, or you can let the next pilot pick them up. Either way, communicate.
  • If someone's already been asked to do particular changes to get a patch landed, don't move the goalposts without a very good reason.
  • Check that the contributors have executed the Canonical contributor agreement. You can do this automatically using the scan-merge-proposals script from Hydrazine or just by checking their membership of ~contributor-agreement-canonical through the web ui.

  • It's good to get to a specific outcome, so that people know what to do next, and to make this clear in both the text and formal status of the merge proposal. That might be: needs X specific fixes, needs Y tests, needs another review, just needs to be merged.
  • You can also keep an eye on work in progress merges and in progress bugs: these don't currently need review but do represent unfinished work.

  • The recommended way to send approved patches to PQM is using the feed-pqm script from https://launchpad.net/hydrazine/

We started 14 November 2009.

Week

Pilot

6 Sep w36

poolie

13 Sep w37

vila

20 Sep w38

spiv

27 Sep w39

jam

4 Oct w40

poolie

11 Oct w41

vila

18 Oct w42

poolie

25 Oct w43

spiv

1 Nov w44

jam

8 Nov w45

vila

15 Nov w46

poolie

22 Nov w47

spiv

29 Nov w48

jam

6 Dec w49

vila

See also: