S Page wrote:
Hey, I really want to help the Wine project out by sharing my problems and workarounds.
But having to register FOUR TIMES on the same winehq.com site (bugs, AppDB, forums, wiki) is excruciatingly painful and hostile to your would-be contributors. I realize you're just using open source tooling, but maybe you can press those four products to a) implement a single sign-on b) support OpenID
Thanks,
=S Page
Strangely enough, I was just talking about this today at the Community Leadership Summit. Unfortunately it seems like it's a pretty difficult problem to solve as the tools to get all these things talking to eachother haven't been written. There are packages that integrate a forum and a wiki and such together, but they don't provide an easy way to get the data out of them - switching to them also presents huge data migration issues.
Mozilla are farthest on the game here, as they were working on writing some of their own custom stuff based on OpenID, however that then deals with the need of having each app support an OpenID login.
I'm not sure if it's a good idea, but there may be some merit in having one of the accounts function as an OpenID Provider and then have the others be able to link to it (but still be "separate accounts"). After that it's just about being able to login by OpenID rather than have a single account moving across each place.
Thanks, Scott Ritchie
On Sun, Jul 19, 2009 at 10:35 PM, Scott Ritchiescott@open-vote.org wrote:
Mozilla are farthest on the game here, as they were working on writing some of their own custom stuff based on OpenID, however that then deals with the need of having each app support an OpenID login.
I'm not sure if it's a good idea, but there may be some merit in having one of the accounts function as an OpenID Provider and then have the others be able to link to it (but still be "separate accounts"). After that it's just about being able to login by OpenID rather than have a single account moving across each place.
Based upon my recollection there was a lot of contempt for OpenID at the last wineconf. Maybe the situation has changed recently...
Thanks
On Mon, Jul 20, 2009 at 4:50 PM, Steven Edwardswinehacker@gmail.com wrote:
On Sun, Jul 19, 2009 at 10:35 PM, Scott Ritchiescott@open-vote.org wrote:
I'm not sure if it's a good idea, but there may be some merit in having one of the accounts function as an OpenID Provider and then have the others be able to link to it (but still be "separate accounts"). After that it's just about being able to login by OpenID rather than have a single account moving across each place.
Based upon my recollection there was a lot of contempt for OpenID at the last wineconf. Maybe the situation has changed recently...
Was the contempt for OpenID in general, or the idea of using an existing third party as an OpenID providers? Although it would be against the spirit of OpenID, it would be possible for one WineHQ service to provide OpenID only to other WineHQ services, and for them to only accept an OpenID from that particular WineHQ provider. This would be no better than other single-sign-on solutions, but there are a lot more open source cross-framework implementations of OpenID available than for most other solutions.
On Mon, Jul 20, 2009 at 5:21 PM, Sparrsparr0@gmail.com wrote:
Was the contempt for OpenID in general, or the idea of using an existing third party as an OpenID providers? Although it would be against the spirit of OpenID, it would be possible for one WineHQ service to provide OpenID only to other WineHQ services, and for them to only accept an OpenID from that particular WineHQ provider. This would be no better than other single-sign-on solutions, but there are a lot more open source cross-framework implementations of OpenID available than for most other solutions.
I think its best if the google contingent answer that. Dan had some issues with it I think but I don't know if any of them are still applicable.
Thanks
-
Scott Ritchie -
Sparr -
Steven Edwards