Michal,

Thanks for setting this up.  For future votes using civs, I’d recommend keeping 
polling results hidden until the poll is completed as to not unduly influence 
voters by the current incomplete polling results.

If folks would like to use civs in favor of our current mailing list voting 
used for core review policy changes, that seems fine, but we need to ensure 
core reviewer voters are identified in the results by name for full 
transparency.  We need to make certain civs supports this mechanism before 
proceeding in this way.  We also need a way to enable any core reviewer to 
trigger a vote on a policy change (we do this informally now by allowing any 
core reviewer to trigger a vote on the mailing list by tagging an email 
[kolla][vote] with the proposed policy change)

For core reviewer nomination votes (our most important votes of all), I’d like 
to keep the full transparency we have with the current mailing list voting 
mechanism in use.  (mailing list easier to follow then watching a poll result 
come in).  This is standard practice in OpenStack and not something we want to 
deviate from.

Also a note to others: I am pretty sure we have more than 9 sessions available 
in total.  We also have been granted space for a  half day contributor meetup.  
Civs says only 9 spots are available.  This applies even if we choose to give 1 
or 2 sessions back to the foundation for emerging projects which need planning 
and coordination time at summit so these projects have a level playing field.

Regards
-steve


On 9/21/16, 1:40 PM, "Michał Jastrzębski" <inc...@gmail.com> wrote:

    Sure, I simply pasted what was in the etherpad. I didn't want to cut
    anything out as some things might be seemingly closed but people in
    fact would like to talk more about them. Let see how priorities will
    look like after couple days:)
    
    Also, please vote!
    
    On 21 September 2016 at 12:54, Swapnil Kulkarni <cools...@gmail.com> wrote:
    > On Wed, Sep 21, 2016 at 11:16 PM, Steven Dake (stdake) <std...@cisco.com> 
wrote:
    >> One note in this poll.  Repo-split has already reached a consensus 
decision via ml vote, and the activity around that will happen prior to summit, 
so it is probably worth ignoring entirely.
    >>
    >> Regards
    >> -steve
    >>
    >>
    >> On 9/21/16, 10:14 AM, "Michał Jastrzębski" <inc...@gmail.com> wrote:
    >>
    >>     Hello,
    >>
    >>     Now, when we have full list of sessions, let's prioritize them
    >>     accordingly to our preferences. Based on this we'll allocate our
    >>     summit space.
    >>
    >>     
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_8368e1e74f8a0049&akey=91bbcf4baeff0a2f
    >>
    >>     
__________________________________________________________________________
    >>     OpenStack Development Mailing List (not for usage questions)
    >>     Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    >>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
    >>
    >>
    >>
    >> 
__________________________________________________________________________
    >> OpenStack Development Mailing List (not for usage questions)
    >> Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
    >
    >
    > I agree. We already devoted a couple of sessions (or more) in Austin
    > design summit and couple of polls on ML thread.
    >
    > __________________________________________________________________________
    > OpenStack Development Mailing List (not for usage questions)
    > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
    
    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
    


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to