<div dir="ltr">Oh sure, you wouldn't have to even learn anything about git to pass on changes to the secretary who will make the actual changes. There are a few good video/interactive git tutorials, and git also has plenty of nice GUI-based tools as well.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 15, 2014 at 11:01 AM, Jeffrey Carl Faden <span dir="ltr"><<a href="mailto:jeffreyatw@gmail.com" target="_blank">jeffreyatw@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">If we're using GitHub, it's quite easy to create an account and then an issue on any specific repository. No command-line or programming knowledge necessary; it's just like using a forum.</div>
<span class="HOEnZb"><font color="#888888">
<div class="gmail_extra"><br></div></font></span><div class="gmail_extra"><span class="HOEnZb"><font color="#888888">Jeffrey</font></span><div><div class="h5"><br><br><div class="gmail_quote">On Wed, Jan 15, 2014 at 10:48 AM, Gregory Dillon <span dir="ltr"><<a href="mailto:gregorydillon@gmail.com" target="_blank">gregorydillon@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif"> is this a good idea before its time? My perception is that many people, even at Noisebridge, are not yet fluent and comfortable working with GIT / GITHUB </div>
<div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif"> The concern then translates into people being excluded from full participation by the lack of particular git skill. So I'd suggest an education effort on GIT, and taking a temperature of the git level that exists, and the git level needed for good implementation. But yes, nice idea, and good presentation of why it would be helpful.</div>
</div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On Wed, Jan 15, 2014 at 9:59 AM, Al Sweigart <span dir="ltr"><<a href="mailto:asweigart@gmail.com" target="_blank">asweigart@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Beat me to it. :) I was thinking of going through the wiki and finding all the policy related stuff that has passed consensus and putting it into a single wiki page, but a git repo is a better idea.<div>
<br>
</div><div>Right now Noisebridge leans too much on oral tradition. It's about time we hack together a printing press.</div><span><font color="#888888"><div><br></div><div>-Al</div></font></span></div><div>
<div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jan 15, 2014 at 9:14 AM, Tom Lowenthal <span dir="ltr"><<a href="mailto:me@tomlowenthal.com" target="_blank">me@tomlowenthal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello, I'm Tom, and I enjoy the way that git allows for structured<br>
modification to documents.<br>
<br>
tl;dr: I think we should use a git repository as the canonical version<br>
of our policies and procedures.<br>
<br>
Over the past six months, we have reached consensus on several<br>
proposals to change or tweak the way we do things. We've modified our<br>
access policy, our membership process, the responsibilities of some of<br>
the officers, and instituted an anti-harassment policy. These changes<br>
are constructive; all have the intention of improving Noisebridge.<br>
<br>
Unfortunately, I have periodically had trouble, made errors, or<br>
omitted things when trying to update our wiki pages to reflect<br>
changes. I fear that the clerical errors I've made are symptomatic of<br>
a general difficulty mentally applying new proposals to our current<br>
policies, and have also exacerbated confusion.<br>
<br>
I propose that we use a git repo as the canonical location of these<br>
documents. Proposals for change should come with a branch or fork<br>
which can be merged to implement the desired change. Changes should<br>
still occur only by consensus, and changes should still have a<br>
human-readable summary. Each of the policies should continue to be<br>
mirrored on the wiki, just not edited there.<br>
<br>
I'm happy to volunteer to get things working and help people start<br>
using it, as well as to maintain & operate the system. I think that<br>
operating such a system is a good responsibility to place on the<br>
secretary in general.<br>
<br>
-Tom<br>
_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net" target="_blank">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net" target="_blank">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br>Let's stay in touch. Greg
</font></span></div>
<br>_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net" target="_blank">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>