<div dir="ltr">+1<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 22, 2018 at 1:09 PM, David Davis <span dir="ltr"><<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1</div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div class="m_1747401555543934736gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div></font></span><div><div class="h5">
<br><div class="gmail_quote">On Tue, May 22, 2018 at 12:37 PM, Jeff Ortel <span dir="ltr"><<a href="mailto:jortel@redhat.com" target="_blank">jortel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font size="-1"><font face="DejaVu Sans">Thanks for the proposal,
Brian. Looks fine to me.</font></font><div><div class="m_1747401555543934736h5"><br>
<br>
<div class="m_1747401555543934736m_-1704744546779871602moz-cite-prefix">On 05/21/2018 04:48 PM, Brian Bouterse
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="m_1747401555543934736h5">
<div dir="ltr">
<div>For core and it's related tools, we don't have a written
process to describe giving the commit bit to a contributor.
We've been wanting to agree on and document that process for a
while, so I'm facilitating thread gathering ideas to inform
the writing of a PUP.</div>
<div><br>
</div>
<div>This starter email gives a brief history of what we've done
and outlines a simple proposal to get us started. We can throw
that proposal away in favor of any other idea.</div>
<div><br>
</div>
<div># History</div>
<div><br>
</div>
<div>Historically if you were hired onto the Pulp team at Red
Hat you received the commit bit day 0. In Oct 2017 we decided
to stop doing that and instead document an open process.
Engineers hired on the pulp time since Oct '17 have not
received commit bit. We have not yet documented an open
process of which to give it to them or any other proven
contributor.<br>
</div>
<div><br>
</div>
<div># Current State</div>
<div><br>
</div>
<div>The current core devs as shown on github are: asmacdo,
bizhang, bmbouter, daviddavis, dkliban, dalley, ipanova,
jortel, pcreech, ttereshc</div>
<div><br>
</div>
<div># Scope of this discussion</div>
<div><br>
</div>
<div>pulp/pulp, pulp/devel, and any repos for the Pulp3 Ansible
installer. It applies to both Pulp2 and Pulp3. Plugins will do
what they want.</div>
<div><br>
</div>
<div># Process Idea<br>
</div>
<div><br>
</div>
<div>One process idea is to add a new core committer upon a vote
with +1's received from all current core developers. The
thinking is that all current core devs needs to be 100%
comfortable for the new person to handle any issue in place of
themselves.<br>
</div>
<div><br>
</div>
<div># Criteria</div>
<div><br>
</div>
<div>Overall I believe someone who has demonstrated commitment
and care towards the needs of all Pulp users and not only
their own interests. Also they must have the experience to be
trusted with major aspects of Pulp functionality.<br>
</div>
<div><br>
</div>
<div>These requirements are somewhat vague by design. Any
process with hard requirements will be gamed so I believe
leaving it to the judgement of the existing devs is a safe
approach. Anyone who specifically wants to get more involved
should approach the core devs about mentorship. I think the
right time will be obvious, and if there are doubts those can
be expressed ahead of time or at vote time.</div>
<div><br>
</div>
<div>
<div># Code owners</div>
<div><br>
</div>
<div>This commit bit vote could be for entire core repos, or
it could be for a subsystem of Pulp enforced using github's
"code owners" feature (<a href="https://blog.github.com/2017-07-06-introducing-code-owners/" target="_blank">https://blog.github.com/2017-<wbr>07-06-introducing-code-owners/</a><wbr>).
</div>
<br>
</div>
<div><br>
</div>
<div>^ is starter content, please send ideas and discussion that
will be incorporated into a first draft PEP at some point.<br>
</div>
<div><br>
</div>
<div>-Brian<br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="m_1747401555543934736m_-1704744546779871602mimeAttachmentHeader"></fieldset>
<br>
</div></div><span><pre>______________________________<wbr>_________________
Pulp-dev mailing list
<a class="m_1747401555543934736m_-1704744546779871602moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>
<a class="m_1747401555543934736m_-1704744546779871602moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a>
</pre>
</span></blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>