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. <div><br></div><div>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.</div>
<div><br></div><div>Perhaps I'm over thinking it, I don't know.</div><div><br></div><div>-will<br><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 10:41 PM, David Recordon <span dir="ltr"><<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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!<div>
<br></div><font color="#888888"><div>--David</div></font><div><div></div><div class="h5"><div><br><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 12:24 AM, Jon Spriggs <span dir="ltr"><<a href="mailto:jon@spriggs.org.uk" target="_blank">jon@spriggs.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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>
<font color="#888888">--<br>
Jon "The Nice Guy" Spriggs<br>
_______________________________________________<br>
Code mailing list<br>
<a href="mailto:Code@lists.openid.net" target="_blank">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>
</font></blockquote></div><br></div>
</div></div></blockquote></div><br></div>