[Noisebridge-discuss] Added proposal to current consensus items

bfb bfb at riseup.net
Wed Dec 11 18:10:22 UTC 2013

I added a line to the text to clarify. The intent is to create a trial period where Noisebridge can hack, experiment and tweak, in good faith, the associate member consensus made on 10-29-2013.

If no second consensus can be reached in February, the associate member role goes away, member dues are reinstated, and Noisebridge is open to the public 24/7.

-------- Original message --------
From: Gregory Dillon <gregorydillon at gmail.com> 
Date:12/10/2013  17:59  (GMT-08:00) 
To: Kevin Schiesser <bfb at riseup.net> 
Cc: NoiseBridge Discuss <noisebridge-discuss at lists.noisebridge.net> 
Subject: Re: [Noisebridge-discuss] Added proposal to current consensus items 

Could you clarify what this means?  Its seems well intended, convoluted and imprecise.  Does it suggest retroactively doing something in the future?   Just what is the "original consensus"  I could guess, but its not clear.    What is a mutation? I don't want to be a mutation.    Isn't $date + 90 before Feb 4, and if so what happens when that bell rings?,  do the Associate Members transform into Capital M members or are they outsiders?  I can see the point of wanting to review a certain consensus item, but I can't make out what this would do.

On Tue, Dec 10, 2013 at 8:48 AM, Kevin Schiesser <bfb at riseup.net> wrote:
"Noisebridge should attach an expiration period of 90 days, beginning October 29, 2013, to the consensus decision to create an Associate Member role. All subsequent mutations of the original consensus should be brought for a second consensus, beginning February 4, 2014. "

See https://noisebridge.net/wiki/Current_Consensus_Items for details.


Noisebridge-discuss mailing list
Noisebridge-discuss at lists.noisebridge.net

Let's stay in touch.  Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.noisebridge.net/pipermail/noisebridge-discuss/attachments/20131211/7f54f30c/attachment.html>

More information about the Noisebridge-discuss mailing list