Current Consensus Items

From Noisebridge
Revision as of 13:06, 22 May 2018 by 166.107.111.254 (talk) (added slack log publishing / privacy consensus proposal)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This is a page for hosting consensus items currently under debate, with their formal wording.

The Consensus Items History is the public record of consensus items that have been decided on in the past. Please move the records from the "Current" page to the "History" page once they've been approved/blocked.

Date First Discussed Proposed By Informal Title Summary Author of this Record
22 May 2018 Beka Philanthropy Renaming Rename Philanthropists to Daemons and update all the relevant related words in parallel ways. Beka
22 May 2018 Beka Document and Do-ocratize Infrastructure Noisebridge will document it's infrastructure (including access control, wikipedia and social media accounts, domain names, financial record keeping and related accounts), and build tools to reduce or eliminate the reliance on trusted individuals, so as to prevent those items of infrastructure from becoming unusable or unmaintainable in the case that those trusted individuals cease to be readily contactable. All such tools will aim to maximize decentralized do-ocratic participation, transparency, and accountability, and minimize secrecy and concentration of power. As part of this, it is necessary to answer the following questions:

1) How can these pieces of infrastructure be accessed without significant vulnerabilities? I.E. what does it mean to access NB's Twitter account in an accountable way? How does that compare to bank information? To domain names? What conditions are appropriate for each such piece of infrastructure, to allow access to working groups building tools?

2) What tools can be made to provide decentralizeddo-ocratic control and accountability? What information must be shared, when, and how can that sharing be guaranteed?

3) Who will build the tools, write the documentation, etc.?

When these three questions can be answered, access will be granted to these tools. The system of trusted individuals may continue to exist as a fallback, if desirable, but will not be the sole way to manage this infrastructure thereafter.

Beka


22 May 2018 Trent Publish Slack Logs Going Forwards; Respect Privacy of Slack Logs Before June 2018 Publish monthly slack logs on the internet moving forwards. Slack history before June 2018 is not to be shared without further Consensus. Trent