Brian,<div>Thanks for the update. Personally, I much prefer Trac to Google Code's issue tracker and I'm curious about your reasoning for this move. Happy to hear about the move to Git however!</div><div><br></div>
<div>Also, I'm curious about how DotNetOpenId fits into the openid libraries that you're referring to. DNOI has its own git repo already and mailing list, and its own Google Code site, although I've been planning on moving it to Trac soon. If we're trying to collect the libraries support mailing lists and issue tracking for a better user experience though I'd like to see what I can do to support that.</div>
<div><br></div><div>In general, since there may be several OpenID libraries for a given language or platform, is the idea to get them all to be hosted or tracked at the same place (besides <a href="http://wiki.openid.net/Libraries">http://wiki.openid.net/Libraries</a>)?</div>
<div><br></div><div>Thanks.</div><div><br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - Voltaire<br>
<br><br><div class="gmail_quote">2009/3/11 Brian Ellin <span dir="ltr"><<a href="mailto:brian@janrain.com">brian@janrain.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Dear <a href="mailto:dev@openidenabled.com" target="_blank">dev@openidenabled.com</a> list,<br><br>We are joining forces with <a href="http://openid.net/" target="_blank">openid.net</a> to consolidate this list with the new <<a href="mailto:code@openid.net" target="_blank">code@openid.net</a>>
email list. The new list will be home to all things OpenID code and library
related, from library internals to implementation details and
issues. By having a single list for developers hosted at <a href="http://openid.net/" target="_blank">openid.net</a> we hope to build a stronger community around the *all* the available libraries in the OpenID developer community.<br>
<br>To join the new list, please visit: <a href="http://openid.net/mailman/listinfo/code" target="_blank">http://openid.net/mailman/listinfo/code</a><br><br>Additionally,
we are changing the development workflow for the libraries currently hosted and maintained at <a href="http://openidenabled.com" target="_blank">openidenabled.com</a>. Changes to the PHP library workflow include:<br>
<br>* Adding Will Norris (Vidoop/Diso) and Luke Shepard (Facebook) as maintainers of the library.<br>* Git will be used as the new version control system, and the repo will be hosted on github at <a href="http://github.com/bce/php-openid/tree/master" target="_blank">http://github.com/bce/php-openid/tree/master</a>.<br>
* If you are interested in contributing to the library, simply fork the repo on github!<br><br>And soon:<br><br>* Create a home for all OpenID code on <a href="http://code.google.com/" target="_blank">code.google.com</a>,
which will house a bug tracker and wiki for use with the libraries.
This is being spearheaded by Chris Messina and David Recordon, so look
for news on the <a href="mailto:code@openid.net" target="_blank">code@openid.net</a> list for details. We will continue using the trac on <a href="http://openidenabled.com/" target="_blank">openidenabled.com</a> until this happens. This is a GREAT thing for OpenID!<br>
* Apply the new workflow to the Ruby and Python libraries.<br><br>What about <a href="http://openidenabled.com/" target="_blank">openidenabled.com</a>?<br>* <a href="http://openidenabled.com/" target="_blank">openidenabled.com</a> will still run the tests at <a href="http://openidenabled.com/resources/openid-test/" target="_blank">http://openidenabled.com/resources/openid-test/</a><br>
* the live demos will also continue to run, as they are handy for testing out implementations: <a href="http://openidenabled.com/php-openid/trunk/examples/consumer/" target="_blank">http://openidenabled.com/php-openid/trunk/examples/consumer/</a><br>
* The ruby and python darcs repositories and release workflow will stay on <a href="http://openidenabled.com/" target="_blank">openidenabled.com</a> for the time being.<br>* The PHP darcs repo will remain available for now, though patches to the git repos will not be available in the darcs repos.<br>
* New PHP releases will continue to be made available on <a href="http://oepnidenabled.com/" target="_blank">openidenabled.com</a> until the new home on <a href="http://code.google.com/" target="_blank">code.google.com</a> exists, at which point releases will be distributed there.<br>
<br>Cheers,<br><font color="#888888">Brian Ellin<br>JanRain, Inc.<br><br>
</font><br>_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@lists.openidenabled.com">Dev@lists.openidenabled.com</a><br>
<a href="http://lists.openidenabled.com/mailman/listinfo/dev" target="_blank">http://lists.openidenabled.com/mailman/listinfo/dev</a><br>
<br></blockquote></div><br></div>