<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I agree that I see no problem using a wiki for this, with change control, but just want to make sure the wiki actually reflects reality. :)<div><br><div><div>On Dec 17, 2008, at 3:20 PM, Chris Messina wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Wed, Dec 17, 2008 at 2:38 PM, Martin Atkins <span dir="ltr"><<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="Ih2E3d">David Recordon wrote:<br>><br> > While it is a wiki, you can't just change the bylaws as they're a legal<br> > document which the board needs to vote to change. I know Bill had been<br> > working on some changes to them, not sure what happened to it all, and<br> > we should also vote to update them to reflect the new fee structure.<br> > The wiki page should however capture the current bylaws if we plan to<br> > refer people to it.<br> ><br> <br> </div>I'm wary of having multiple copies of this lying around, since at some<br> point they're going to get out of sync.<br> <br> Things like the bylaws should be in exactly one place. If alternate<br> formats are desired, they should be automatically generated from the<br> source and guaranteed to always match the original exactly.<br> <br> However, if the complaint was just that folks don't want it as a PDF we<br> ought to be able to make the canonical version HTML and just throw away<br> the PDF to keep things simple. I assume this was a wordprocessor<br> document at some point, so it should be trivial for whoever holds that<br> copy to export it to HTML.<br> <br> This really isn't the sort of thing that belongs on a wiki.<br></blockquote></div><br clear="all">I disagree. PBWiki provides page-level authoring permissions, so I can lock down this page to a few select individuals who should have the rights to edit it (likely the secretary).<div> <br></div><div>My predominant interests in having the Bylaws on the wiki are:</div><div><br></div><div>1. to have a web-friendly URL that we can use to access the bylaws, rather than a PDF</div><div>2. to be able to publicly track changes and link to the changeset. i.e.:</div> <div><br></div><div><a href="https://openid.pbwiki.com/sdiff.php?first=Bylaws.2008-12-17-20-38-48&second=Bylaws.2008-12-17-19-11-50">https://openid.pbwiki.com/sdiff.php?first=Bylaws.2008-12-17-20-38-48&second=Bylaws.2008-12-17-19-11-50</a></div> <div><br></div><div>In hard document formats, you don't get this kind of transparency, and I think it's very important to be able to demonstrate what changes were made by whom and when.</div><div><br></div><div>I am inspired by the work going on at the Change Wiki, attempting to keep a changelog of pages on <a href="http://change.gov">change.gov</a>:</div> <div><br></div><div><a href="http://change.wikia.com/wiki/Change_Wiki">http://change.wikia.com/wiki/Change_Wiki</a></div><div><br></div><div>I think we should endeavor to provide such transparency natively, without forcing people to scrape and diff our content!</div> <div><br></div><div>So, I do agree that binding changes shouldn't be able to be made by just anyway and that we should have a canonical location for the bylaws, but I also think that transparency and editing history is just as important.</div> <div><br></div><div>Chris<br><div><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></div> _______________________________________________<br>general mailing list<br><a href="mailto:general@openid.net">general@openid.net</a><br>http://openid.net/mailman/listinfo/general<br></blockquote></div><br></div></body></html>