- From: elf Pavlik <perpetual-tripper@wwelves.org>
- Date: Thu, 09 Feb 2012 11:40:01 +0000
- To: public-webid <public-webid@w3.org>
Excerpts from Melvin Carvalho's message of 2012-02-09 10:57:12 +0000: > Had a chat with Henry lately and we were wondering about what steps > would help gain wider adoption. > > Of course everyone is doing their little bit, some people working on > identity providers, some working on apps, some working on the spec, > some working on integration, some on frameworks, some working on > outreach. All of this is really positive in taking the WebID > ecosystem forward. > > Some of us have been doing WebID for quite a while now, and naturally > we all have a subjective perspective on the best ways to make WebID > more popular > > But maybe we are at the point where we can, as a group, brainstorm > possible concrete strategies for how WebID can gain wider adoption. > > Does any one strategy stand out? I would like to make it easy to add as one of available login options, and for that have 'strategies' available for many frameworks like: node.js - passport, everyauth rails - omniauth django - allauth as well as modules/plugins for drupal/wordpress/elgg etc. than also helping with enabling it in popular open platforms like statusnet, diaspora and maybe others listed in: http://libreprojects.net/ so here documentation on implementing webid will become very important! since I have mostly work with ruby, possibly could at some point help in diaspora, rstatus, redmine/bettermeans, shapado and maybe some other listed at: http://www.opensourcerails.com/ most likely trying to at the same time enable in them WebID, BrowserID and OpenID, but using all/every/ominauth like libraries should make it relatively easy and extensible... =) ~ elf Pavlik ~
Received on Thursday, 9 February 2012 11:40:26 UTC