<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr">I've been toying with send this email for a while, but here goes: this all feels like overcomplication and changing of a system that doesn't really need to change.
<div><br>
</div>
<div>I've read the pros and cons, and I still can't really see a convincing reason not to move the PTL election to just-before-PTG, so that the new PTL is present for one development cycle as before. If the bigger projects want to have "release stewards" (which
again, seems to be a fancy term for "current PTL" and "stable PTL") then they should be able to do that with the current model anyway. I think this preferable because it prevents any disconnect from either A) an election mid way through development and B)
and election that isn't actually in effect until 3 months later.</div>
<div><br>
</div>
<div>I think the PTG/Forum change is already generating some confusion amongst management and organisations that are outside of core upstream development (as in, not 100% upstream work), and I think trying to shake up project organisation is just going to make
things more confusing. I don't imagine I'm the only person reading through this thread and just wondering "why?".</div>
<div><br>
</div>
<div>I absolutely agree that encouraging people to take leadership roles and responsibility within their community is a great thing, but I don't think this really achieves it. That's down to the projects to change their culture, rather than just adding new
roles and hoping for the best :)<br>
<br>
Rob</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 9 September 2016 at 10:00, Thierry Carrez <span dir="ltr">
<<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sean Dague wrote:<br>
> [...]<br>
<span class="">> I'm also not very concerned about delayed authority of the PTL. Peaceful<br>
> handoff should be a pretty basic tenant in projects. Knowing about it<br>
> for a longer time shouldn't be a big deal. If it causes giant strife to<br>
> pass the torch from one PTL to the next there is something else going<br>
> wrong in that project. In the few cases I'm familiar with in which a<br>
> standing PTL lost an election, the relationship between that PTL and the<br>
> PTL-next was fine.<br>
><br>
> Again, these are personal experiences from the projects I'm actively<br>
> involved with, or collaborate with the most.<br>
<br>
</span>I think that we are in alignment in 98% of what's proposed here.<br>
Elections would still be run in the weeks prior to the summit. I'm<br>
saying that there should be release stewards and by default it would be<br>
the PTL. You are saying there should be PTLs with release duties, but<br>
they can still delegate that. That's nearly the same thing.<br>
<br>
The two differences are:<br>
- defining "release stewards" as a thing slightly encourages PTLs to<br>
delegate the role.<br>
- the transfer of the ultimate tie-breaking/veto authority of the PTL<br>
happens at election time in my case (as defined in the TC charter),<br>
while you suggest it happens 3 months later, when development on N+1 starts.<br>
<br>
One thing to note is that unless someone proposes a TC charter change<br>
during Ocata, the authority of the newly-elected PTL starts at election<br>
time, since the charter only recognizes one PTL at a time.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><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>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>