Agreed with Will. (And this is an issue for specs@, not board@.)<div><br><div class="gmail_quote">On Sun, Dec 27, 2009 at 8:41 PM, Will Norris <span dir="ltr"><<a href="mailto:will@willnorris.com">will@willnorris.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I'm not sure that it needs to be either/or. We have the 'openid' account secured on github, bitbucket, and google code. Let individual working groups use whichever version control system they are most comfortable with. Of course the final deliverables that come out of any working group should be in common location (such as <a href="http://openid.net/developers/specs/" target="_blank">http://openid.net/developers/specs/</a>), but that doesn't necessarily mean that they all need to use the same technology to develop them.<br>
<br>
-will<br>
<div><div></div><div class="h5"><br>
On Dec 26, 2009, at 6:57 PM, Nat Sakimura wrote:<br>
<br>
> David and Allen,<br>
><br>
> I suppose we should ask the wider community, so I am including board@<br>
> in the distribution list.<br>
><br>
> For those of you who are new to this topic, we have been<br>
> "experimenting/trying a move to" github from svn. However, after<br>
> having used it for sometime, I have started to find some problems with<br>
> github and it now looks to me that <a href="http://bitbucket.org" target="_blank">bitbucket.org</a> is a better option<br>
> than github.<br>
><br>
> The reasons are:<br>
><br>
> 1. It uses OpenID for web interface login.<br>
> 2. It allows the use of https logins through proxies so it can be<br>
> accessed through corporate firewalls etc. as well. (It is extremely<br>
> difficult to do this for github -- it can be done, but it probably is<br>
> beyond many people because you need to build a tunnel through the<br>
> proxy.)<br>
> 3. It allows CNAMEs when paid US$5 a month, so that it could be<br>
> accessed as <a href="http://openid.net" target="_blank">openid.net</a>., e.g., <a href="http://specs.openid.net/ax/" target="_blank">http://specs.openid.net/ax/</a> -><br>
> <a href="http://bitbucket.org/openid/ax/" target="_blank">http://bitbucket.org/openid/ax/</a> This is kind of vanity thing, but is<br>
> important to establish the "authenticity" of the repository to the<br>
> public.<br>
><br>
> For our use, I have secured account "openid" at bitbucket.<br>
><br>
> What would you think?<br>
><br>
> =nat<br>
><br>
> On Sat, Dec 26, 2009 at 5:56 PM, Nat <<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>> wrote:<br>
>> One problem that I found about github is that it is very difficult to<br>
>> configure it to work with corporate proxies. We started to use github for<br>
>> translation project as well, but several members got stack there. Do you<br>
>> know of a work around?<br>
>><br>
>> =nat@Tokyo via iPhone<br>
<br>
</div></div>_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
</blockquote></div><br></div>