<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 19, 2014 at 6:13 AM, 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">Sean Dague wrote:<br>
> Honestly, if we are going to track this, we should probably do the set<br>
> of things that reviewers tend to do when running through these.<br>
><br>
> License:<br>
> Upstream Location:<br>
> Ubuntu/Debian Package: Y/N? (url)<br>
> Fedora Package: Y/N? (url)<br>
> Suse Package: Y/N? (url)<br>
> Last Release: Date (in case of abandonware)<br>
> Python 3 support: Y/N? (informational only)<br>
><br>
> I'd honestly stick that in a yaml file instead, and have something<br>
> sanity check it on new requirements add.<br>
<br>
</div>Licensing is the only legally-binding issue at stake, the rest are<br>
technically-binding issues that we consider when we accept or reject a<br>
new dependency. I'm not saying there is no value in tracking that extra<br>
information, just saying that we really need to track licensing. I don't<br>
want perfection to get in the way of making baby steps towards making<br>
things better.<br>
<br>
Tracking licensing is a good first step, and having full licensing<br>
coverage will take some time. We shouldn't block on YAML conversion or<br>
full technical information... As a first step let's just accept patches<br>
that mention licensing information in trailing comments, then if someone<br>
wants to convert the requirements files to YAML so that they can contain<br>
more information, great!<br></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">I added a note about this to the review criteria list [1].</div><div class="gmail_default" style="font-size:small">
<br></div><div class="gmail_default" style="font-size:small">Doug<br></div><br></div><div><div class="gmail_default" style="font-size:small">[1] <a href="https://wiki.openstack.org/wiki/Requirements#Review_Criteria">https://wiki.openstack.org/wiki/Requirements#Review_Criteria</a></div>
<div class="gmail_default"><br></div><div class="gmail_default" style="font-size:small"></div><br></div><div> </div><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">

<span class=""><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
<br>
</font></span><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>