Open Stack

Michal,

Another option is 2 individuals from each core review team + PTL.  That is lighter weight then 3 and 4, yet more constrained then 1 and 2 and would be my preferred choice (or alternatively 3 or 4).  Adding a deliverable is serious business ☺

FWIW I don’t’ think we are at an impasse, it just requires a policy vote as we do today.

Regards
-steve

-----Original Message-----
From: Michał Jastrzębski <inc007 at gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Wednesday, January 4, 2017 at 3:38 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [tc][kolla] Adding new deliverables

    Hello,
    
    New deliverable to Kolla was proposed, and we found ourselves in a bit
    of an impasse regarding process of accepting new deliverables. Kolla
    community grew a lot since we were singular project, and now we have 3
    deliverables already (kolla, kolla-ansible and kolla-kubernetes). 4th
    one was proposed, kolla-salt, all of them having separate core teams
    today. How to we proceed with this and following deliverables? How to
    we accept them to kolla namespace? I can think of several ways.
    
    1) Open door policy - whoever wants to create new deliverable, is just
    free to do so.
    2) Lightweight agreement - just 2*+2 from Kolla core team to some list
    of deliveralbes that will sit in kolla repo, potentially 2*+2 + PTL
    vote it would be good for PTL to know what he/she is PTL of;)
    3) Majority vote from Kolla core team - much like we do with policy
    changes today
    4) Majority vote from all Kolla deliverables core teams
    
    My personal favorite is option 2+PTL vote. We want to encourage
    experiments and new contributors to use our namespace, for both larger
    community and ease of navigation for users.
    
    One caveat to this would be to note that pre-1.0 projects are
    considered dev/experimental.
    
    Thoughts?
    
    Cheers,
    Michal
    
    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev