What's Canonical thinking about Bazaar?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

> 1.  You know, JAM has been really visible on this list making sure
>     that no technical-type posts fall through the cracks (and it may
>     be just as important that he stays *out* of threads like this one,
>     for the most part).  That's really good, and ISTR at least one
>     other 3rd-party post mentioning it, as well as somebody (maybe JAM
>     himself?) from the core.  It would help a lot, I think, if
>     somebody could function as testing mentor, and somebody as patch
>     noodler.  To the extent that you can *commit* such resources,
>     advertise the fact.  If you can't, well, I guess the best you can
>     do is "we try to mentor" kind of phrasing (but it has to be backed
>     up with visible progress, on a general public channel such as this
>     list -- if you can't do that, it doesn't help to increase trust or
>     ownership).

Just to note, I *do* read pretty much every post to this list. I haven't
really commented in this thread, because I'm not sure there is much else
to say.

As for community involvement, we certainly have more total committers
who are not canonical employees than are, but certainly not as active.
And canonical does tend to hire people or contract with people who stand
out in the community. Certainly my first year+ on this project was
solely as a community person.

Jelmer, Wouter, Alexander, Gary are all community members who have
commit access in pqm. However, they haven't landed many patches. I think
it comes down to the fact that reviewing is often a bit of a pain, so
people let it fall to others. AFAIK the list of pqm committers is not
public (I think I'm even missing a few). I'll also note that Martin has
said repeatedly that we will listen to any review that is made. (The
official policy is 2 reviews, not necessarily 2 core reviews.)

You mention "how do I get there"... basically by being active. Which is
a bit nebulous, but really we don't have any rules for it. When someone
has been active for a while, and showing that they are doing good work,
we "promote" them.

> 
> 2.  In the list of priorities, add "streamlining bureacracy" (phrase
>     that however you like) and put in the recent efforts at making
>     testing easier.  Maritza has been pretty obviously pleased in the
>     last day or so, so you could take advantage of that.
> 
> 3.  Not directly related but one thing I like on the Python Dev list
>     is the weekly report from the tracker.  I suppose you can get
>     something similar from Launchpad, but I just wouldn't bother going
>     to Launchpad for this, while it's a nice extra when frequent but
>     not too frequent.

I would worry a lot about signal-to-noise ratio. There is quite a bit of
activity on the bug tracker, so I'm not really sure how to distill that
down in a meaningful sense.


John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkr0RU8ACgkQJdeBCYSNAAOkBACeJ5m4lmQRpaFdX4gkdH3hl4rM
r/YAnRTwwe9rdY+Q+45QD11f8qx1ESTx
=9Q/F
-----END PGP SIGNATURE-----