<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap:break-word">
<div>Hi Morgan!</div>
<div><br>
</div>
<div>Stackforge projects can be configured to make the CLA optional. I am willing to speak to the HTTPretty maintainers about the benefits of stackforge. Do we happen to know any of them? If not I can track them down through email.</div>
<div><br>
</div>
<div>Adrian</div>
<div><br>
</div>
<div><br>
</div>
<div style="font-size:75%">--</div>
<div style="font-size:75%">Adrian</div>
<br>
<br>
-------- Original message --------<br>
From: Morgan Fainberg <br>
Date:12/04/2013 6:17 PM (GMT-08:00) <br>
To: Jamie Lennox ,"OpenStack Development Mailing List (not for usage questions)" <br>
Subject: Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
<br>
<br>
<div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial; font-size:13px; margin:0px; line-height:auto">
<br>
</div>
<p style="color:#A0A0A8">On December 4, 2013 at 18:05:07, Jamie Lennox (<a href="mailto://jamielennox@redhat.com">jamielennox@redhat.com</a>) wrote:</p>
<div>
<div>
<div>
<blockquote type="cite" class="clean_bq" style="font-family:helvetica; font-size:13px; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; background-color:rgb(255,255,255)">
<span>
<div>
<div><br>
On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote:<span class="Apple-converted-space"> </span><br>
> On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto<span class="Apple-converted-space"> </span><br>
> <adrian.otto@rackspace.com> wrote:<span class="Apple-converted-space"> </span><br>
> Jamie,<span class="Apple-converted-space"> </span><br>
><span class="Apple-converted-space"> </span><br>
> Thanks for the guidance here. I am checking to see if any of<span class="Apple-converted-space"> </span><br>
> our developers might take an interest in helping with the<span class="Apple-converted-space"> </span><br>
> upstream work. At the very least, it might be nice to have<span class="Apple-converted-space"> </span><br>
> some understanding of how much work there is to be done in<span class="Apple-converted-space"> </span><br>
> HTTPretty.<span class="Apple-converted-space"> </span><br>
><span class="Apple-converted-space"> </span><br>
><span class="Apple-converted-space"> </span><br>
> (Dolph correct me if I am wrong, but...)<span class="Apple-converted-space"> </span><br>
><span class="Apple-converted-space"> </span><br>
><span class="Apple-converted-space"> </span><br>
> I don't think that there is much work to be done beyond getting that<span class="Apple-converted-space"> </span><br>
> pull request merged upstream. Dolph ran the tests using the code from<span class="Apple-converted-space"> </span><br>
> the pull request somewhat successfully. The errors that we saw were<span class="Apple-converted-space"> </span><br>
> just in keystoneclient code.<span class="Apple-converted-space"> </span><br>
<br>
But I don't think that there own test suite runs under py33 with that<span class="Apple-converted-space"> </span><br>
branch. So they've hit the main issues, but we won't get a release in<span class="Apple-converted-space"> </span><br>
that state.<span class="Apple-converted-space"> </span></div>
</div>
</span></blockquote>
</div>
<p>Should we offer to bring HTTPretty under something like stackforge and leverage our CI infrastructure? Not sure how open the owner/maintainers would be to this, but it would help to solve that issue… downside is that pull-requests are no longer (gerrit
instead) used and IIRC CLA is still required for stackforge projects (might be a detractor). Just a passing thought (that might be irrelevant depending on the owner/maintainer’s point of view).</p>
</div>
<div><br class="Apple-interchange-newline">
</div>
</div>
<p>—Morgan</p>
<p><br>
</p>
<div></div>
</div>
</body>
</html>