Noisebridge - User contributions [en]

Draft Consensus Items

2019-01-09T20:29:06Z

166.107.111.254: remove outdated proposal

This page is for consensus item drafts so that:

* people can easily share ideas with a record of changes
* avoid creating time pressure for community members by introducing items before sufficient discussion has happened

{| class="wikitable sortable" border="1"
! Date First Discussed
! Proposed By
! Informal Title
! Summary
! Author of this Record

|-
| Jan 09, 2019
| Matt Arcidy
| Move off noisebridge.net to a new domain
| Text here: https://www.noisebridge.net/wiki/User:Rando/Move_Domains
| Matt Arcidy

|-
| May 22, 2018
| John Shutt
| Defining Board Officer and Chairperson Roles
| Text here: https://www.noisebridge.net/wiki/Defining-Roles
| John Shutt

|-
| 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

|}

== Related Pages ==

The [[Current Consensus Items]] is a page for hosting consensus items currently under debate, with their formal wording.

The [[Consensus_Items_History|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.

Current Consensus Items

2018-05-22T20:18:54Z

166.107.111.254: undo on request from james, for now

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

The [[Consensus_Items_History|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.

{| class="wikitable sortable" border="1"
! 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

|}

Current Consensus Items

2018-05-22T20:06:32Z

166.107.111.254: added slack log publishing / privacy consensus proposal

Wiki Upgrade

2017-12-20T23:24:16Z

166.107.111.254: added instructions for migrating a wiki

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database.
# Migrate to postgresql?
## make a git repo to store migration sql and other sql used for massaging the database contents
# Delete old passwords (md5 with no salt) and expire all user passwords?
## Write/publish public sql script to clean up the production database for public publishing
# Clean the database of spam/cruft?
## publish these scripts to the same sql script repo

=== MediaWiki-Vagrant ===

This potentially is a good environment for testing and migrating the database: https://www.mediawiki.org/wiki/MediaWiki-Vagrant

(more OpenStack Semantic MediaWiki images: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS)

You'll need to follow this guide to get a dump of our database up and running: https://www.mediawiki.org/wiki/Manual:Moving_a_wiki

=== Password Rollover ===

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<code>
user_password_expires

MediaWiki version: ≥ 1.23

Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().

</code>

Wiki Upgrade

2017-12-20T23:02:09Z

166.107.111.254: /* Database Hacking */

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database.
# Migrate to postgresql?
## make a git repo to store migration sql and other sql used for massaging the database contents
# Delete old passwords (md5 with no salt) and expire all user passwords?
## Write/publish public sql script to clean up the production database for public publishing
# Clean the database of spam/cruft?
## publish these scripts to the same sql script repo

=== MediaWiki-Vagrant ===

This potentially is a good environment for testing and migrating the database: https://www.mediawiki.org/wiki/MediaWiki-Vagrant

(more OpenStack Semantic MediaWiki images: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS)

=== Password Rollover ===

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<code>
user_password_expires

MediaWiki version: ≥ 1.23

Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().

</code>

Wiki Upgrade

2017-12-20T22:21:25Z

166.107.111.254: /* Database Hacking */

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database. Lets use one of the OpenStack Semantic MediaWiki images for testing and refitting the database: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS

# Migrate to postgresql?
## make a git repo to store migration sql and other sql used for massaging the database contents
# Delete old passwords (md5 with no salt) and expire all user passwords?
## Write/publish public sql script to clean up the production database for public publishing
# Clean the database of spam/cruft?
## publish these scripts to the same sql script repo

=== Password Rollover ===

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<code>
user_password_expires

MediaWiki version: ≥ 1.23

Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().

</code>

Wiki Upgrade

2017-12-20T22:18:23Z

166.107.111.254: added some database hacking ideas

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database. Lets use one of the OpenStack Semantic MediaWiki images for testing and refitting the database: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS

# Migrate to postgresql?
# Delete old passwords (md5 with no salt) and expire all user passwords?
# Clean the database of spam/cruft?
# Write/publish public sql script to clean up the production database for public publishing

=== Password Rollover ===

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<code>
user_password_expires

MediaWiki version: ≥ 1.23

Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().

</code>

Wiki Upgrade

2017-12-20T22:05:02Z

166.107.111.254:

Wiki Upgrade

2017-12-20T22:04:46Z

166.107.111.254:

Wiki Upgrade

2017-12-20T22:04:28Z

166.107.111.254: /* Password Rollover */

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database. Lets use one of the OpenStack Semantic MediaWiki images for testing and refitting the database: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS

=== Password Rollover ===

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<code>
user_password_expires[edit] .
MediaWiki version: ≥ 1.23 .
Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().
</code>

Wiki Upgrade

2017-12-20T22:04:16Z

166.107.111.254: /* Password Rollover */

Wiki Upgrade

2017-12-20T22:03:51Z

166.107.111.254:

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database. Lets use one of the OpenStack Semantic MediaWiki images for testing and refitting the database: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS

=== Password Rollover ===

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<source>
user_password_expires[edit]
MediaWiki version: ≥ 1.23
Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().
</source>

Wiki Upgrade

2017-12-20T21:42:27Z

166.107.111.254: added database hacking ideas

Wiki Upgrade

2017-12-20T21:38:22Z

166.107.111.254: /* Ansible Roles */

Wiki Upgrade

2017-12-20T21:37:04Z

166.107.111.254: /* Ansible Roles */

Wiki Upgrade

2017-12-20T21:33:06Z

166.107.111.254: added roles section

Wiki Upgrade

2017-12-20T21:22:52Z

166.107.111.254: /* Chosen Technologies */

Wiki Upgrade

2017-12-20T21:22:03Z

166.107.111.254: added formatting and requirements and title

Moving

2017-12-06T19:47:38Z

166.107.111.254: changed next meeting date

[[File:nbsp.jpg|400px|right]]

This is a set of pages meant to facilitate the discussion on moving Noisebridge to a new physical location. We should use this space to capture consensus as it occurs, and to draw all our planning tools together.
<br />

__TOC__

<br clear=all>
<br />

'''NEXT MEETING: 2017-12-09 6pm @ Noisebridge'''

== New Space 2017 Meeting Notes ==
* [[New space meeting 2017 12 02]]
* [[New space meeting 2017 11 18]]
* [[New space meeting 2017 11 11]]

== Frequently Asked Questions ==

* How big is Noisebridge currently: approximately 5,550 sq. ft.
* How much is our current rent: $4,356/month ~ $0.79/sq. ft. /month
* When is our current lease up: August 31th 2018 5pm

== 2009 Move page ==

* [[Moving2009]]