[OpenID] Moving OpenID code repositories

[Chris Messina]

Touché. Good point.

I'd recommend that you go star this issue in order to express your
desire for Google Code to support OpenID:

http://code.google.com/p/support/issues/detail?id=813

And make sure to start #414 to get OAuth support as well:

http://code.google.com/p/support/issues/detail?id=414

As it is, I'm not sure that anyone has actually patched SVN or git to
work with OpenIDs, so whether the repository allow for OpenID
authentication is somewhat moot when it comes to managing source code.
I also just attempted to hook up my OpenID with Sourceforge account
and it wasn't exactly ... user friendly.

But that's besides the point.

My interest is in making it as simple and straightforward as possible
for folks to get the resources that they need to adopt OpenID -- and
so far both Google Code and Github, with their simple, basic designs
and features support that goal -- so I'm with you that it'd be ideal
if either of them supported OpenID, but it's not necessary for this
change to support my original goal.

Chris

On Sun, Oct 5, 2008 at 8:26 PM, Peter Williams <pwilliams at rapattoni.com> wrote:
> Can one login to google code using an openid?
>
> If not, would it not make more sense to endorse a code repository that does?
>
> Perhaps im being disingenuous about money and endorsement politics within the vc community, here. More likely, im just showing my ignorance about google code.
>
> Have openid. Willing to do trial of applying it to access google code project. Any takers?
>
> -----Original Message-----
> From: David Recordon <drecordon at sixapart.com>
> Sent: Sunday, October 05, 2008 8:16 PM
> To: Chris Messina <chris.messina at gmail.com>
> Cc: Josh Hoyt <joshhoyt at gmail.com>; Scott Kveton <scott at kveton.com>; Michael Richardson <michael at gobyairship.com>; OpenID List <general at openid.net>; dlehn at gmail.com <dlehn at gmail.com>
> Subject: Re: [OpenID] Moving OpenID code repositories
>
>
> +1 for Google Code (if this happens), but have you been talking with
> the current library maintainers to see if they would even move their
> code?
>
> --David
>
> On Oct 5, 2008, at 10:26 PM, Chris Messina wrote:
>
>> I've been having conversations with folks about the current OpenID
>> libraries lately and it seems to me that it would be highly valuable
>> to both consolidate the existing [good] libraries, to get more
>> visibility and transparency into their development, to increase the
>> number of contributors, to give the foundation more direct management
>> of the codebase, to open up the support queue, to enable branching,
>> and to also go about creating separate libraries for each respective
>> language, rather than just using ports of the Python libraries.
>>
>> Yes, this is a tall order, but given the experience I've had with
>> pushing the development of OAuth libraries (http://oauth.net/code), I
>> think we need to shift where and how the development happens to get
>> more momentum going and make it easier to manage project access.
>>
>> I propose that we make use of either Google Code or Github. I'm not
>> looking for a religious battle here; I'm personally more familiar and
>> comfortable with Google Code, but Github has proven to be a rather
>> excellent tool for distributed/decentralized development.
>>
>> This request is primarily initiated from conversations I've had in the
>> course of working on the DiSo Project -- both from WordPress and
>> Drupal devs... and from folks who have submitted patches to the
>> openidenabled dev list [1] which have been ignored.
>>
>> Such impressions can lead to lasting impressions, and if anything, we
>> need to radically improve the community and developer footprint of
>> OpenID -- and turn it into a leading open source initiative. Working
>> with top tier tools is the place to start.
>>
>> Now, there's one caveat here that requires a nod from the Sourceforge
>> project maintainers: the Sourceforge project
>> (http://openid.sourceforge.net/) currently redirects to the wiki. This
>> means that the "OpenID" project name is reserved on Google Code, so if
>> we want to make use of that project, the folks who own the Sourceforge
>> project would need to give us the go-ahead to reuse that project name
>> (Google reserved all the Sourceforge project names to prevent
>> squatting).
>>
>> If yes, we can go about getting the projects started up -- perhaps
>> following the architecture of the OAuth repository:
>>
>> http://code.google.com/p/oauth/source/browse/#svn/code
>>
>> I look forward to your thoughts and feedback.
>>
>> Thanks!
>>
>> Chris
>>
>> [1] http://lists.openidenabled.com/mailman/listinfo/dev
>>
>> --
>> Chris Messina
>> Citizen-Participant &
>>  Open Source Advocate-at-Large
>> factoryjoe.com # diso-project.org
>> citizenagency.com # vidoop.com
>> This email is:   [ ] bloggable    [X] ask first   [ ] private
>
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>



-- 
Chris Messina
Citizen-Participant &
  Open Source Advocate-at-Large
factoryjoe.com # diso-project.org
citizenagency.com # vidoop.com
This email is:   [ ] bloggable    [X] ask first   [ ] private