On 07/31/2014 11:24 AM, Stefano Maffulli wrote:
> Given the amount of google juice that Ask OpeNStack gets, I'd suggest to
> ask those questions there and work on answers on that site. It's really
> effective at making information like this available. We can tag the
> questions and reference them i
On 07/28/2014 01:51 AM, Thierry Carrez wrote:
> This is a great set of questions. When we have answers, we should
> consolidate them into a "contributors expectations" wiki page (in the
> same vein as the ML Etiquette one[1] or the Reviewers expectations one[2])
Given the amount of google juice th
On 28 July 2014 11:37, Salvatore Orlando wrote:
> Therefore the likeness of your patch merging depends on the specific
> nature of the -1 you received.
>
This is really a key point.
Here is a pattern that's worth recognising:
If your code is in reasonable shape but there is no urgent need to c
For what is worth, I'm trying below to provide my perspective on Luke's
question both as a reviewer and as developer.
Salvatore
On 26 July 2014 20:02, Luke Gorrie wrote:
> On 25 July 2014 20:05, Stefano Maffulli wrote:
>
>> Indeed, communication is key. I'm not sure how you envision to
>> im
Luke Gorrie a écrit :
> Here are some other topics that seem to take some time to develop a mental
> model of:
>
> How quickly and how often should you revise your patchset after a -1? (Is
> it better to give the community a week or so to collectively comment? Or
> should you revise ASAP after eve
Wow! These are the exact questions that I have struggled with. Thanks for
stating them so clearly.
Regards,
Mandeep
-
On Sat, Jul 26, 2014 at 11:02 AM, Luke Gorrie wrote:
> On 25 July 2014 20:05, Stefano Maffulli wrote:
>
>> Indeed, communication is key. I'm not sure how you envision to
On 25 July 2014 20:05, Stefano Maffulli wrote:
> Indeed, communication is key. I'm not sure how you envision to
> implement this though. We do send a message to first time
> contributors[1] to explain them how the review process works and give
> them very basic suggestions on how to react to comm
On Fri 25 Jul 2014 01:25:16 AM PDT, Luke Gorrie wrote:
> I have one idea for low-hanging fruit to put new contributors more at
> ease: to explain a little about both when and why the "Merge" button
> is finally pressed on a change.
Indeed, communication is key. I'm not sure how you envision to
im
On 24 July 2014 17:09, Kyle Mestery wrote:
> I've received a lot of emails lately, mostly private, from people who
> feel they are being left out of the Neutron process. I'm unsure if
> other projects have people who feel this way, thus the uniquely worded
> subject above. I wanted to broadly add
-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info]
Sent: July-24-14 12:27 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron] [not-only-neutron] How to Contribute
upstream in OpenStack Neutron
On 07/24/2014 11:50 AM, Alan Kavanagh wrote:
>
On 07/24/2014 11:50 AM, Alan Kavanagh wrote:
> Hi Kyle
>
> Thanks for taking the time for writing this note also I know this is not an
> easy discussion and not something being a matter of "waving hands or
> fingers". I believe what you have stated is well understood, though the main
> points I
Hi Kyle
Thanks for taking the time for writing this note also I know this is not an
easy discussion and not something being a matter of "waving hands or fingers".
I believe what you have stated is well understood, though the main points I
raised seems to be missing from this Neutron Policies wi
12 matches
Mail list logo
