+1 to improving reviews since I agree with sandy on it being our greatest
strength. I also I prefer sandy's approach (unless I'm mistaken), jump in
and see how it goes, we can update a wiki as things proceed. I don't
understand the need for a more formal documentation of process. I'd just
hate for
This stuff was discussed and decided upon in the release meeting a couple
days ago, unless somebody more official wants to make a statement the
results of the decision were:
(1) Developer review days are a go, Soren will set up a wiki page assigning
devs to days (i don't think this is done yet).
I have some anecdotal evidence to add to this from my time at Google:
(1) At Google in all reality you spent at least 2 days a week pretty much
only participating in code review and mailing list responses. This is due to
a couple things, but mostly because code review is taken extremely
Soren Hansen wrote:
That's really a corollary to this proposal: Being in nova-core means you have
a review day once every N days (where N is the amount of (human) members of
nova-core). As such, if you're not prepared to accept such a review day, you
don't get to be part of the team. Simple.
On Feb 17, 2011, at 4:18 AM, Soren Hansen wrote:
That's really a corollary to this proposal: Being in nova-core means you have
a review day once every N days (where N is the amount of (human) members of
nova-core). As such, if you're not prepared to accept such a review day, you
don't get to
-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of
Thierry Carrez [thie...@openstack.org]
Sent: Thursday, February 17, 2011 10:26 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Review days for nova
On Thu, Feb 17, 2011 at 9:51 AM, Ed Leafe e...@leafe.com wrote:
On Feb 17, 2011, at 4:18 AM, Soren Hansen wrote:
That's really a corollary to this proposal: Being in nova-core means you have
a review day once every N days (where N is the amount of (human) members of
nova-core). As such, if
On Wed, Feb 16, 2011 at 9:53 PM, Paul Voccio paul.voc...@rackspace.com wrote:
Not sure what the etiquette is for removing someone. Michael Gundlach is
still listed but is no longer participating.
I think these sorts of things can be resolved on the mailing list just
fine. It's not a big deal
Josh Kearney wrote:
I'm with Sandy on this. I'd like to step in as well.
Could you each start a new thread about your application ? That should
make it easier to track the lazy consensus described in:
http://wiki.openstack.org/Governance/Approved/CoreDevProcess
--
Thierry Carrez (ttx)
Release
2011/2/17 Jay Pipes jaypi...@gmail.com:
Also, good point to keep in mind: Membership to nova-core isn't a
privilege or even any fun. It's a responsibility and a duty to your
fellow contributors :)
The first draft of my e-mail said something about it being a chore,
but I decided to edit that
2011/2/16 Jay Pipes jaypi...@gmail.com:
Lots of coding and bug fixing has been done in the past weeks. As a
result, we've got a big backlog of code reviews to do.
If you have some cycles, please do participate:
https://code.launchpad.net/nova/+activereviews
Nova-core members, remember,
: Soren Hansen so...@ubuntu.commailto:so...@ubuntu.com, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com,
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Review days for nova-core
12 matches
Mail list logo
