<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/22/2014 09:02 PM, Anne Gentle
wrote:<br>
</div>
<blockquote
cite="mid:CAD0KtVEk5GxG1nnRMLob=YQ6wWVwKFvA+hD4YGJ3rBUSYtk9Sg@mail.gmail.com"
type="cite">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div><br>
</div>
</div>
/flame-on<br>
Let's call spades, spades here. Czar is not only overkill, but
the wrong metaphor.<br>
/flame-off<br>
</blockquote>
<div><br>
</div>
<div>I'm with Rocky on the anti-czar-as-a-word camp. We all like
clever names to shed the "corporate" stigma but this word ain't
it. Liaison or lead?
<div><br>
</div>
<div>Also wanted to point to <a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/PTLguide"
target="_blank">https://wiki.openstack.org/wiki/PTLguide</a> as
it's quite nice.</div>
</div>
</blockquote>
<br>
<br>
In the Linux Kernel world they are called Lieutenants, but they are
per sub system. I'm guessing that is more like the PTL role
today. THe etymology is good, to, as a Lieutenant is one who
"stands in Lieu of the commander."<br>
<br>
I think that some projects probably need to divvy up the roles along
different line. For example, in Keystone, we have KVS, SQL and LDAP
backends. Morgan's been the KVS guy due to rewriting things for
Dogpile, and I've been kind of the LDAP guy since I was originally
responsible for that. I suspect the same is true of other projects.<br>
<br>
Many of the roles you listed (Bug, etc) are straight PTL
responsibilities in my book. What is lacking is a structure over
delegating out some subset of that responsibility: no regular bug
triage meeting, etc. I'd rather not throw all bug-triage onto one
persons shoulders, as it really should be a team effort.<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>