<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Ubuntu">Hi Donald, all</font></p>
<p><font face="Ubuntu">As discuss yesterday on Slack, here it is my
proposal to manage Pull Request to be discuss during the audio.</font></p>
<p>Regards</p>
<p>Olivier</p>
<p>--- FRR Pull request management ---</p>
<p> - Once a Pull Request is submitted, it is assigned to a code
reviewer. The code reviewer has 2 weeks to review the code and
commit it into the master. If the assigned code reviewer is too
busy to manage the Pull Request he must delegate the review to
another person within 3 days.</p>
<p> - Code reviewer has not necessary the right to commit directly
the code. If he hasn't the right, a maintainer could do that once
the review is done and the Pull request accepted.</p>
<p> - Code reviewer is responsible to interact with the owner of the
Pull Request if modifications are necessary</p>
<p> - Code reviewers are designate based on volunteer who explicitly
indicate which part of the code he/she is confident and able to
review<br>
</p>
<p> - To start, helping people becoming a code reviewer and
facilitate Pull request assignation to a code reviewer, we could
fulfil the following table, which is give as example. The idea is
at least to split the project into its various routing protocols
and some transverses functions.<br>
</p>
<table border="0" cellpadding="2" cellspacing="2" width="500">
<tbody>
<tr>
<td valign="top">FRR Code<br>
</td>
<td valign="top">Primary Reviewer<br>
</td>
<td valign="top">Backup Reviewer<br>
</td>
</tr>
<tr>
<td valign="top">bgpd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">isisd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">ldpd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">lib<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">ospf6d<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">ospfd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">pimd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">ripd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">ripngd<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">vtysh<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">zebra<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">packaging<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">compilation<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<td valign="top">tools<br>
</td>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
</tbody>
</table>
<p><br>
</p>
<div class="moz-cite-prefix">Le 10/01/2017 à 14:43, Donald Sharp a
écrit :<br>
</div>
<blockquote
cite="mid:CAK989yfwhJWZWg=5A02Z24PnLOcNFF0p-P1cQ_HJ3J6PewcYvw@mail.gmail.com"
type="cite">
<pre wrap="">1) Status
2) Pull Request : <a class="moz-txt-link-freetext" href="https://github.com/freerangerouting/frr/pull/44">https://github.com/freerangerouting/frr/pull/44</a>
-> RD/RT cli discussion
-> Functionality how does this properly fit into vnc?
3) Anything else?
donald
_______________________________________________
frr mailing list
<a class="moz-txt-link-abbreviated" href="mailto:frr@lists.nox.tf">frr@lists.nox.tf</a>
<a class="moz-txt-link-freetext" href="https://lists.nox.tf/listinfo/frr">https://lists.nox.tf/listinfo/frr</a>
</pre>
</blockquote>
<br>
</body>
</html>