sounds good to me.<br><br><div class="gmail_quote">On Fri, Jul 23, 2010 at 9:31 AM, Chris Messina <span dir="ltr"><<a href="mailto:chris.messina@gmail.com">chris.messina@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I like David's suggestion to have the patch reviewed on the list. With<br>
sufficient +1's (where deficient should be defined flexibly), the<br>
patch should be accepted.<br>
<br>
Transparency is important, but so is getting momentum behind cleaning<br>
up the libraries! (which was a prime motivator for moving to GitHub).<br>
<font color="#888888"><br>
Chris<br>
</font><div><div></div><div class="h5"><br>
On Friday, July 23, 2010, David Recordon <<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>> wrote:<br>
> Which is why I'm thinking that sending the patch to this list will give a variety of people the ability to review it. :)<br>
><br>
> On Fri, Jul 23, 2010 at 9:26 AM, Will Norris <<a href="mailto:will@willnorris.com">will@willnorris.com</a>> wrote:<br>
> actually doing a standard fork + pull request in github will work fine. I think when you do the pull request you can specify who you want it to be sent to.<br>
><br>
> We have been generally unresponsive to these in the past, but for me that has primarily been due to a lack of leadership on the libraries. By that I mean, no one has really taken ownership of any of the libraries since we moved them into github. JanRain has continued to do minor patches, which is great. And I've been in the process of cleaning up the unit tests for the PHP library, and beginning to write a contributor's guide. But that only answers the technical questions of what you need to do in order to submit a patch. I still don't know who the right people are to actually decide what gets committed. As much as I'd like to, I can't commit to taking on this role at this time. And even then, I'd only be comfortable doing it for PHP. I don't know who would take the lead on Python or Ruby.<br>
><br>
><br>
><br>
> Perhaps I'm over thinking it, I don't know.<br>
> -will<br>
><br>
> On Thu, Jul 22, 2010 at 10:41 PM, David Recordon <<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>> wrote:<br>
> Hey Jon, as there isn't really a lot of active development, the best might be to attach the patches to this thread. I'm cc'ing both Will and Luke who have hacked on the library in the past. Thanks again for helping make it better!<br>
><br>
><br>
><br>
><br>
> --David<br>
><br>
> On Thu, Jul 22, 2010 at 12:24 AM, Jon Spriggs <<a href="mailto:jon@spriggs.org.uk">jon@spriggs.org.uk</a>> wrote:<br>
><br>
> Hi everyone.<br>
><br>
> I've been going over my error logs, and have found a couple of PHP<br>
> warnings and errors when acting as a consumer in the OpenID PHP<br>
> library. I'd like to request that these updates be pulled into the<br>
> tree, but I don't know who to notify when I've made some tweaks. Would<br>
> it be possible to make the workflow clear, so that drive-by<br>
> contributors like myself can make patches?<br>
><br>
> All the best,<br>
> --<br>
> Jon "The Nice Guy" Spriggs<br>
> _______________________________________________<br>
> Code mailing list<br>
> <a href="mailto:Code@lists.openid.net">Code@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-code" target="_blank">http://lists.openid.net/mailman/listinfo/openid-code</a><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
<br>
</div></div><div><div></div><div class="h5">--<br>
Chris Messina<br>
Open Web Advocate, Google<br>
<br>
Personal: <a href="http://factoryjoe.com" target="_blank">http://factoryjoe.com</a><br>
Follow me on Buzz: <a href="http://buzz.google.com/chrismessina" target="_blank">http://buzz.google.com/chrismessina</a><br>
...or Twitter: <a href="http://twitter.com/chrismessina" target="_blank">http://twitter.com/chrismessina</a><br>
<br>
This email is: [ ] shareable [X] ask first [ ] private<br>
<br>
</div></div></blockquote></div><br>