I think that Stian raises a key point here: we'd not just use LDAP / custom made identity management for the a one-off but for automatically connecting users with other P2PU hosted services in an <i>ongoing</i> basis and allowing consistency of identity across those services. I think this is a very important aspect of this discussion.<br>
<br>As it currently sits, users need to create multiple user accounts to deal with the various systems that P2PU recommends, whether they be OSQA, Pivotal Tracker, UserVoice, Open Atrium (<a href="http://tracker.p2pu.org">tracker.p2pu.org</a>), a wiki, mailing lists, blogs etc. LDAP is supported already for many of these systems and as it is frequently used, it is relatively well documented. Surely creating custom migration / identity management for every service going to be more time consuming and challenging than learning how to use LDAP? I think Jessy-Kate made this point very well and makes it clear that we can have LDAP and support OpenID too.<br>
<br>In my mind the experience of community members (and most importantly course participants) is made much more difficult through that process of creating accounts for each individual service. Maybe its a little bit like making it difficult to click through to buy something and losing sales as a result - in order to participate in learning I should not have to wait for confirmation emails from every service, I should not have to create my profile information afresh etc etc. <br>
<br>The current setup is making learners lives far more difficult than they need to be and quite possibly multiple sign-ups and managing multiple accounts is one factor leading to course drop-outs.<br><br>Pippa<br><br>
<br><br><div class="gmail_quote">On 9 February 2011 05:19, Stian Håklev <span dir="ltr"><<a href="mailto:shaklev@gmail.com">shaklev@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This is very useful. However, this was a straight migration, for P2PU the concern currently is to enable OSQA and Drupal integration in the short term, and longer term to enable integration with a number of different services (potentially IRC, Big Blue Button, OSQA, a wiki, etc). <br>
<br>Going to play with your new site now! :)<br><font color="#888888">Stian</font><div><div></div><div class="h5"><br><br></div></div></blockquote></div>