Enable login via openID. If there's any demographic that understands openID, it's developers, so you've already got the perfect audience.
Cart before the horse? Get the forges and source control engines to support OpenID. Then when you contribute to open source and claim it here, it actually means something.
I rather think of it as tool before the engine. OpenID is not something to push top-down into the community. It has to be deployed bottom-up.
Although I am not quite sure what would happen to existing accounts and whether upgrades would be possible I vote for it. This would be nice.
Yes, this would be a good thing. Ohloh helps associate you with your work; it's a natural step to be want to link an Ohloh profile to an OpenID identity, in the absence of a firmer way of proving the connection between you and your code.
If you do implement this, consider allowing a user to register multiple OpenIDs to their account, and have it in addition to password auth.
Count my vote for OpenID login!
Sourceforge have just moved on this, and seem to have done it pretty comprehensively for their web front-end.
However, you still need a local account and username/password for accessing the version control repositories.
I recommend to add this as a additional auth method not as default.
Vote for OpenID.
Just another vote for OpenID. I considered not registering when I saw I couldn't use it.
I'm pretty amazed that Ohloh doesn't support OpenID, since they seem to be otherwise technically proficient.
I have used Ohloh anonymously for a while now, but never considered registering here. I only registered now to be able to register my software project. Now that I've done that, I would consider deleting my account, but that is not even possible. It's the old lock-in strategy again. Maybe it's no wonder they don't support OpenID...
there is no excuse not to have openid anymore!
Could someone from the site's team give some info on this subject, PLEASE?
I bet that Ohloh will come out with a big announcement "We support OpenID!", and it will turn out to be just as an OpenID producer, not a consumer. Which would be a pointless exercise.
It seems a common pattern; many sites wants their site to be the primary site, so everyone implements OpenID identities connected to the site's accounts but not logins to accounts using OpenIDs from other sites. But doing this is selfish, stupid, pointless and ultimately self-defeating, since this makes OpenID itself meaningless.
Maybe I'm just cynical, but we will see.
This should be a sticky topic, by the way :)
Although we have no definite plans to add OpenID support right now, it is something that we would like to do in the fullness of time.
Widespread adoption of OpenID is actually very good for a site like Ohloh, and we've investigated adding the feature before. At this point it comes down to balancing the immediate needs of the keeping Ohloh running versus all the cool things we'd like to add.
@Teddy, speaking for myself personally, I think it's lame when companies use OpenID as a pretense to corner the market on single sign-on. That's contrary to the whole point of OpenID. When it comes, Ohloh will be an OpenID consumer.
I was pleasantly surprised to see your response, but I hold little hope until I can see it actually implemented.
As it is, if I may play devil's advocate again, you might say that Ohloh is currently worse than OpenID-provider-only sites, since those sites at least acknowledges that other sites exist and are useful. With Ohloh only having Ohloh-specific accounts, it's like they're saying "Thou shalt visit no other sites except Ohloh".
I hope you guys are still looking at this. I've had great experience implementing login with OpenID on an existing webapp of mine; I created a table called "openids" and I'm filling it with account name / openid associations. One account can have multiple OpenIDs.
Using Janrain libraries it should be trivial to create such a simple implementation. Targetting Google and Yahoo! logins is most difficult and is a best stress test for an OpenID implementation.
For a great reference implementation on "how developer sites should solve login", see StackOverflow. Great OpenID implementation is also present at Plaxo.
To me, OpenID provides a great relief from burden of dozens of passwords. It also provides me a single click sign-on, especially with OpenID2.0 and my Google account. (C'mon, it can't get easier than clicking on a big button labeled "Google" and being logged in :) )
Please support OpenID; I've become spoiled by its ease of use lately.
Oh, and thanks guys for all the stuff you're doing on Ohloh! :)
When a site doesn't have OpenID enabled I hesitate for quite a while if I will give it a try. Please enable OpenID =)
We hear you on this enhancement! As Robin said in his reply, adding OpenID support is something we'd like to explore. So I'm re-activating this thread to gather more input from you all on how you'd want OpenID to work on ohloh. We have a few questions:
Just making ohloh use OpenID as an alternative to name/password is probably a doable task. Making people's identities across different sites match up, and using that match to improve ohloh's attribution of contributions etc. may be a much bigger task, and the developer ecosystem may not be up to it yet. Do you think that OpenID is adopted widely enough to be the answer? Is this sort of unified ID across developer sites a good idea? Are there privacy implications? Please comment - we're listening!
“Should OpenID be the only way to log in to ohloh, or should it be an alternative to standard name/password? Which should be the default?”
I would not mind OpenID being the only way to log in. It should definitely be the default.
“How would you want ohloh to handle people who have multiple OpenIDs that they use on different developer sites? How widespread is that case?”
Have the possibility to register multiple OpenIDs and log in with any one of them.
+1 for openid support.
Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.