[OpenID board] OpenID on Google Code

[David Recordon]

1) That's certainly a limitation of Google Code though other projects  
have ignored it as an issue with each library having their own license  
within its source code.

2) Sure.

This might be why GitHub is a better choice for source code  
management.  Either way, we have real library maintainers who want to  
move forward with this and are currently blocked on this discussion.

--David

On Apr 9, 2009, at 12:24 PM, Martin Atkins wrote:

> David Recordon wrote:
>> I think it would be fine if you continue doing this for Perl while  
>> the PHP and Python libraries move into a shared project on either  
>> Google Code or GitHub (each has their advantages).  If anything,  
>> I'd encourage the Perl repository to join this shared project while  
>> leaving bug tracking and releases on CPAN and discussion on the  
>> openid-perl mailing list.
>
> There are still some remaining niggles:
>
> * Google Code requires you to specify a source code licence for the  
> whole project. Different libraries are under different licences. The  
> JanRain libraries seem to be Apache Licence while the Perl library  
> is "under the same terms as Perl itself" (i.e. GPL/Artistic dual- 
> licenced.)
>
> * Are all library developers really going to get top-level admin  
> access on a single Google Code project? I can't help but thing that  
> it's simpler to just give each library its own Google Code project  
> and let each project manage its own destiny, and making it easier  
> for the respective maintainers not to trample on each other's toes.
>
> _______________________________________________
> board mailing list
> board at openid.net
> http://openid.net/mailman/listinfo/board