Obviously +1 for me.<div><br></div><div>I currently personally manage/maintain about 15 PBWikis including <a href="http://twitter.pbwiki.com">twitter.pbwiki.com</a>, <a href="http://barcamp.org">barcamp.org</a>, <a href="http://coworking.pbwiki.com">coworking.pbwiki.com</a>, <a href="http://wiki.oauth.net">wiki.oauth.net</a> and <a href="http://wiki.factoryjoe.com">wiki.factoryjoe.com</a>. I'm responsible for the largest wikis on PBWiki but they treat me really well and I've developed a personal relationship with the folks there.</div>
<div><br></div><div>There is very little reason for us to maintain our own MediaWiki instance, especially when we don't seem to have the in-house expertise to manage or keep the software up-to-date. If our wiki was a shining example of unified accounts across multiple disparate open source software packages, I'd think differently, but the past has shown that there's little motivation or interest in maintaining the wiki or the software underneath it. I'm happy to take on that role, including helping to migrate content, if it's decided that this is the right move forward.</div>
<div><br></div><div>Should that decision be made, we only need create a CNAME pointing to <a href="http://openid.pbwiki.com">openid.pbwiki.com</a> from <a href="http://wiki.openid.net">wiki.openid.net</a> for the transition to be made (this is how it's setup on <a href="http://wiki.oauth.net">wiki.oauth.net</a>). I can commit to helping skin the PBWiki among other admin tasks.</div>
<div><br></div><div>Chris <br><br><div class="gmail_quote">On Wed, Dec 3, 2008 at 11:15 PM, David Recordon <span dir="ltr"><<a href="mailto:drecordon@sixapart.com">drecordon@sixapart.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Starting to work on the wiki (<a href="http://wiki.openid.net/" target="_blank">http://wiki.openid.net/</a>) and remember<br>
why I'm not the largest fan of running your own MediaWiki<br>
installation. I've also made a change so that the default skin is now<br>
set back to the MediaWiki default instead of the OpenID one that Mart<br>
made since a) it was hard to read and b) the site no longer uses that<br>
design anyway.<br>
<br>
I know that Chris Messina setup a "fan wiki" at <a href="http://openid.pbwiki.com/" target="_blank">http://openid.pbwiki.com/</a><br>
as well. When we originally installed the OpenID Wiki we chose to<br>
self host MediaWiki since none of the hosted wiki services supported<br>
OpenID. Now that PBWiki has good OpenID support, I'd personally like<br>
to see us move to using it. We can copy over the useful information<br>
on the current wiki and set it up so that <a href="http://wiki.openid.net" target="_blank">wiki.openid.net</a> points at<br>
the PBWiki Chris created.<br>
<br>
Anyone strongly object to this approach? I think it will be easier to<br>
work with, has better OpenID support than MediaWiki, and is one less<br>
thing for Scott and I to manage on the OpenID.net box.<br>
<br>
--David<br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Citizen-Participant &<br> Open Technology Advocate-at-Large<br><a href="http://factoryjoe.com">factoryjoe.com</a> # <a href="http://diso-project.org">diso-project.org</a><br>
<a href="http://citizenagency.com">citizenagency.com</a> # <a href="http://vidoop.com">vidoop.com</a><br>This email is: [ ] bloggable [X] ask first [ ] private<br>
</div>