<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 5, 2017 at 8:58 AM, Sam Yaple <span dir="ltr"><<a href="mailto:samuel@yaple.net" target="_blank">samuel@yaple.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Involving kolla-ansible and kolla-kubernetes in a decision about kolla-salt (or kolla-puppet, or kolla-chef) is silly since the projects are unrelated. That would be like involving glance when cinder has a new service because they both use keystone. The kolla-core team is reasonable since those are the images being consumed.<div><br></div></div></blockquote><div><br></div><div>Technically, I think if there was going to be a puppet module for kolla, it should fall under the Puppet OpenStack namespace (as puppet-kolla). So in this case kolla-salt is only falling under the kolla namespace because there's no longer a salt group in OpenStack right? I don't have any skin in the kolla game, but I would encourage a puppet-kolla if someone wanted to contribute :) Just to add my thoughts on the original question posed by this thread as an outside observer, I would echo what <span style="font-size:12.8px">Michal said</span> since the PTL should at the very least have a say.</div><div><br></div><div>Thanks,</div><div>-Alex</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>Thanks,</div><div>SamYaple<span class="gmail-HOEnZb"><font color="#888888"><br><div><br></div><div><br></div></font></span></div></div><div class="gmail_extra"><span class="gmail-HOEnZb"><font color="#888888"><br clear="all"><div><div class="gmail-m_-76419234921966976gmail_signature"><div dir="ltr"><div>Sam Yaple</div></div></div></div></font></span><div><div class="gmail-h5">
<br><div class="gmail_quote">On Thu, Jan 5, 2017 at 12:31 AM, Steven Dake (stdake) <span dir="ltr"><<a href="mailto:stdake@cisco.com" target="_blank">stdake@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Michal,<br>
<br>
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 ☺<br>
<br>
FWIW I don’t’ think we are at an impasse, it just requires a policy vote as we do today.<br>
<br>
Regards<br>
-steve<br>
<div class="gmail-m_-76419234921966976HOEnZb"><div class="gmail-m_-76419234921966976h5"><br>
-----Original Message-----<br>
From: Michał Jastrzębski <<a href="mailto:inc007@gmail.com" target="_blank">inc007@gmail.com</a>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a>><br>
Date: Wednesday, January 4, 2017 at 3:38 PM<br>
To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack<wbr>.org</a>><br>
Subject: [openstack-dev] [tc][kolla] Adding new deliverables<br>
<br>
Hello,<br>
<br>
New deliverable to Kolla was proposed, and we found ourselves in a bit<br>
of an impasse regarding process of accepting new deliverables. Kolla<br>
community grew a lot since we were singular project, and now we have 3<br>
deliverables already (kolla, kolla-ansible and kolla-kubernetes). 4th<br>
one was proposed, kolla-salt, all of them having separate core teams<br>
today. How to we proceed with this and following deliverables? How to<br>
we accept them to kolla namespace? I can think of several ways.<br>
<br>
1) Open door policy - whoever wants to create new deliverable, is just<br>
free to do so.<br>
2) Lightweight agreement - just 2*+2 from Kolla core team to some list<br>
of deliveralbes that will sit in kolla repo, potentially 2*+2 + PTL<br>
vote it would be good for PTL to know what he/she is PTL of;)<br>
3) Majority vote from Kolla core team - much like we do with policy<br>
changes today<br>
4) Majority vote from all Kolla deliverables core teams<br>
<br>
My personal favorite is option 2+PTL vote. We want to encourage<br>
experiments and new contributors to use our namespace, for both larger<br>
community and ease of navigation for users.<br>
<br>
One caveat to this would be to note that pre-1.0 projects are<br>
considered dev/experimental.<br>
<br>
Thoughts?<br>
<br>
Cheers,<br>
Michal<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div></div>