Sudo Room - User contributions [en]

Facilities

2026-10-02T05:14:52Z

Indoorjetpacks: /* Cleaning Protocols */

Sudo Room's facilities are maintained through the collaborative effort of the Sudo Room facilities working group, the Omni Commons building working group, and every Sudo Room member. Below are links to relevant information about our facility.

== Cleaning Protocols ==
Every member should know how to take the trash out and do it when the trash is full. When full, trash bags should be tied off and transferred to the large street bins stored in the trash room. A new bag should be placed in the bin from the top shelf of the Soon To Be Removed/supplies rack by the front stairs. Trash bag donations are appreciated. Uncertain what size most of our bins use, but can confirm 30 gal is too small for the front double recycle+trash bin set.

=== E-Waste Disposal ===
E-Waste can be disposed of by dropping of bins at the Oakland Household Waste (HHW) center. To drop of waste, [[https://www.stopwaste.org/at-home/household-hazardous-waste/residential-hhw-drop-off-service/oakland-hhw-facility|go to their website]] and click "Schedule appointment", then select a time and certify that you meet the requirements of their program. Once complete, all you have to do is load the e-waste into bins and place them in your trunk. Drive up to their facility at 2100 East 7th Street, Oakland and follow their instructions. You'll just need to open your trunk and they'll take out the contents.

You can also drop off e-waste with the E-Waste Collective in Berkeley at their Berkeley drop-off location: 620 Page St, Berkeley, CA, 94710. Hours and contact information can be found [https://ewastecollective.org/contact/ on their website].

=== Disposing of large or bulky items ===
Information on scheduling large item pickup is available on the Oakland Recycles webpage for [https://www.oaklandrecycles.com/bulky-service/ Bulky Junk Services].

== Tool List ==
[[Work Stations]]

== Parts catalog ==
TBD

== Donations Protocols ==
TBD

Sudohumans

2026-09-04T04:01:07Z

Indoorjetpacks: past-tense-ing sudohumans page

SudoHumans was our previous membership, donor web app, before our move to membermatters: backers.sudoroom.org.

It used to do the following:
* https://sudoroom.org/humans/

* It's open source
* Created by SudoRoom members
* Collects dues
* Enables creation of profiles

[[Category:Projects]]

Meeting Notes 2026-08-30

2026-08-31T05:40:35Z

Indoorjetpacks: formatting from md-style for some things to mediawiki

'''Sudo Room Meeting - Day Month 2026 4pm-6pm'''

= Meeting Details =

== Roles ==
* Facilitator/s:
* Stacktaker:
* Timekeeper:
* Notetaker/s: Mn, Mk, R

== Attendees ==
A (virtual)
Mn
Mk
E
Mz
R
D

= Agenda =

== Funding ==
Is membership the only source of income?
M: Grants? (we have one currently,
2027 Spring (April deadline?)

up to $50,000
"art" project, community infrastructure

"The Creative Capital Award provides individual artists with unrestricted project grants and professional development services for the creation of innovative, original, groundbreaking new artistic works."

https://creative-capital.org/creative-capital-award/

mk: has there been annual fundraizers?

a: not sure what has been happening in the past, but there has been some reach out to the community. dont think there has been coordination to get org visibility on the radio, i dont know how people find out about sudoroom

a: i'd suggest doing some basic classes, i think people would pay to attend some basic classes about electronics or multimeters - also she talks bout calendar/event visiblity, event organizing/community outreach -

e: is this an idea for a fundraiser for sudoroom? or were you taklking about a different thing?

a: has to do with creating community/expanding community, you'd have more members, providing services/classes that the community could partake in, a lot of like the seniors struggle with basic (tech?) things, could do a flat $20 rate etc for classes or help

mk: i saw a professor setup a structure he does in south america, he created a format for what you're describing in a more..professional structure that's a subscritption based thing, if elderly people want tech support, they'd pay for a chunk of hours, and the student could help (list of services that they'd support)

(a cuts out but was talking about...something streaming/tv/radio show type thing? unsure)

mz: talkingg about tv reception etc

a: good idea to offer really basic classes on multimeters, using phones, some sort of structured classes for basic things, could go to senior center on behalf of sudoroom, half to the person half to the sudoroom

mz: we could offer printing/laser services to the community also

a: not so much a class vs a one time lecture, also we could see about using the ballroom to do lectures, that's an opportunity we could try to use since we're just in the building

mk: surprised there's no annual fundraising, it'd be awesome if there was a community outreach from seniors/students etc, mini conferences/workshops. I likek the bigger structures of multiple, but that's need to be planned out nd oranized, make sure it fits with bylaws and nonprofit stuff etc.

r note: commission based vs hourly

R: Generate events besides regular meetings for fundraising, promotion, community building, and social networking

* create volunteer lead group meetings, classes

* social events at a park, raffles, grab bags, donations

* consider sponsorships (grants)

* volunteers do odd jobs, maybe a kind of fundraiser to see how many people can be helped

* grant writing night

* outreach at senior centers

* etsy: making things for seniors

* grant writing

* networking

* sponsorships

== Anti Data Center Petition ==

* sign as an org?

* be in social media post and why

* offer support/meeting location etc?

https://www.nodatacenteroakland.com/nodatacenterincoakland/#endorse

(various chatter about sudoroom.org history)

Mz: is there any specifics about type of data centers?

Mk: thats a good question, companies are trying to skirt it with legal

overall thoughts are should figure out more about the org and what they're doing and what actions they want and what we'd be committing to etc

Mz: Depending on what kind of data center. Edge data centers close to the users offer lower latency and make it convient for people who want to host stuff locally. But yes for LLM there's no need to be in oakland.

== workshops? ==

intro to linux (with chromebooks?)

discord - notification settings, nuance

potential subscription or fundraiser potential? for seniors, students, public events

== Sudoroom.org server ==

More info about this?

mz: I think we are using digital ocean now There's one for sudohumans and one for main sudoroom.org (wiki and listserv), maybe another VPS for member matters.

mz: we're looking at doing some selfhosting. The concerns are internet bandwidth and DDoS attack

mn: yeah i was just curious what the sudoroom.org new server would be/what we'd host vs have still on digital ocean, just curious more about what the project is

(A rejoins, catching up on what missed during the drop)

E: "as usual if you know other ways we can make more money, that'd be great"

==Signal Groupchat for members==

mz: sudoroom communicates via discord/mailing list, we have a bunch of signal gropou chats, seems like signal is the most mature for group stuff, when applying can put in their signal groupchat, we could have a thing go ou on the mailin list. what do yall think?

mk: i think doesn't seem totally neessary to have it in the form.

a: my input is i dont understand how that'd be different than discord

mz: encrypted end to end

r: discord rolled out a new thing about tracking/security thing

mz: no guarentee discord wont use chats to train AI

e: the one i'm concerned about wiht discord is age verification, has that started yet?

mk: hasvent started yet but its' coming

e: also there's ads etc,

mk: signal would be simpler and private

e: i like signal because it's simple and allows you to do enough for most things

mz: members list is supposed to be private, but it isn't

s: in general i'm in support of using signal, the fragmentation is my concern though, discord/signal/mailing list etc -

mz: could do an api etc

mz: group for people interestd in organizing/managing sudoroom etc

s: same point about it's not clear to outsider

mz: a lot of people do just use diiscord, dont' have other conversations on signal etc, so do you

s: i think it'd go a long way to solvle the issue, providing clarity about what things are for what - general purpose chitchat for all members vs something else/managing

mk: chat gets difficult to catch up on as it scales

s: the issue with discord is how it's organized, server will send notifs even though the various groups are/aren't...organized by like volume of messages etc

s: overall i'd like to nudge people away from discord

mz: sudo discuss vs sudo members

mk: big fan of forum style

mz: pyramid form of wiki>forum>chat

r: website structured as projects vs weekly meetings, it'd be good to setup something in like bbcode around that, and then weekly meetings could be structured around those projects

mk: on the wiki?

r: on the phone its hard to tell meetings vs projects etc

mk: i dont think we have weekly things

mk: is it a question of where do projects set with the meetings?

r: for any normal projects looking at weekly things vs where to get involved in things - also graphic things, hard to read white text etc (website text is hard to read)

r: can we also shift topics to fundraising again, what events we have and what planned fo rht erest f the year, looking at FNB and other coallitions? Could we have a grant writing night,

mn: do you have experience doing that? would be great to put that on

r: if we have a monthly grant writing night, it'd be an enteratining way to keep it going

mk: even if there's not an existing one, having a night to develop/practice grant writing that'd be good

r: the way my non profit would do things is a flat rate etc

mz: we dont have a agreed upon way to compensate members about their time vs tothe org etc

mk: look at other orgs, horizontal structure vs ......... common pool resources, basicaly the structure of this problem, the shared resources, theres always the issues of that

r: we should put out a survey of "howd you hear about sudo, what do ou see, what things are you apart of?" (fixit clinic, radio night, etc)

r: have a laptop read with survey

mz: cryptpad? i have done stuff before i can help set it up

mz: outreach is good - community stuff isn't realy known like this, hackerspaces vs tech spaces not really known to the people

mz: back to the basics type - excellence, do-acray, consensus - trifecta of anarchy

== Recap ==

communication methods:

discord/signal/wiki/forum/email/Matrix

fundraising:

* workshops (basics/one-off lectures + people arrive with questions)

* fundraisers, raffles, video screenings, social networking

* outreach, survey, social networking events

* offer serices to senior home centers, have individuals go to senior homes to offer classes ask Alice

* grant writing night

events:
r: brainstorm past events, to come up with past events to see what we could do again in the future

mz: just started some opensource events meetup

(mk and mz chat about FOSS and CoreBoot stuff)

(chatter about grant writing night, process of grant writing)

D: have we connected with berkley law? they have a small business type night and help with nonprofits, ucberkeleylaw www.law.berkeley.edu, I can look into that before I leave

D: sounds like it's not great for learning to do grant writing, they have clinics that are profit based sort of

mk: on that note, do we have sort of "normal" social media for public outreach?

* weekly instagram, or stories work like flyers that other people can repost

* streaming events (twitch, youtube, tiktok)

== Process membership applications ==

Mz added some new members, did some kanban stuff, sent some emails to people

Meeting Notes 2026-08-30

2026-08-31T03:34:32Z

Indoorjetpacks: /* Process membership applications */

'''Sudo Room Meeting - Day Month 2026 4pm-6pm'''

= Meeting Details =

(this meeting needs formatting bc some people were notetaking in markdown style formatting :[ )

== Roles ==
* Facilitator/s:
* Stacktaker:
* Timekeeper:
* Notetaker/s: Mn, Mk, R

== Attendees ==
A (virtual)
Mn
Mk
E
Mz
R
D

= Agenda =

== Funding ==
Is membership the only source of income?
M: Grants? (we have one currently,
- 2027 Spring (April deadline?)

up to $50,000

"art" project, community infrastructure

"The Creative Capital Award provides individual artists with unrestricted project grants and professional development services for the creation of innovative, original, groundbreaking new artistic works.

https://creative-capital.org/creative-capital-award/

mk: has there been annual fundraizers?

a: not sure what has been happening in the past, but there has been some reach out to the community. dont think there has been coordination to get org visibility on the radio, i dont know how people find out about sudoroom

a: i'd suggest doing some basic classes, i think people would pay to attend some basic classes about electronics or multimeters - also she talks bout calendar/event visiblity, event organizing/community outreach -

e: is this an idea for a fundraiser for sudoroom? or were you taklking about a different thing?

a: has to do with creating community/expanding community, you'd have more members, providing services/classes that the community could partake in, a lot of like the seniors struggle with basic (tech?) things, could do a flat $20 rate etc for classes or help

mk: i saw a professor setup a structure he does in south america, he created a format for what you're describing in a more..professional structure that's a subscritption based thing, if elderly people want tech support, they'd pay for a chunk of hours, and the student could help (list of services that they'd support)

(a cuts out but was talking about...something streaming/tv/radio show type thing? unsure)

mz: talkingg about tv reception etc

a: good idea to offer really basic classes on multimeters, using phones, some sort of structured classes for basic things, could go to senior center on behalf of sudoroom, half to the person half to the sudoroom

mz: we could offer printing/laser services to the community also

a: not so much a class vs a one time lecture, also we could see about using the ballroom to do lectures, that's an opportunity we could try to use since we're just in the building

mk: surprised there's no annual fundraising, it'd be awesome if there was a community outreach from seniors/students etc, mini conferences/workshops. I likek the bigger structures of multiple, but that's need to be planned out nd oranized, make sure it fits with bylaws and nonprofit stuff etc.

r note: commission based vs hourly

R: Generate events besides regular meetings for fundraising, promotion, community building, and social networking

- create volunteer lead group meetings, classes

- social events at a park, raffles, grab bags, donations

- consider sponsorships (grants)

- volunteers do odd jobs, maybe a kind of fundraiser to see how many people can be helped

- grant writing night

- outreach at senior centers

- etsy: making things for seniors

- grant writing
- networking
- sponsorships

== Anti Data Center Petition ==
- sign as an org?
- be in social media post and why
- offer support/meeting location etc?
https://www.nodatacenteroakland.com/nodatacenterincoakland/#endorse
(various chatter about sudoroom.org history)
Mz: is there any specifics about type of data centers?
Mk: thats a good question, companies are trying to skirt it with legal
overall thoughts are should figure out more about the org and what they're doing and what actions they want and what we'd be committing to etc
Mz: Depending on what kind of data center. Edge data centers close to the users offer lower latency and make it convient for people who want to host stuff locally. But yes for LLM there's no need to be in oakland.

== workshops? ==
intro to linux (with chromebooks?)
discord - notification settings, nuance
potential subscription or fundraiser potential? for seniors, students, public events

== Sudoroom.org server ==
More info about this?
mz: I think we are using digital ocean now There's one for sudohumans and one for main sudoroom.org (wiki and listserv), maybe another VPS for member matters.
mz: we're looking at doing some selfhosting. The concerns are internet bandwidth and DDoS attack
mn: yeah i was just curious what the sudoroom.org new server would be/what we'd host vs have still on digital ocean, just curious more about what the project is

(A rejoins, catching up on what missed during the drop)
E: "as usual if you know other ways we can make more money, that'd be great"

==Signal Groupchat for members==
mz: sudoroom communicates via discord/mailing list, we have a bunch of signal gropou chats, seems like signal is the most mature for group stuff, when applying can put in their signal groupchat, we could have a thing go ou on the mailin list. what do yall think?
mk: i think doesn't seem totally neessary to have it in the form.
a: my input is i dont understand how that'd be different than discord
mz: encrypted end to end
r: discord rolled out a new thing about tracking/security thing
mz: no guarentee discord wont use chats to train AI
e: the one i'm concerned about wiht discord is age verification, has that started yet?
mk: hasvent started yet but its' coming
e: also there's ads etc,
mk: signal would be simpler and private
e: i like signal because it's simple and allows you to do enough for most things
mz: members list is supposed to be private, but it isn't
s: in general i'm in support of using signal, the fragmentation is my concern though, discord/signal/mailing list etc -
mz: could do an api etc
mz: group for people interestd in organizing/managing sudoroom etc
s: same point about it's not clear to outsider
mz: a lot of people do just use diiscord, dont' have other conversations on signal etc, so do you
s: i think it'd go a long way to solvle the issue, providing clarity about what things are for what - general purpose chitchat for all members vs something else/managing
mk: chat gets difficult to catch up on as it scales
s: the issue with discord is how it's organized, server will send notifs even though the various groups are/aren't...organized by like volume of messages etc
s: overall i'd like to nudge people away from discord
mz: sudo discuss vs sudo members
mk: big fan of forum style
mz: pyramid form of wiki>forum>chat

r: website structured as projects vs weekly meetings, it'd be good to setup something in like bbcode around that, and then weekly meetings could be structured around those projects
mk: on teh wiki?
r: on the phone hard to tell meetings vs projects etc
mk: i dont think we have weekly things
mk: is it a question of where do projects set with the meetings?
r: for any normal projects looking at weekly things vs where to get involved in things - also graphic things, hard to read white text etc (website text is hard to read)

r: can we also shift topics to fundraising again, what events we have and what planned fo rht erest f the year, looking at FNB and other coallitions? Could we have a grant writing night,
m: do you have experience donig that? would be great to put that on
r: if we have a monthly grant writing night, it'd be an enteratining way to keep it going
mk: even if there's not an existing one, having a night to develop/practice grant writing that'd be good

r: the way my non profit would do things is a flat rate etc
mz: we dont have a agreed upon way to compensate members about their time vs tothe org etc
mk: look at other orgs, horizontal structure vs ......... common pool resources, basicaly the structure of this problem, the shared resources, theres always the issues of that
r: we should put out a survey of "howd you hear about sudo, what do ou see, what things are you apart of?" (fixit clinic, radio night, etc)
r: have a laptop read with survey
mz: cryptpad? i have done stuff before i can help set it up

mz: outreach is good - community stuff isn't realy known like this, hackerspaces vs tech spaces not really known to the people

mz: back to the basics type - excellence, do-acray, consensus - trifecta of anarchy

== Recap ==:
communication methods
- discord/signal/wiki/forum/email/Matrix
fundraising:

- workshops (basics/one-off lectures + people arrive with questions)

- fundraisers, raffles, video screenings, social networking

- outreach, survey, social networking events

- offer serices to senior home centers, have individuals go to senior homes to offer classes ask Alice

- grant writing night

events:
r: brainstorm past events, to come up with past events to see what we could do again in the future
mz: just started some opensource events meetup
(mk and mz chat about FOSS and CoreBoot stuff)

(chatter about grant writing night, process of grant writing)
D: have we connected with berkley law? they have a small business type night and help with nonprofits, ucberkeleylaw www.law.berkeley.edu, I can look into that before I leave
D: not great for learning to do grant writing, they have clinics that are profit based sort of

mk: on that note, do we have sort of "normal" social media for public outreach?

- weekly instagram, or stories work like flyers that other people can repost

- streaming events (twitch, youtube, tiktok)

== Process membership applications ==

Mz added some new members, did some kanban stuff, sent some emails to people

-----------------------------------

Meeting Notes 2026-08-30

2026-08-31T03:30:57Z

Indoorjetpacks: /* Meeting Details */

Meeting Notes 2026-08-30

2026-08-31T03:29:39Z

Indoorjetpacks: Created page with " '''Sudo Room Meeting - Day Month 2026 4pm-6pm''' = Meeting Details = == Roles == * Facilitator/s: * Stacktaker: * Timekeeper: * Notetaker/s: Mn, Mk, R == Attendees == A (virtual) Mn Mk E Mz R D = Agenda = == Funding == Is membership the only source of income? M: Grants? (we have one currently, - 2027 Spring (April deadline?) up to $50,000 "art" project, community infrastructure "The Creative Capital Award provides individual artists with unr..."

'''Sudo Room Meeting - Day Month 2026 4pm-6pm'''

= Meeting Details =

== Roles ==
* Facilitator/s:
* Stacktaker:
* Timekeeper:
* Notetaker/s: Mn, Mk, R

== Attendees ==
A (virtual)
Mn
Mk
E
Mz
R
D

= Agenda =

== Funding ==
Is membership the only source of income?
M: Grants? (we have one currently,
- 2027 Spring (April deadline?)

up to $50,000

"art" project, community infrastructure

"The Creative Capital Award provides individual artists with unrestricted project grants and professional development services for the creation of innovative, original, groundbreaking new artistic works.

https://creative-capital.org/creative-capital-award/

mk: has there been annual fundraizers?

a: not sure what has been happening in the past, but there has been some reach out to the community. dont think there has been coordination to get org visibility on the radio, i dont know how people find out about sudoroom

a: i'd suggest doing some basic classes, i think people would pay to attend some basic classes about electronics or multimeters - also she talks bout calendar/event visiblity, event organizing/community outreach -

e: is this an idea for a fundraiser for sudoroom? or were you taklking about a different thing?

a: has to do with creating community/expanding community, you'd have more members, providing services/classes that the community could partake in, a lot of like the seniors struggle with basic (tech?) things, could do a flat $20 rate etc for classes or help

mk: i saw a professor setup a structure he does in south america, he created a format for what you're describing in a more..professional structure that's a subscritption based thing, if elderly people want tech support, they'd pay for a chunk of hours, and the student could help (list of services that they'd support)

(a cuts out but was talking about...something streaming/tv/radio show type thing? unsure)

mz: talkingg about tv reception etc

a: good idea to offer really basic classes on multimeters, using phones, some sort of structured classes for basic things, could go to senior center on behalf of sudoroom, half to the person half to the sudoroom

mz: we could offer printing/laser services to the community also

a: not so much a class vs a one time lecture, also we could see about using the ballroom to do lectures, that's an opportunity we could try to use since we're just in the building

mk: surprised there's no annual fundraising, it'd be awesome if there was a community outreach from seniors/students etc, mini conferences/workshops. I likek the bigger structures of multiple, but that's need to be planned out nd oranized, make sure it fits with bylaws and nonprofit stuff etc.

r note: commission based vs hourly

R: Generate events besides regular meetings for fundraising, promotion, community building, and social networking

- create volunteer lead group meetings, classes

- social events at a park, raffles, grab bags, donations

- consider sponsorships (grants)

- volunteers do odd jobs, maybe a kind of fundraiser to see how many people can be helped

- grant writing night

- outreach at senior centers

- etsy: making things for seniors

- grant writing
- networking
- sponsorships

== Anti Data Center Petition ==
- sign as an org?
- be in social media post and why
- offer support/meeting location etc?
https://www.nodatacenteroakland.com/nodatacenterincoakland/#endorse
(various chatter about sudoroom.org history)
Mz: is there any specifics about type of data centers?
Mk: thats a good question, companies are trying to skirt it with legal
overall thoughts are should figure out more about the org and what they're doing and what actions they want and what we'd be committing to etc
Mz: Depending on what kind of data center. Edge data centers close to the users offer lower latency and make it convient for people who want to host stuff locally. But yes for LLM there's no need to be in oakland.

== workshops? ==
intro to linux (with chromebooks?)
discord - notification settings, nuance
potential subscription or fundraiser potential? for seniors, students, public events

== Sudoroom.org server ==
More info about this?
mz: I think we are using digital ocean now There's one for sudohumans and one for main sudoroom.org (wiki and listserv), maybe another VPS for member matters.
mz: we're looking at doing some selfhosting. The concerns are internet bandwidth and DDoS attack
mn: yeah i was just curious what the sudoroom.org new server would be/what we'd host vs have still on digital ocean, just curious more about what the project is

(A rejoins, catching up on what missed during the drop)
E: "as usual if you know other ways we can make more money, that'd be great"

==Signal Groupchat for members==
mz: sudoroom communicates via discord/mailing list, we have a bunch of signal gropou chats, seems like signal is the most mature for group stuff, when applying can put in their signal groupchat, we could have a thing go ou on the mailin list. what do yall think?
mk: i think doesn't seem totally neessary to have it in the form.
a: my input is i dont understand how that'd be different than discord
mz: encrypted end to end
r: discord rolled out a new thing about tracking/security thing
mz: no guarentee discord wont use chats to train AI
e: the one i'm concerned about wiht discord is age verification, has that started yet?
mk: hasvent started yet but its' coming
e: also there's ads etc,
mk: signal would be simpler and private
e: i like signal because it's simple and allows you to do enough for most things
mz: members list is supposed to be private, but it isn't
s: in general i'm in support of using signal, the fragmentation is my concern though, discord/signal/mailing list etc -
mz: could do an api etc
mz: group for people interestd in organizing/managing sudoroom etc
s: same point about it's not clear to outsider
mz: a lot of people do just use diiscord, dont' have other conversations on signal etc, so do you
s: i think it'd go a long way to solvle the issue, providing clarity about what things are for what - general purpose chitchat for all members vs something else/managing
mk: chat gets difficult to catch up on as it scales
s: the issue with discord is how it's organized, server will send notifs even though the various groups are/aren't...organized by like volume of messages etc
s: overall i'd like to nudge people away from discord
mz: sudo discuss vs sudo members
mk: big fan of forum style
mz: pyramid form of wiki>forum>chat

r: website structured as projects vs weekly meetings, it'd be good to setup something in like bbcode around that, and then weekly meetings could be structured around those projects
mk: on teh wiki?
r: on the phone hard to tell meetings vs projects etc
mk: i dont think we have weekly things
mk: is it a question of where do projects set with the meetings?
r: for any normal projects looking at weekly things vs where to get involved in things - also graphic things, hard to read white text etc (website text is hard to read)

r: can we also shift topics to fundraising again, what events we have and what planned fo rht erest f the year, looking at FNB and other coallitions? Could we have a grant writing night,
m: do you have experience donig that? would be great to put that on
r: if we have a monthly grant writing night, it'd be an enteratining way to keep it going
mk: even if there's not an existing one, having a night to develop/practice grant writing that'd be good

r: the way my non profit would do things is a flat rate etc
mz: we dont have a agreed upon way to compensate members about their time vs tothe org etc
mk: look at other orgs, horizontal structure vs ......... common pool resources, basicaly the structure of this problem, the shared resources, theres always the issues of that
r: we should put out a survey of "howd you hear about sudo, what do ou see, what things are you apart of?" (fixit clinic, radio night, etc)
r: have a laptop read with survey
mz: cryptpad? i have done stuff before i can help set it up

mz: outreach is good - community stuff isn't realy known like this, hackerspaces vs tech spaces not really known to the people

mz: back to the basics type - excellence, do-acray, consensus - trifecta of anarchy

== Recap ==:
communication methods
- discord/signal/wiki/forum/email/Matrix
fundraising:

- workshops (basics/one-off lectures + people arrive with questions)

- fundraisers, raffles, video screenings, social networking

- outreach, survey, social networking events

- offer serices to senior home centers, have individuals go to senior homes to offer classes ask Alice

- grant writing night

events:
r: brainstorm past events, to come up with past events to see what we could do again in the future
mz: just started some opensource events meetup
(mk and mz chat about FOSS and CoreBoot stuff)

(chatter about grant writing night, process of grant writing)
D: have we connected with berkley law? they have a small business type night and help with nonprofits, ucberkeleylaw www.law.berkeley.edu, I can look into that before I leave
D: not great for learning to do grant writing, they have clinics that are profit based sort of

mk: on that note, do we have sort of "normal" social media for public outreach?

- weekly instagram, or stories work like flyers that other people can repost

- streaming events (twitch, youtube, tiktok)

== Process membership applications ==

-----------------------------------

Meetings

2026-08-31T03:29:12Z

Indoorjetpacks: /* Archive */

__NOTOC__
'''Twice a month'''
'''Every ''second'' Thursday 19:00 (7 PM)'''
'''Every ''last'' Sunday 16:00 (4 PM)'''
Check upcoming events: https://sudoroom.org/events/categories/member-meeting/

== Overview ==
Sudo Room's official meetings are bureaucratic, sometimes fun, and usually more functional than rumored. We try to handle conflicts respectfully.


<pre>sudo make meeting --excellence TRUE</pre>

== Join ==
We meet in a hybrid format, in-person at Sudo Room and online.

[[Directions | Getting to Sudo Room]]

[https://meet.waag.org/turtlesturtlesturtles Online Jitsi video conference]

== Future meeting topics ==
Add topics to this etherpad: https://pad.riseup.net/p/sudo-proposals

If you have something you want addressed consider attending and helping to guide the discussion on it.

== Etherpad ==
We keep our agenda on an etherpad. The etherpad is projected on a big screen for everyone to see. Anyone who knows the URL can collaboratively edit it on their laptop. After the meeting, its contents are copied to our wiki - that's how we keep record. Then we clear it for the next meeting and people can add items throughout the week. Ideally someone posts a summary to the mailing list, but that doesn't always happen.

Unfortunately, in the past our etherpad has caught the attention of online troll dens who like to overwhelm it and make it unusable. For this reason, we don't post the address online. Sorry! '''These addresses''' had been used in the past, and '''are obsolete''':

* https://pad.riseup.net/p/sudoroommeeting

See [[Meeting template]] when starting a new meeting!

== Archive ==
Each past meeting gets its own page, and we link to them here.

{| class="wikitable sortable mw-collapsible"
! colspan="3"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | new member interviews
! class="unsortable" | comments
|-
| [[ Meeting Notes 2026-08-30|2026-08-30 ]]
|
| fundraising, data center peition, workshops
|-
|-
| [[ Meeting Notes 2026-05-31|2026-05-31]]
|
| member onboarding, member matters, memorial at omni, 2nd hack night, governance
|-
|-
| [[ Meeting Notes 2026-04-26|2026-04-26]]
|
| long meeting. income streams, wiki, 3d print
|-
|-
| [[ Meeting Notes 2026-03-29|2026-03-29]]
|
| short meeting. We need more monthly $$ contributions!
|-
|-
| [[ Meeting Notes 2026-02-22|2026-02-22]]
|
| Member Matters, Name tags
|-
|-
| [[ Meeting Notes 2026-02-12|2026-02-12]]
|
|-
|-
| [[Meeting Notes 2026-01-25|2026-01-25]]
|
| matrix, thursday party once a month, new members, overdue for board member elections, finances, emailing lapsed members results
|-
|-
| [[Meeting Notes 2026-01-15|2026-01-15]]
|
| Emailing lapsed members,Member Matters migration,Discourse forum for sudoroom, events, new member applications
|-
|-
| [[Meeting Notes 2025-12-28|2025-12-28]]
|
| money, Member Matters, communication, recurring member meetings, wiki meeting, SR member conflict, new members
|-
|-
| [[Meeting Notes 2025-10-12|2025-10-12]]
|
| Member Matters, membership
|-
|-
| [[Meeting Notes 2025-09-14|2025-09-14]]
|
| back door progress, budget, Membership approvals and process discussion, events, fundraising
|-
|-
| [[Meeting Notes 2025-07-16|2025-07-16]]
|
| apartheid free comunities pledge, weekly finance report back labor
|-
| [[Meeting Notes 2025-05-28|2025-05-28]]
|
| Membership, Apartheid Free Zone proposal, new events
|-
|-
| [[Meeting Notes 2025-05-14|2025-05-14]]
|
| Nonprofit Organizing meeting
|-
|-
| [[Meeting Notes 2024-12-11|2024-12-11]]
|
| member voting quorum for new bylaws decided
|-
|-
| [[Meeting Notes 2024-11-21|2024-11-21]]
|
| creating new bylaws, clearing out space for CC, need to remove items below stairwell
|-
|-
| [[Meeting Notes 2024-08-21|2024-08-21]]
|
| discussing new CALLI/EB PREC lease
|-
|-
| [[Meeting Notes 2024-06-12|2024-06-12]]
|
| williams proposal for new projects in sudoroom
|-
|-
| [[Meeting Notes 2024-03-27|2024-03-27]]
|
| alex steps down as delegate, draft new collective requirements
|-
|-
| [[Meeting Notes 2024-03-06|2024-03-06]]
|
| omni bylaw discussion (majority to majority + 1), wheelchair lift gate plans
|-
|-
| [[Meeting Notes 2024-02-28|2024-02-28]]
|
| approve bylaw changes and deb gives collective membership. fundraising requests
|-
|-
| [[Meeting Notes 2024-02-21|2024-02-21]]
|
| another recap meeting. call for SR volunteers for maker fair on 25th and for the fundraising wg
|-
|-
| [[Meeting Notes 2024-02-14|2024-02-14]]
|
| CAST meeting recap, Deb Gives collective app, laser class march 13
|-
|-
| [[Meeting Notes 2024-01-31|2024-01-31]]
|
| PP collective app, omni officer nominations, ed update
|-
|-
| [[Meeting Notes 2024-01-24|2024-01-24]]
|
| Jamal hiring contract, peoples programs proposal, Missey, CIM, land trusts, LLC update
|-
|-
| [[Meeting Notes 2024-01-17|2024-01-17]]
|
| foreclosure worst outcome, alex voted delegate
|-
|-
|-
| [[Meeting Notes 2024-01-10|2024-01-10]]
|
| accountability, bans, omni executive director discussion
|-
|-
|-
| [[Meeting Notes 2024-01-03|2024-01-03]]
|
|
|-
|-
| [[Meeting Notes 2023-12-27|2023-12-27]]
|
| PP co-ownership proposal, future imaginations
|-
|-
| [[Meeting Notes 2023-12-20|2023-12-20]]
|
| PP proposal and counterproposals in advance of omni meeting
|-
|-
| [[Meeting Notes 2023-12-13|2023-12-13]]
|
| PP proposal, proposal to set up LLC
|-
|-
| [[Meeting Notes 2023-11-02|2023-11-02]]
|
| omni collective statement and finances
|-
|-
| [[Meeting Notes 2023-10-05|2023-10-05]]
|
| informal, how to make sudoroom more welcoming, delegate position and duties
|-
| [[Meeting Notes 2023-09-27|2023-09-27]]
|
|
|-
| [[Meeting Notes 2023-09-20|2023-09-20]]
|
|
|-
| [[Meeting Notes 2023-09-06|2023-09-06]]
|
|
|-
| [[Meeting Notes 2023-08-02|2023-08-02]]
|
| event planning
|-
| [[Meeting Notes 2023-07-05|2023-07-05]]
|
| cnc router, organizing ourselves
|-
| [[Meeting Notes 2023-06-07|2023-06-07]]
| none
| member stats, save omni, keeping space clean, event ideas
|-
| [[Meeting Notes 2023-03-01|2023-03-01]]
| Our big March Meeting
| Plans for March
|-
| [[Meeting Notes 2023-01-25|2023-01-25]]
| low stakes meeting
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2023-01-11|2023-01-11]]
| Start of the new year
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2022-04-06|2022-04-06]]
| Arthur Eva PWM PB
| Four new members, plus two proposals
|-
| [[Meeting Notes 2021-06-02|2021-06-02]]
| kabirdas
| electrical and ventilation
|-
| | [[Meeting Notes 2021-05-26|2021-05-26]]
|
| Reopening, project and event ideas
|-
| [[Meeting Notes 2021-05-19|2021-05-19]]
| Nik
| Reopening, access control, computers
|-
| [[Meeting Notes 2021-05-12|2021-05-12]]
|
| Sudo Room decides to continue existing and stuff
|-
| [[Sudoroom_Meeting_2019_04_03|2019-04-03]]
|
| discussion & consensus about GCEA proposals & paying Jenny for bookkeeping
|-
| [[Meeting_Notes_2018-04-11|2018-04-11]]
| Rich
| Steve banned, omni proposals mentioned but not discussed
|-
| [[Meeting_Notes_2018-03-14|2018-03-14]]
| Tom Levine Andrew Vaziri
| Change to membership process passed, endorsing statement from The Village to City, discussion of conflict w/ Steve
|-
| [[Meeting_Notes_2018-01-10|2018-01-10]]
| Jacques Noah
| melissa and sierk as new omni delegates;
|-
| [[Meeting_Notes_2017-12-13|2017-12-13]]
| * Adam Bredenberg Melissa Crow Pato Adam Eric Jan
| discussion of finances, omni cafe proposal discussion
|-
| [[Meeting_Notes_2017-11-29|2017-11-29]]
|
| Another irregular meeting, with two topics of interest.
|-
| [[Meeting_Notes_2017-11-08|2017-11-08]]
|
|
|-
| [[Meeting_Notes_2017-11-01|2017-11-01]]
|
| Not a usual meeting date, but notes were taken.
|-
| [[Meeting_Notes_2017-08-13|2017-08-13]]
|
|
|-
| [[Meeting_Notes_2017-08-09|2017-08-09]]
| Kyle Matt Rayc
|
|-
| [[Meeting_Notes_2017-07-12|2017-07-12]]
|
|
|-
| [[Meeting_Notes_2017-05-10|2017-05-10]]
| Corey Travis
|
|-
| [[Meeting_Notes_2017-04-12|2017-04-12]]
|
|
|-
| [[Meeting_Notes_2017-03-08|2017-03-08]]
|
|
|-
| [[Meeting_Notes_2017-02-08|2017-02-08]]
|
|
|-
| [[Meeting_Notes_2017-01-25|2017-01-25]]
|
|
|-
| [[Meeting_Notes_2017-01-11|2017-01-11]]
|
|
|-
| [[Meeting_Notes_2017-01-04|2017-01-04]]
|
|
|-
| [[Meeting_Notes_2016-12-14|2016-12-14]]
|
|
|-
| [[Meeting_Notes_2016-11-16|2016-11-16]]
|
|
|-
| [[Meeting_Notes_2016-11-09|2016-11-09]]
|
|
|-
| [[Meeting_Notes_2016-10-12|2016-10-12]]
| Vienna
|
|-
| [[Meeting_Notes_2016-09-14|2016-09-14]]
| T Maes Evan Short
|
|-
| [[Meeting_Notes_2016-08-17|2016-08-17]]
|
|
|-
| [[Meeting_Notes_2016-08-10|2016-08-10]]
|
|
|-
| [[Meeting_Notes_2016-07-20|2016-07-20]]
|
|
|-
| [[Meeting_Notes_2016-07-13|2016-07-13]]
|
|
|-
| [[Meeting_Notes_2016-06-15|2016-06-15]]
| Eric Wen-qing Alex Yvonne
|
|-
| [[Meeting_Notes_2016-06-08|2016-06-08]]
| Tim Chris Lindsey
|
|-
| [[Meeting_Notes_2016-05-11|2016-05-11]]
| James Corey Benjamin Huang
|
|-
| [[Meeting_Notes_2016-04-27|2016-04-27]]
| Elliot
|
|-
| [[Meeting_Notes_2016-04-20|2016-04-20]]
| Syd
|
|-
| [[Meeting_Notes_2016-04-13|2016-04-13]]
| Abhiram Pete Forsyth Dirty Bill Chris Jamie
|
|-
| [[Meeting_Notes_2016-04-06|2016-04-06]]
| Jacob Jason
|
|-
| 2016-03-30
|rowspan=6 colspan=2 align=center|We totally flaked for the entire month of March.
|-
| 2016-03-23
|-
| 2016-03-23
|-
| 2016-03-16
|-
| 2016-03-09
|-
| 2016-03-02
|-
| [[Meeting_Notes_2016-02-24|2016-02-24]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-17|2016-02-17]]
| bstack
|
|-
| [[Meeting_Notes_2016-02-10|2016-02-10]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-03|2016-02-03]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-27|2016-01-27]]
| Jay
|
|-
| [[Meeting_Notes_2016-01-20|2016-01-20]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-13|2016-01-13]]
|
| cancelled-ish
|-
| [[Meeting_Notes_2016-01-06|2016-01-06]]
| nathan Nick
|
|-
| [[Meeting_Notes_2015-12-30|2015-12-30]]
| Charley
|
|-
| 2015-12-23
|
| no signs of having happened
|-
| [[Meeting_Notes_2015-12-16|2015-12-16]]
| Daisy
|
|-
| [[Meeting_Notes_2015-12-09|2015-12-09]]
|
|
|-
| [[Meeting_Notes_2015-12-02|2015-12-02]]
| Max
|
|-
| [[Meeting_Notes_2015-11-25|2015-11-25]]
|
| didn't really happen, blame thanksgiving
|-
| [[Meeting_Notes_2015-11-18|2015-11-18]]
| morgan
|
|-
| [[Meeting_Notes_2015-11-11|2015-11-11]]
| Kwaku Gracie Micolah
|
|-
| [[Meeting_Notes_2015-11-04|2015-11-04]]
| dane
|
|-
| [[Meeting_Notes_2015-10-28|2015-10-28]]
| Andrew
|
|-
| [[Meeting Notes 2015-10-21|2015-10-21]]
| Merry
|
|-
| [[Meeting Notes 2015-10-14|2015-10-14]]
| Alex Lef Mari
|
|-
| [[Meeting Notes 2015-10-07|2015-10-07]]
| Tom Daron
|
|-
| [[Meeting Notes 2015-09-30|2015-09-30]]
|
| Insufficient critical mass
|-
| [[Meeting Notes 2015-09-23|2015-09-23]]
| Ari
|
|-
| [[Meeting Notes 2015-09-16|2015-09-16]]
| david
|
|-
| [[Meeting Notes 2015-09-09|2015-09-09]]
|
|
|-
| [[Meeting Notes 2015-09-02|2015-09-02]]
| Benji
|
|-
| [[Meeting Notes 2015-08-26|2015-08-26]]
|
|
|-
| 2015-08-19
|
| nobody showed up
|-
| [[Meeting Notes 2015-08-12|2015-08-12]]
|
|
|-
| [[Meeting Notes 2015-08-05|2015-08-05]]
|
|
|-
| [[Meeting Notes 2015-07-29|2015-07-29]]
|
|
|-
| [[Meeting_Notes_2015-07-22|2015-07-22]]
|
|
|-
| [[Meeting_Notes_2015-07-15|2015-07-15]]
|
|
|-
| [[Meeting_Notes_2015-07-08|2015-07-08]]
|
|
|-
| [[Meeting_Notes_2015-07-01|2015-07-01]]
|
|
|-
| [[Meeting_Notes_2015-06-24|2015-06-24]]
|
|
|-
| [[Meeting_Notes_2015-06-17|2015-06-17]]
|
|
|-
| [[Meeting_Notes_2015-06-10|2015-06-10]]
|
|
|-
| [[Meeting_Notes_2015-06-03|2015-06-03]]
|
|
|-
| [[Meeting_Notes_2015-05-27|2015-05-27]]
|
|
|-
| [[Meeting_Notes_2015-05-20|2015-05-20]]
|
|
|-
| [[Meeting_Notes_2015-05-13|2015-05-13]]
|
|
|-
| [[Meeting_Notes_2015-05-06|2015-05-06]]
|
|
|-
| [[Meeting_Notes_2015-04-29|2015-04-29]]
|
|
|-
| [[Meeting_Notes_2015-04-22|2015-04-22]]
|
|
|-
| [[Meeting_Notes_2015-04-15|2015-04-15]]
|
|
|-
| [[Meeting_Notes_2015-04-08|2015-04-08]]
|
|
|-
| [[Meeting_Notes_2015-04-01|2015-04-01]]
|
|
|-
| [[Meeting_Notes_2015-03-25|2015-03-25]]
|
|
|-
| [[Meeting_Notes_2015-03-18|2015-03-18]]
|
|
|-
| [[Meeting_Notes_2015-03-11|2015-03-11]]
|
|
|-
| [[Meeting_Notes_2015-03-04|2015-03-04]]
|
|
|-
| [[Meeting_Notes_2015-02-25|2015-02-25]]
|
|
|-
| [[Meeting_Notes_2015-02-18|2015-02-18]]
|
|
|-
| [[Meeting_Notes_2015-02-11|2015-02-11]]
|
|
|-
| [[Meeting_Notes_2015-02-04|2015-02-04]]
|
|
|-
| [[Meeting_Notes_2015-01-28|2015-01-28]]
|
|
|-
| [[Meeting_Notes_2015-01-21|2015-01-21]]
|
|
|-
| [[Meeting_Notes_2015-01-14|2015-01-14]]
|
|
|-
| [[Meeting_Notes_2015-01-07|2015-01-07]]
|
|
|-
| [[Meeting_Notes_2014-12-31|2014-12-31]]
|
|
|-
| [[Meeting_Notes_2014-12-24|2014-12-24]]
|
|
|-
| [[Meeting_Notes_2014-12-17|2014-12-17]]
|
|
|-
| [[Meeting_Notes_2014-12-10|2014-12-10]]
|
|
|-
| [[Meeting_Notes_2014-12-03|2014-12-03]]
|
|
|-
| [[Meeting_Notes_2014-11-26|2014-11-26]]
|
|
|-
| [[Meeting_Notes_2014-11-19|2014-11-19]]
|
|
|-
| [[Meeting_Notes_2014-11-12|2014-11-12]]
|
|
|-
| [[Meeting_Notes_2014-11-05|2014-11-05]]
|
|
|-
| [[Meeting_Notes_2014-10-29|2014-10-29]]
|
|
|-
| [[Meeting_Notes_2014-10-27|2014-10-27]]
|
| Board of Directors Meeting
|-
| [[Meeting_Notes_2014-10-22|2014-10-22]]
|
|
|-
| [[Meeting_Notes_2014-10-15|2014-10-15]]
|
|
|-
| [[Meeting_Notes_2014-10-08|2014-10-08]]
|
|
|-
| [[Meeting_Notes_2014-10-01|2014-10-01]]
|
|
|-
| [[Meeting_Notes_2014-09-24|2014-09-24]]
|
|
|-
| [[Meeting_Notes_2014-09-17|2014-09-17]]
|
|
|-
| [[Meeting_Notes_2014-09-10|2014-09-10]]
|
|
|-
| [[Meeting_Notes_2014-09-03|2014-09-03]]
|
|
|-
| [[Meeting_Notes_2014-08-27|2014-08-27]]
|
|
|-
| [[Meeting_Notes_2014-08-20|2014-08-20]]
|
|
|-
| [[Meeting_Notes_2014-08-13|2014-08-13]]
|
|
|-
| [[Meeting_Notes_2014-08-06|2014-08-06]]
|
|
|-
| [[Meeting_Notes_2014-07-30|2014-07-30]]
|
|
|-
| [[Meeting_Notes_2014-07-23|2014-07-23]]
|
|
|-
| [[Meeting_Notes_2014-07-16|2014-07-16]]
|
|
|-
| [[Meeting_Notes_2014-07-09|2014-07-09]]
|
|
|-
| [[Meeting_Notes_2014-07-02|2014-07-02]]
|
| First meeting in our new space @ 4799 Shattuck!
|-
| 2014-06-25
|
| big moving day, no meeting notes
|-
| [[Meeting_Notes_2014-06-18|2014-06-18]]
|
|
|-
| [[Meeting_Notes_2014-06-11|2014-06-11]]
|
|
|-
| [[Meeting_Notes_2014-06-04|2014-06-04]]
|
|
|-
| [[Meeting Notes 2014-05-28|2014-05-28]]
|
|
|-
| [[Meeting Notes 2014-05-21|2014-05-21]]
|
|
|-
| [[Meeting Notes 2014-05-14|2014-05-14]]
|
|
|-
| [[Meeting Notes 2014-05-07|2014-05-07]]
|
|
|-
| [[Meeting Notes 2014-04-30|2014-04-30]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-23|2014-04-23]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-16|2014-04-16]]
|
|
|-
| [[Meeting Notes 2014-04-09|2014-04-09]]
|
|
|-
| [[Meeting Notes 2014-04-02|2014-04-02]]
|
| mostly reboot
|-
| [[Meeting Notes 2014-03-26|2014-03-26]]
|
|
|-
| [[Meeting Notes 2014-03-19|2014-03-19]]
|
|
|-
| [[Meeting Notes 2014-03-12|2014-03-12]]
|
|
|-
| [[Meeting Notes 2014-03-05|2014-03-05]]
|
| Special edition on reboot
|-
| [[Meeting Notes 2014-02-26|2014-02-26]]
|
|
|-
| [[Meeting Notes 2014-02-19|2014-02-19]]
|
|
|-
| [[Meeting Notes 2014-02-12|2014-02-12]]
|
|
|-
| [[Meeting Notes 2014-02-05|2014-02-05]]
|
|
|-
| [[Meeting Notes 2014-01-29|2014-01-29]]
|
|
|-
| [[Meeting Notes 2014-01-22|2014-01-22]]
|
|
|-
| [[Meeting Notes 2014-01-15|2014-01-15]]
|
|
|-
| [[Meeting Notes 2014-01-08|2014-01-08]]
|
|
|-
| [[Meeting Notes 2014-01-01|2014-01-01]]
|
|
|-
| [[Meeting Notes 2013-12-25|2013-12-25]]
|
|
|-
| [[Meeting Notes 2013-12-18|2013-12-18]]
|
|
|-
| [[Meeting Notes 2013-12-11|2013-12-11]]
|
|
|-
| [[Meeting Notes 2013-12-04|2013-12-04]]
|
|
|-
| [[Meeting Notes 2013-11-27|2013-11-27]]
|
|
|-
| [[Meeting Notes 2013-11-20|2013-11-20]]
|
|
|-
| [[Meeting Notes 2013-11-13|2013-11-13]]
|
|
|-
| [[Meeting Notes 2013-11-06|2013-11-06]]
|
|
|-
| [[Meeting Notes 2013-10-30|2013-10-30]]
|
|
|-
| [[Meeting Notes 2013-10-23|2013-10-23]]
|
|
|-
| [[Meeting Notes 2013-10-16|2013-10-16]]
|
|
|-
| [[Meeting Notes 2013-10-02|2013-10-02]]
|
|
|-
| [[Meeting Notes 2013-09-25|2013-09-25]]
|
|
|-
| [[Meeting Notes 2013-09-18|2013-09-18]]
|
|
|-
| [[Meeting Notes 2013-09-11|2013-09-11]]
|
|
|-
| [[Meeting Notes 2013-09-04|2013-09-04]]
|
|
|-
| [[Meeting Notes 2013-08-28|2013-08-28]]
|
|
|-
| [[Meeting Notes 2013-08-21|2013-08-21]]
|
|
|-
| [[Meeting Notes 2013-08-14|2013-08-14]]
|
|
|-
| [[Meeting Notes 2013-08-07|2013-08-07]]
|
|
|-
| [[Meeting Notes 2013-07-30|2013-07-30]]
|
|
|-
| [[Meeting Notes 2013-07-24|2013-07-24]]
|
|
|-
| [[Meeting Notes 2013-07-17|2013-07-17]]
|
|
|-
| [[Meeting Notes 2013-07-10|2013-07-10]]
|
|
|-
| [[Meeting Notes 2013-07-03|2013-07-03]]
|
|
|-
| [[Meeting Notes 2013-06-26|2013-06-26]]
|
|
|-
| [[Meeting Notes 2013-06-19|2013-06-19]]
|
|
|-
| [[Meeting Notes 2013-06-12|2013-06-12]]
|
|
|-
| [[Meeting Notes 2013-06-05|2013-06-05]]
|
|
|-
| [[Meeting Notes 2013-05-29|2013-05-29]]
|
|
|-
| [[Meeting Notes 2013-05-22|2013-05-22]]
|
|
|-
| [[Meeting Notes 2013-05-15|2013-05-15]]
|
|
|-
| [[Meeting Notes 2013-05-08|2013-05-08]]
|
|
|-
| [[Meeting Notes 2013-05-01|2013-05-01]]
|
|
|-
| [[Meeting Notes 2013-04-24|2013-04-24]]
|
|
|-
| [[Meeting Notes 2013-04-17|2013-04-17]]
|
|
|-
| [[Meeting Notes 2013-04-11|2013-04-11]]
|
|
|-
| [[Meeting Notes 2013-04-03|2013-04-03]]
|
|
|-
| [[Meeting Notes 2013-03-27|2013-03-27]]
|
|
|-
| 2013-03-20
|
| no notes?
|-
| [[Meeting Notes 2013-03-13|2013-03-13]]
|
|
|-
| [[Meeting Notes 2013-03-06|2013-03-06]]
|
|
|-
| [[Meeting Notes 2013-02-27|2013-02-27]]
|
|
|-
| [[Meeting Notes 2013-02-20|2013-02-20]]
|
|
|-
| [[Meeting Notes 2013-02-13|2013-02-13]]
|
|
|-
| [[Meeting Notes 2013-02-06|2013-02-06]]
|
|
|-
| [[Meeting Notes 2013-01-30|2013-01-30]]
|
|
|-
| [[Meeting Notes 2013-01-23|2013-01-23]]
|
|
|-
| [[Meeting Notes 2013-01-16|2013-01-16]]
|
|
|-
| [[Meeting Notes 2013-01-09|2013-01-09]]
|
|
|-
| [[Meeting Notes 2013-01-02|2013-01-02]]
|
|
|-
| [[Sudo room/12-26-2012 Meetup|2012-12-26]]
|
|
|-
| [[Sudo room/12-19-2012 Meetup|2012-12-19]]
|
|
|-
| [[Sudo room/12-12-2012 Meetup|2012-12-12]]
|
|
|-
| [[Sudo room/12-05-2012 Meetup|2012-12-05]]
|
|
|-
| [[Sudo room/11-28-2012 Meetup|2012-11-28]]
|
|
|-
| [[Sudo room/11-21-2012 Meetup|2012-11-21]]
|
|
|-
| [[Sudo room/11-14-2012 Meetup|2012-11-14]]
|
|
|-
| [[Sudo room/11-7-2012 Meetup|2012-11-07]]
|
|
|-
| [[Sudo room/10-31-2012 Meetup|2012-10-31]]
|
|
|-
| [[Sudo room/10-24-2012 Meetup|2012-10-24]]
|
|
|-
| [[Sudo room/10-17-2012 Meetup|2012-10-17]]
|
|
|-
| [[Sudo room/10-10-2012 Meetup|2012-10-10]]
|
|
|-
| [[Sudo room/10-03-2012 Meetup|2012-10-03]]
|
|
|-
| [[Sudo room/09-26-2012 Meetup|2012-09-26]]
|
|
|-
| [[Sudo room/09-19-2012 Meetup|2012-09-19]]
|
|
|-
| [[Sudo room/09-12-2012 Meetup|2012-09-12]]
|
|
|-
| [[Sudo room/09-05-2012 Meetup|2012-09-05]]
|
|
|-
| [[Sudo room/08-29-2012 Meetup|2012-08-29]]
|
|
|-
| [[Sudo room/08-22-2012 Meetup|2012-08-22]]
|
|
|-
| [[Sudo room/08-13-2012 Meetup|2012-08-13]]
|
|
|-
| [[Sudo room/08-08-2012 Meetup|2012-08-08]]
|
|
|-
| [[Sudo room/08-01-2012 Meetup|2012-08-01]]
|
|
|-
| [[Sudo room/07-25-2012 Meetup|2012-07-25]]
|
|
|-
| [[Sudo room/07-18-2012 Meetup|2012-07-18]]
|
|
|-
| [[Sudo room/07-11-2012 Meetup|2012-07-11]]
|
|
|-
| [[Sudo room/07-04-2012 Meetup|2012-07-04]]
|
|
|-
| [[Sudo room/06-27-2012 Meetup|2012-06-27]]
|
|
|-
| [[Sudo room/06-20-2012 Meetup|2012-06-20]]
|
|
|-
| [[Sudo room/06-13-2012 Meetup|2012-06-13]]
|
|
|-
| [[Sudo room/06-06-2012 Meetup|2012-06-06]]
|
|
|-
| [[Sudo room/05-30-2012 Meetup|2012-05-30]]
|
|
|-
| [[Sudo room/05-23-2012 Meetup|2012-05-23]]
|
|
|-
| [[Sudo room/05-16-2012 Meetup|2012-05-16]]
|
|
|-
| 2012-05-09
|
| no notes?
|-
| 2012-05-02
|
| no notes?
|-
| [[Sudo room/04-25-2012 Meetup|2012-04-25]]
|
|
|-
| 2012-04-18
|
| no notes?
|-
| 2012-04-11
|
| no notes?
|-
| 2012-04-04
|
| no notes?
|-
| 2012-03-28
|
| no notes?
|-
| 2012-03-21
|
| no notes?
|-
| 2012-03-14
|
| no notes?
|-
| 2012-03-07
|
| no notes?
|-
| 2012-02-29
|
| no notes?
|-
| [[Sudo room/02-22-2012 Meetup|2012-02-22]]
|
|
|-
| 2012-02-15
|
| no notes?
|-
| 2012-02-08
|
| no notes?
|-
| [[Sudo room/02-01-2011 Meetup|2012-02-01]]
|
|
|-
| [[Sudo room/01-25-2011 Meetup|2012-01-25]]
|
|
|-
| [[Sudo room/01-18-2011 Meetup|2012-01-18]]
|
|
|-
| [[Sudo room/01-11-2011 Meetup|2012-01-11]]
|
|
|-
| [[Sudo room/01-04-2011 Meetup|2012-01-04]]
|
|
|-
| [[Sudo room/12-28-2011 Meetup|2011-12-28]]
|
|
|-
| [[Sudo room/12-21-2011 Meetup|2011-12-21]]
|
|
|-
| [[Sudo room/12-14-2011 Meetup|2011-12-14]]
|
|
|-
| [[Sudo room/12-07-2011 Meetup|2011-12-07]]
|
|
|-
| [[Sudo room/First Wed Meetup|2011-11-30]]
|
| @ Cafe Mediterraneum
|-
| [[Sudo room/Initial Meeting| Initial Meeting]]
|
| 2011-11-18, 12pm @ Actual Cafe
|}

[[Category:SudoRoom Organization]][[Category:Meetings]]

Meetings

2026-08-31T03:28:44Z

Indoorjetpacks: /* Archive */

__NOTOC__
'''Twice a month'''
'''Every ''second'' Thursday 19:00 (7 PM)'''
'''Every ''last'' Sunday 16:00 (4 PM)'''
Check upcoming events: https://sudoroom.org/events/categories/member-meeting/

== Overview ==
Sudo Room's official meetings are bureaucratic, sometimes fun, and usually more functional than rumored. We try to handle conflicts respectfully.


<pre>sudo make meeting --excellence TRUE</pre>

== Join ==
We meet in a hybrid format, in-person at Sudo Room and online.

[[Directions | Getting to Sudo Room]]

[https://meet.waag.org/turtlesturtlesturtles Online Jitsi video conference]

== Future meeting topics ==
Add topics to this etherpad: https://pad.riseup.net/p/sudo-proposals

If you have something you want addressed consider attending and helping to guide the discussion on it.

== Etherpad ==
We keep our agenda on an etherpad. The etherpad is projected on a big screen for everyone to see. Anyone who knows the URL can collaboratively edit it on their laptop. After the meeting, its contents are copied to our wiki - that's how we keep record. Then we clear it for the next meeting and people can add items throughout the week. Ideally someone posts a summary to the mailing list, but that doesn't always happen.

Unfortunately, in the past our etherpad has caught the attention of online troll dens who like to overwhelm it and make it unusable. For this reason, we don't post the address online. Sorry! '''These addresses''' had been used in the past, and '''are obsolete''':

* https://pad.riseup.net/p/sudoroommeeting

See [[Meeting template]] when starting a new meeting!

== Archive ==
Each past meeting gets its own page, and we link to them here.

{| class="wikitable sortable mw-collapsible"
! colspan="3"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | new member interviews
! class="unsortable" | comments
|-
|- [[ Meeting Notes 2026-08-30|2026-08-30 ]]
|
| fundraising, data center peition, workshops
|-
|-
| [[ Meeting Notes 2026-05-31|2026-05-31]]
|
| member onboarding, member matters, memorial at omni, 2nd hack night, governance
|-
|-
| [[ Meeting Notes 2026-04-26|2026-04-26]]
|
| long meeting. income streams, wiki, 3d print
|-
|-
| [[ Meeting Notes 2026-03-29|2026-03-29]]
|
| short meeting. We need more monthly $$ contributions!
|-
|-
| [[ Meeting Notes 2026-02-22|2026-02-22]]
|
| Member Matters, Name tags
|-
|-
| [[ Meeting Notes 2026-02-12|2026-02-12]]
|
|-
|-
| [[Meeting Notes 2026-01-25|2026-01-25]]
|
| matrix, thursday party once a month, new members, overdue for board member elections, finances, emailing lapsed members results
|-
|-
| [[Meeting Notes 2026-01-15|2026-01-15]]
|
| Emailing lapsed members,Member Matters migration,Discourse forum for sudoroom, events, new member applications
|-
|-
| [[Meeting Notes 2025-12-28|2025-12-28]]
|
| money, Member Matters, communication, recurring member meetings, wiki meeting, SR member conflict, new members
|-
|-
| [[Meeting Notes 2025-10-12|2025-10-12]]
|
| Member Matters, membership
|-
|-
| [[Meeting Notes 2025-09-14|2025-09-14]]
|
| back door progress, budget, Membership approvals and process discussion, events, fundraising
|-
|-
| [[Meeting Notes 2025-07-16|2025-07-16]]
|
| apartheid free comunities pledge, weekly finance report back labor
|-
| [[Meeting Notes 2025-05-28|2025-05-28]]
|
| Membership, Apartheid Free Zone proposal, new events
|-
|-
| [[Meeting Notes 2025-05-14|2025-05-14]]
|
| Nonprofit Organizing meeting
|-
|-
| [[Meeting Notes 2024-12-11|2024-12-11]]
|
| member voting quorum for new bylaws decided
|-
|-
| [[Meeting Notes 2024-11-21|2024-11-21]]
|
| creating new bylaws, clearing out space for CC, need to remove items below stairwell
|-
|-
| [[Meeting Notes 2024-08-21|2024-08-21]]
|
| discussing new CALLI/EB PREC lease
|-
|-
| [[Meeting Notes 2024-06-12|2024-06-12]]
|
| williams proposal for new projects in sudoroom
|-
|-
| [[Meeting Notes 2024-03-27|2024-03-27]]
|
| alex steps down as delegate, draft new collective requirements
|-
|-
| [[Meeting Notes 2024-03-06|2024-03-06]]
|
| omni bylaw discussion (majority to majority + 1), wheelchair lift gate plans
|-
|-
| [[Meeting Notes 2024-02-28|2024-02-28]]
|
| approve bylaw changes and deb gives collective membership. fundraising requests
|-
|-
| [[Meeting Notes 2024-02-21|2024-02-21]]
|
| another recap meeting. call for SR volunteers for maker fair on 25th and for the fundraising wg
|-
|-
| [[Meeting Notes 2024-02-14|2024-02-14]]
|
| CAST meeting recap, Deb Gives collective app, laser class march 13
|-
|-
| [[Meeting Notes 2024-01-31|2024-01-31]]
|
| PP collective app, omni officer nominations, ed update
|-
|-
| [[Meeting Notes 2024-01-24|2024-01-24]]
|
| Jamal hiring contract, peoples programs proposal, Missey, CIM, land trusts, LLC update
|-
|-
| [[Meeting Notes 2024-01-17|2024-01-17]]
|
| foreclosure worst outcome, alex voted delegate
|-
|-
|-
| [[Meeting Notes 2024-01-10|2024-01-10]]
|
| accountability, bans, omni executive director discussion
|-
|-
|-
| [[Meeting Notes 2024-01-03|2024-01-03]]
|
|
|-
|-
| [[Meeting Notes 2023-12-27|2023-12-27]]
|
| PP co-ownership proposal, future imaginations
|-
|-
| [[Meeting Notes 2023-12-20|2023-12-20]]
|
| PP proposal and counterproposals in advance of omni meeting
|-
|-
| [[Meeting Notes 2023-12-13|2023-12-13]]
|
| PP proposal, proposal to set up LLC
|-
|-
| [[Meeting Notes 2023-11-02|2023-11-02]]
|
| omni collective statement and finances
|-
|-
| [[Meeting Notes 2023-10-05|2023-10-05]]
|
| informal, how to make sudoroom more welcoming, delegate position and duties
|-
| [[Meeting Notes 2023-09-27|2023-09-27]]
|
|
|-
| [[Meeting Notes 2023-09-20|2023-09-20]]
|
|
|-
| [[Meeting Notes 2023-09-06|2023-09-06]]
|
|
|-
| [[Meeting Notes 2023-08-02|2023-08-02]]
|
| event planning
|-
| [[Meeting Notes 2023-07-05|2023-07-05]]
|
| cnc router, organizing ourselves
|-
| [[Meeting Notes 2023-06-07|2023-06-07]]
| none
| member stats, save omni, keeping space clean, event ideas
|-
| [[Meeting Notes 2023-03-01|2023-03-01]]
| Our big March Meeting
| Plans for March
|-
| [[Meeting Notes 2023-01-25|2023-01-25]]
| low stakes meeting
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2023-01-11|2023-01-11]]
| Start of the new year
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2022-04-06|2022-04-06]]
| Arthur Eva PWM PB
| Four new members, plus two proposals
|-
| [[Meeting Notes 2021-06-02|2021-06-02]]
| kabirdas
| electrical and ventilation
|-
| | [[Meeting Notes 2021-05-26|2021-05-26]]
|
| Reopening, project and event ideas
|-
| [[Meeting Notes 2021-05-19|2021-05-19]]
| Nik
| Reopening, access control, computers
|-
| [[Meeting Notes 2021-05-12|2021-05-12]]
|
| Sudo Room decides to continue existing and stuff
|-
| [[Sudoroom_Meeting_2019_04_03|2019-04-03]]
|
| discussion & consensus about GCEA proposals & paying Jenny for bookkeeping
|-
| [[Meeting_Notes_2018-04-11|2018-04-11]]
| Rich
| Steve banned, omni proposals mentioned but not discussed
|-
| [[Meeting_Notes_2018-03-14|2018-03-14]]
| Tom Levine Andrew Vaziri
| Change to membership process passed, endorsing statement from The Village to City, discussion of conflict w/ Steve
|-
| [[Meeting_Notes_2018-01-10|2018-01-10]]
| Jacques Noah
| melissa and sierk as new omni delegates;
|-
| [[Meeting_Notes_2017-12-13|2017-12-13]]
| * Adam Bredenberg Melissa Crow Pato Adam Eric Jan
| discussion of finances, omni cafe proposal discussion
|-
| [[Meeting_Notes_2017-11-29|2017-11-29]]
|
| Another irregular meeting, with two topics of interest.
|-
| [[Meeting_Notes_2017-11-08|2017-11-08]]
|
|
|-
| [[Meeting_Notes_2017-11-01|2017-11-01]]
|
| Not a usual meeting date, but notes were taken.
|-
| [[Meeting_Notes_2017-08-13|2017-08-13]]
|
|
|-
| [[Meeting_Notes_2017-08-09|2017-08-09]]
| Kyle Matt Rayc
|
|-
| [[Meeting_Notes_2017-07-12|2017-07-12]]
|
|
|-
| [[Meeting_Notes_2017-05-10|2017-05-10]]
| Corey Travis
|
|-
| [[Meeting_Notes_2017-04-12|2017-04-12]]
|
|
|-
| [[Meeting_Notes_2017-03-08|2017-03-08]]
|
|
|-
| [[Meeting_Notes_2017-02-08|2017-02-08]]
|
|
|-
| [[Meeting_Notes_2017-01-25|2017-01-25]]
|
|
|-
| [[Meeting_Notes_2017-01-11|2017-01-11]]
|
|
|-
| [[Meeting_Notes_2017-01-04|2017-01-04]]
|
|
|-
| [[Meeting_Notes_2016-12-14|2016-12-14]]
|
|
|-
| [[Meeting_Notes_2016-11-16|2016-11-16]]
|
|
|-
| [[Meeting_Notes_2016-11-09|2016-11-09]]
|
|
|-
| [[Meeting_Notes_2016-10-12|2016-10-12]]
| Vienna
|
|-
| [[Meeting_Notes_2016-09-14|2016-09-14]]
| T Maes Evan Short
|
|-
| [[Meeting_Notes_2016-08-17|2016-08-17]]
|
|
|-
| [[Meeting_Notes_2016-08-10|2016-08-10]]
|
|
|-
| [[Meeting_Notes_2016-07-20|2016-07-20]]
|
|
|-
| [[Meeting_Notes_2016-07-13|2016-07-13]]
|
|
|-
| [[Meeting_Notes_2016-06-15|2016-06-15]]
| Eric Wen-qing Alex Yvonne
|
|-
| [[Meeting_Notes_2016-06-08|2016-06-08]]
| Tim Chris Lindsey
|
|-
| [[Meeting_Notes_2016-05-11|2016-05-11]]
| James Corey Benjamin Huang
|
|-
| [[Meeting_Notes_2016-04-27|2016-04-27]]
| Elliot
|
|-
| [[Meeting_Notes_2016-04-20|2016-04-20]]
| Syd
|
|-
| [[Meeting_Notes_2016-04-13|2016-04-13]]
| Abhiram Pete Forsyth Dirty Bill Chris Jamie
|
|-
| [[Meeting_Notes_2016-04-06|2016-04-06]]
| Jacob Jason
|
|-
| 2016-03-30
|rowspan=6 colspan=2 align=center|We totally flaked for the entire month of March.
|-
| 2016-03-23
|-
| 2016-03-23
|-
| 2016-03-16
|-
| 2016-03-09
|-
| 2016-03-02
|-
| [[Meeting_Notes_2016-02-24|2016-02-24]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-17|2016-02-17]]
| bstack
|
|-
| [[Meeting_Notes_2016-02-10|2016-02-10]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-03|2016-02-03]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-27|2016-01-27]]
| Jay
|
|-
| [[Meeting_Notes_2016-01-20|2016-01-20]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-13|2016-01-13]]
|
| cancelled-ish
|-
| [[Meeting_Notes_2016-01-06|2016-01-06]]
| nathan Nick
|
|-
| [[Meeting_Notes_2015-12-30|2015-12-30]]
| Charley
|
|-
| 2015-12-23
|
| no signs of having happened
|-
| [[Meeting_Notes_2015-12-16|2015-12-16]]
| Daisy
|
|-
| [[Meeting_Notes_2015-12-09|2015-12-09]]
|
|
|-
| [[Meeting_Notes_2015-12-02|2015-12-02]]
| Max
|
|-
| [[Meeting_Notes_2015-11-25|2015-11-25]]
|
| didn't really happen, blame thanksgiving
|-
| [[Meeting_Notes_2015-11-18|2015-11-18]]
| morgan
|
|-
| [[Meeting_Notes_2015-11-11|2015-11-11]]
| Kwaku Gracie Micolah
|
|-
| [[Meeting_Notes_2015-11-04|2015-11-04]]
| dane
|
|-
| [[Meeting_Notes_2015-10-28|2015-10-28]]
| Andrew
|
|-
| [[Meeting Notes 2015-10-21|2015-10-21]]
| Merry
|
|-
| [[Meeting Notes 2015-10-14|2015-10-14]]
| Alex Lef Mari
|
|-
| [[Meeting Notes 2015-10-07|2015-10-07]]
| Tom Daron
|
|-
| [[Meeting Notes 2015-09-30|2015-09-30]]
|
| Insufficient critical mass
|-
| [[Meeting Notes 2015-09-23|2015-09-23]]
| Ari
|
|-
| [[Meeting Notes 2015-09-16|2015-09-16]]
| david
|
|-
| [[Meeting Notes 2015-09-09|2015-09-09]]
|
|
|-
| [[Meeting Notes 2015-09-02|2015-09-02]]
| Benji
|
|-
| [[Meeting Notes 2015-08-26|2015-08-26]]
|
|
|-
| 2015-08-19
|
| nobody showed up
|-
| [[Meeting Notes 2015-08-12|2015-08-12]]
|
|
|-
| [[Meeting Notes 2015-08-05|2015-08-05]]
|
|
|-
| [[Meeting Notes 2015-07-29|2015-07-29]]
|
|
|-
| [[Meeting_Notes_2015-07-22|2015-07-22]]
|
|
|-
| [[Meeting_Notes_2015-07-15|2015-07-15]]
|
|
|-
| [[Meeting_Notes_2015-07-08|2015-07-08]]
|
|
|-
| [[Meeting_Notes_2015-07-01|2015-07-01]]
|
|
|-
| [[Meeting_Notes_2015-06-24|2015-06-24]]
|
|
|-
| [[Meeting_Notes_2015-06-17|2015-06-17]]
|
|
|-
| [[Meeting_Notes_2015-06-10|2015-06-10]]
|
|
|-
| [[Meeting_Notes_2015-06-03|2015-06-03]]
|
|
|-
| [[Meeting_Notes_2015-05-27|2015-05-27]]
|
|
|-
| [[Meeting_Notes_2015-05-20|2015-05-20]]
|
|
|-
| [[Meeting_Notes_2015-05-13|2015-05-13]]
|
|
|-
| [[Meeting_Notes_2015-05-06|2015-05-06]]
|
|
|-
| [[Meeting_Notes_2015-04-29|2015-04-29]]
|
|
|-
| [[Meeting_Notes_2015-04-22|2015-04-22]]
|
|
|-
| [[Meeting_Notes_2015-04-15|2015-04-15]]
|
|
|-
| [[Meeting_Notes_2015-04-08|2015-04-08]]
|
|
|-
| [[Meeting_Notes_2015-04-01|2015-04-01]]
|
|
|-
| [[Meeting_Notes_2015-03-25|2015-03-25]]
|
|
|-
| [[Meeting_Notes_2015-03-18|2015-03-18]]
|
|
|-
| [[Meeting_Notes_2015-03-11|2015-03-11]]
|
|
|-
| [[Meeting_Notes_2015-03-04|2015-03-04]]
|
|
|-
| [[Meeting_Notes_2015-02-25|2015-02-25]]
|
|
|-
| [[Meeting_Notes_2015-02-18|2015-02-18]]
|
|
|-
| [[Meeting_Notes_2015-02-11|2015-02-11]]
|
|
|-
| [[Meeting_Notes_2015-02-04|2015-02-04]]
|
|
|-
| [[Meeting_Notes_2015-01-28|2015-01-28]]
|
|
|-
| [[Meeting_Notes_2015-01-21|2015-01-21]]
|
|
|-
| [[Meeting_Notes_2015-01-14|2015-01-14]]
|
|
|-
| [[Meeting_Notes_2015-01-07|2015-01-07]]
|
|
|-
| [[Meeting_Notes_2014-12-31|2014-12-31]]
|
|
|-
| [[Meeting_Notes_2014-12-24|2014-12-24]]
|
|
|-
| [[Meeting_Notes_2014-12-17|2014-12-17]]
|
|
|-
| [[Meeting_Notes_2014-12-10|2014-12-10]]
|
|
|-
| [[Meeting_Notes_2014-12-03|2014-12-03]]
|
|
|-
| [[Meeting_Notes_2014-11-26|2014-11-26]]
|
|
|-
| [[Meeting_Notes_2014-11-19|2014-11-19]]
|
|
|-
| [[Meeting_Notes_2014-11-12|2014-11-12]]
|
|
|-
| [[Meeting_Notes_2014-11-05|2014-11-05]]
|
|
|-
| [[Meeting_Notes_2014-10-29|2014-10-29]]
|
|
|-
| [[Meeting_Notes_2014-10-27|2014-10-27]]
|
| Board of Directors Meeting
|-
| [[Meeting_Notes_2014-10-22|2014-10-22]]
|
|
|-
| [[Meeting_Notes_2014-10-15|2014-10-15]]
|
|
|-
| [[Meeting_Notes_2014-10-08|2014-10-08]]
|
|
|-
| [[Meeting_Notes_2014-10-01|2014-10-01]]
|
|
|-
| [[Meeting_Notes_2014-09-24|2014-09-24]]
|
|
|-
| [[Meeting_Notes_2014-09-17|2014-09-17]]
|
|
|-
| [[Meeting_Notes_2014-09-10|2014-09-10]]
|
|
|-
| [[Meeting_Notes_2014-09-03|2014-09-03]]
|
|
|-
| [[Meeting_Notes_2014-08-27|2014-08-27]]
|
|
|-
| [[Meeting_Notes_2014-08-20|2014-08-20]]
|
|
|-
| [[Meeting_Notes_2014-08-13|2014-08-13]]
|
|
|-
| [[Meeting_Notes_2014-08-06|2014-08-06]]
|
|
|-
| [[Meeting_Notes_2014-07-30|2014-07-30]]
|
|
|-
| [[Meeting_Notes_2014-07-23|2014-07-23]]
|
|
|-
| [[Meeting_Notes_2014-07-16|2014-07-16]]
|
|
|-
| [[Meeting_Notes_2014-07-09|2014-07-09]]
|
|
|-
| [[Meeting_Notes_2014-07-02|2014-07-02]]
|
| First meeting in our new space @ 4799 Shattuck!
|-
| 2014-06-25
|
| big moving day, no meeting notes
|-
| [[Meeting_Notes_2014-06-18|2014-06-18]]
|
|
|-
| [[Meeting_Notes_2014-06-11|2014-06-11]]
|
|
|-
| [[Meeting_Notes_2014-06-04|2014-06-04]]
|
|
|-
| [[Meeting Notes 2014-05-28|2014-05-28]]
|
|
|-
| [[Meeting Notes 2014-05-21|2014-05-21]]
|
|
|-
| [[Meeting Notes 2014-05-14|2014-05-14]]
|
|
|-
| [[Meeting Notes 2014-05-07|2014-05-07]]
|
|
|-
| [[Meeting Notes 2014-04-30|2014-04-30]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-23|2014-04-23]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-16|2014-04-16]]
|
|
|-
| [[Meeting Notes 2014-04-09|2014-04-09]]
|
|
|-
| [[Meeting Notes 2014-04-02|2014-04-02]]
|
| mostly reboot
|-
| [[Meeting Notes 2014-03-26|2014-03-26]]
|
|
|-
| [[Meeting Notes 2014-03-19|2014-03-19]]
|
|
|-
| [[Meeting Notes 2014-03-12|2014-03-12]]
|
|
|-
| [[Meeting Notes 2014-03-05|2014-03-05]]
|
| Special edition on reboot
|-
| [[Meeting Notes 2014-02-26|2014-02-26]]
|
|
|-
| [[Meeting Notes 2014-02-19|2014-02-19]]
|
|
|-
| [[Meeting Notes 2014-02-12|2014-02-12]]
|
|
|-
| [[Meeting Notes 2014-02-05|2014-02-05]]
|
|
|-
| [[Meeting Notes 2014-01-29|2014-01-29]]
|
|
|-
| [[Meeting Notes 2014-01-22|2014-01-22]]
|
|
|-
| [[Meeting Notes 2014-01-15|2014-01-15]]
|
|
|-
| [[Meeting Notes 2014-01-08|2014-01-08]]
|
|
|-
| [[Meeting Notes 2014-01-01|2014-01-01]]
|
|
|-
| [[Meeting Notes 2013-12-25|2013-12-25]]
|
|
|-
| [[Meeting Notes 2013-12-18|2013-12-18]]
|
|
|-
| [[Meeting Notes 2013-12-11|2013-12-11]]
|
|
|-
| [[Meeting Notes 2013-12-04|2013-12-04]]
|
|
|-
| [[Meeting Notes 2013-11-27|2013-11-27]]
|
|
|-
| [[Meeting Notes 2013-11-20|2013-11-20]]
|
|
|-
| [[Meeting Notes 2013-11-13|2013-11-13]]
|
|
|-
| [[Meeting Notes 2013-11-06|2013-11-06]]
|
|
|-
| [[Meeting Notes 2013-10-30|2013-10-30]]
|
|
|-
| [[Meeting Notes 2013-10-23|2013-10-23]]
|
|
|-
| [[Meeting Notes 2013-10-16|2013-10-16]]
|
|
|-
| [[Meeting Notes 2013-10-02|2013-10-02]]
|
|
|-
| [[Meeting Notes 2013-09-25|2013-09-25]]
|
|
|-
| [[Meeting Notes 2013-09-18|2013-09-18]]
|
|
|-
| [[Meeting Notes 2013-09-11|2013-09-11]]
|
|
|-
| [[Meeting Notes 2013-09-04|2013-09-04]]
|
|
|-
| [[Meeting Notes 2013-08-28|2013-08-28]]
|
|
|-
| [[Meeting Notes 2013-08-21|2013-08-21]]
|
|
|-
| [[Meeting Notes 2013-08-14|2013-08-14]]
|
|
|-
| [[Meeting Notes 2013-08-07|2013-08-07]]
|
|
|-
| [[Meeting Notes 2013-07-30|2013-07-30]]
|
|
|-
| [[Meeting Notes 2013-07-24|2013-07-24]]
|
|
|-
| [[Meeting Notes 2013-07-17|2013-07-17]]
|
|
|-
| [[Meeting Notes 2013-07-10|2013-07-10]]
|
|
|-
| [[Meeting Notes 2013-07-03|2013-07-03]]
|
|
|-
| [[Meeting Notes 2013-06-26|2013-06-26]]
|
|
|-
| [[Meeting Notes 2013-06-19|2013-06-19]]
|
|
|-
| [[Meeting Notes 2013-06-12|2013-06-12]]
|
|
|-
| [[Meeting Notes 2013-06-05|2013-06-05]]
|
|
|-
| [[Meeting Notes 2013-05-29|2013-05-29]]
|
|
|-
| [[Meeting Notes 2013-05-22|2013-05-22]]
|
|
|-
| [[Meeting Notes 2013-05-15|2013-05-15]]
|
|
|-
| [[Meeting Notes 2013-05-08|2013-05-08]]
|
|
|-
| [[Meeting Notes 2013-05-01|2013-05-01]]
|
|
|-
| [[Meeting Notes 2013-04-24|2013-04-24]]
|
|
|-
| [[Meeting Notes 2013-04-17|2013-04-17]]
|
|
|-
| [[Meeting Notes 2013-04-11|2013-04-11]]
|
|
|-
| [[Meeting Notes 2013-04-03|2013-04-03]]
|
|
|-
| [[Meeting Notes 2013-03-27|2013-03-27]]
|
|
|-
| 2013-03-20
|
| no notes?
|-
| [[Meeting Notes 2013-03-13|2013-03-13]]
|
|
|-
| [[Meeting Notes 2013-03-06|2013-03-06]]
|
|
|-
| [[Meeting Notes 2013-02-27|2013-02-27]]
|
|
|-
| [[Meeting Notes 2013-02-20|2013-02-20]]
|
|
|-
| [[Meeting Notes 2013-02-13|2013-02-13]]
|
|
|-
| [[Meeting Notes 2013-02-06|2013-02-06]]
|
|
|-
| [[Meeting Notes 2013-01-30|2013-01-30]]
|
|
|-
| [[Meeting Notes 2013-01-23|2013-01-23]]
|
|
|-
| [[Meeting Notes 2013-01-16|2013-01-16]]
|
|
|-
| [[Meeting Notes 2013-01-09|2013-01-09]]
|
|
|-
| [[Meeting Notes 2013-01-02|2013-01-02]]
|
|
|-
| [[Sudo room/12-26-2012 Meetup|2012-12-26]]
|
|
|-
| [[Sudo room/12-19-2012 Meetup|2012-12-19]]
|
|
|-
| [[Sudo room/12-12-2012 Meetup|2012-12-12]]
|
|
|-
| [[Sudo room/12-05-2012 Meetup|2012-12-05]]
|
|
|-
| [[Sudo room/11-28-2012 Meetup|2012-11-28]]
|
|
|-
| [[Sudo room/11-21-2012 Meetup|2012-11-21]]
|
|
|-
| [[Sudo room/11-14-2012 Meetup|2012-11-14]]
|
|
|-
| [[Sudo room/11-7-2012 Meetup|2012-11-07]]
|
|
|-
| [[Sudo room/10-31-2012 Meetup|2012-10-31]]
|
|
|-
| [[Sudo room/10-24-2012 Meetup|2012-10-24]]
|
|
|-
| [[Sudo room/10-17-2012 Meetup|2012-10-17]]
|
|
|-
| [[Sudo room/10-10-2012 Meetup|2012-10-10]]
|
|
|-
| [[Sudo room/10-03-2012 Meetup|2012-10-03]]
|
|
|-
| [[Sudo room/09-26-2012 Meetup|2012-09-26]]
|
|
|-
| [[Sudo room/09-19-2012 Meetup|2012-09-19]]
|
|
|-
| [[Sudo room/09-12-2012 Meetup|2012-09-12]]
|
|
|-
| [[Sudo room/09-05-2012 Meetup|2012-09-05]]
|
|
|-
| [[Sudo room/08-29-2012 Meetup|2012-08-29]]
|
|
|-
| [[Sudo room/08-22-2012 Meetup|2012-08-22]]
|
|
|-
| [[Sudo room/08-13-2012 Meetup|2012-08-13]]
|
|
|-
| [[Sudo room/08-08-2012 Meetup|2012-08-08]]
|
|
|-
| [[Sudo room/08-01-2012 Meetup|2012-08-01]]
|
|
|-
| [[Sudo room/07-25-2012 Meetup|2012-07-25]]
|
|
|-
| [[Sudo room/07-18-2012 Meetup|2012-07-18]]
|
|
|-
| [[Sudo room/07-11-2012 Meetup|2012-07-11]]
|
|
|-
| [[Sudo room/07-04-2012 Meetup|2012-07-04]]
|
|
|-
| [[Sudo room/06-27-2012 Meetup|2012-06-27]]
|
|
|-
| [[Sudo room/06-20-2012 Meetup|2012-06-20]]
|
|
|-
| [[Sudo room/06-13-2012 Meetup|2012-06-13]]
|
|
|-
| [[Sudo room/06-06-2012 Meetup|2012-06-06]]
|
|
|-
| [[Sudo room/05-30-2012 Meetup|2012-05-30]]
|
|
|-
| [[Sudo room/05-23-2012 Meetup|2012-05-23]]
|
|
|-
| [[Sudo room/05-16-2012 Meetup|2012-05-16]]
|
|
|-
| 2012-05-09
|
| no notes?
|-
| 2012-05-02
|
| no notes?
|-
| [[Sudo room/04-25-2012 Meetup|2012-04-25]]
|
|
|-
| 2012-04-18
|
| no notes?
|-
| 2012-04-11
|
| no notes?
|-
| 2012-04-04
|
| no notes?
|-
| 2012-03-28
|
| no notes?
|-
| 2012-03-21
|
| no notes?
|-
| 2012-03-14
|
| no notes?
|-
| 2012-03-07
|
| no notes?
|-
| 2012-02-29
|
| no notes?
|-
| [[Sudo room/02-22-2012 Meetup|2012-02-22]]
|
|
|-
| 2012-02-15
|
| no notes?
|-
| 2012-02-08
|
| no notes?
|-
| [[Sudo room/02-01-2011 Meetup|2012-02-01]]
|
|
|-
| [[Sudo room/01-25-2011 Meetup|2012-01-25]]
|
|
|-
| [[Sudo room/01-18-2011 Meetup|2012-01-18]]
|
|
|-
| [[Sudo room/01-11-2011 Meetup|2012-01-11]]
|
|
|-
| [[Sudo room/01-04-2011 Meetup|2012-01-04]]
|
|
|-
| [[Sudo room/12-28-2011 Meetup|2011-12-28]]
|
|
|-
| [[Sudo room/12-21-2011 Meetup|2011-12-21]]
|
|
|-
| [[Sudo room/12-14-2011 Meetup|2011-12-14]]
|
|
|-
| [[Sudo room/12-07-2011 Meetup|2011-12-07]]
|
|
|-
| [[Sudo room/First Wed Meetup|2011-11-30]]
|
| @ Cafe Mediterraneum
|-
| [[Sudo room/Initial Meeting| Initial Meeting]]
|
| 2011-11-18, 12pm @ Actual Cafe
|}

[[Category:SudoRoom Organization]][[Category:Meetings]]

Meetings

2026-08-31T03:28:10Z

Indoorjetpacks: /* Archive */

__NOTOC__
'''Twice a month'''
'''Every ''second'' Thursday 19:00 (7 PM)'''
'''Every ''last'' Sunday 16:00 (4 PM)'''
Check upcoming events: https://sudoroom.org/events/categories/member-meeting/

== Overview ==
Sudo Room's official meetings are bureaucratic, sometimes fun, and usually more functional than rumored. We try to handle conflicts respectfully.


<pre>sudo make meeting --excellence TRUE</pre>

== Join ==
We meet in a hybrid format, in-person at Sudo Room and online.

[[Directions | Getting to Sudo Room]]

[https://meet.waag.org/turtlesturtlesturtles Online Jitsi video conference]

== Future meeting topics ==
Add topics to this etherpad: https://pad.riseup.net/p/sudo-proposals

If you have something you want addressed consider attending and helping to guide the discussion on it.

== Etherpad ==
We keep our agenda on an etherpad. The etherpad is projected on a big screen for everyone to see. Anyone who knows the URL can collaboratively edit it on their laptop. After the meeting, its contents are copied to our wiki - that's how we keep record. Then we clear it for the next meeting and people can add items throughout the week. Ideally someone posts a summary to the mailing list, but that doesn't always happen.

Unfortunately, in the past our etherpad has caught the attention of online troll dens who like to overwhelm it and make it unusable. For this reason, we don't post the address online. Sorry! '''These addresses''' had been used in the past, and '''are obsolete''':

* https://pad.riseup.net/p/sudoroommeeting

See [[Meeting template]] when starting a new meeting!

== Archive ==
Each past meeting gets its own page, and we link to them here.

{| class="wikitable sortable mw-collapsible"
! colspan="3"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | new member interviews
! class="unsortable" | comments
|-
|- [[ Meeting Notes 2026-08-30|2026-08-30]]
|
| fundraising, data center peition, workshops
|-
|-
| [[ Meeting Notes 2026-05-31|2026-05-31]]
|
| member onboarding, member matters, memorial at omni, 2nd hack night, governance
|-
|-
| [[ Meeting Notes 2026-04-26|2026-04-26]]
|
| long meeting. income streams, wiki, 3d print
|-
|-
| [[ Meeting Notes 2026-03-29|2026-03-29]]
|
| short meeting. We need more monthly $$ contributions!
|-
|-
| [[ Meeting Notes 2026-02-22|2026-02-22]]
|
| Member Matters, Name tags
|-
|-
| [[ Meeting Notes 2026-02-12|2026-02-12]]
|
|-
|-
| [[Meeting Notes 2026-01-25|2026-01-25]]
|
| matrix, thursday party once a month, new members, overdue for board member elections, finances, emailing lapsed members results
|-
|-
| [[Meeting Notes 2026-01-15|2026-01-15]]
|
| Emailing lapsed members,Member Matters migration,Discourse forum for sudoroom, events, new member applications
|-
|-
| [[Meeting Notes 2025-12-28|2025-12-28]]
|
| money, Member Matters, communication, recurring member meetings, wiki meeting, SR member conflict, new members
|-
|-
| [[Meeting Notes 2025-10-12|2025-10-12]]
|
| Member Matters, membership
|-
|-
| [[Meeting Notes 2025-09-14|2025-09-14]]
|
| back door progress, budget, Membership approvals and process discussion, events, fundraising
|-
|-
| [[Meeting Notes 2025-07-16|2025-07-16]]
|
| apartheid free comunities pledge, weekly finance report back labor
|-
| [[Meeting Notes 2025-05-28|2025-05-28]]
|
| Membership, Apartheid Free Zone proposal, new events
|-
|-
| [[Meeting Notes 2025-05-14|2025-05-14]]
|
| Nonprofit Organizing meeting
|-
|-
| [[Meeting Notes 2024-12-11|2024-12-11]]
|
| member voting quorum for new bylaws decided
|-
|-
| [[Meeting Notes 2024-11-21|2024-11-21]]
|
| creating new bylaws, clearing out space for CC, need to remove items below stairwell
|-
|-
| [[Meeting Notes 2024-08-21|2024-08-21]]
|
| discussing new CALLI/EB PREC lease
|-
|-
| [[Meeting Notes 2024-06-12|2024-06-12]]
|
| williams proposal for new projects in sudoroom
|-
|-
| [[Meeting Notes 2024-03-27|2024-03-27]]
|
| alex steps down as delegate, draft new collective requirements
|-
|-
| [[Meeting Notes 2024-03-06|2024-03-06]]
|
| omni bylaw discussion (majority to majority + 1), wheelchair lift gate plans
|-
|-
| [[Meeting Notes 2024-02-28|2024-02-28]]
|
| approve bylaw changes and deb gives collective membership. fundraising requests
|-
|-
| [[Meeting Notes 2024-02-21|2024-02-21]]
|
| another recap meeting. call for SR volunteers for maker fair on 25th and for the fundraising wg
|-
|-
| [[Meeting Notes 2024-02-14|2024-02-14]]
|
| CAST meeting recap, Deb Gives collective app, laser class march 13
|-
|-
| [[Meeting Notes 2024-01-31|2024-01-31]]
|
| PP collective app, omni officer nominations, ed update
|-
|-
| [[Meeting Notes 2024-01-24|2024-01-24]]
|
| Jamal hiring contract, peoples programs proposal, Missey, CIM, land trusts, LLC update
|-
|-
| [[Meeting Notes 2024-01-17|2024-01-17]]
|
| foreclosure worst outcome, alex voted delegate
|-
|-
|-
| [[Meeting Notes 2024-01-10|2024-01-10]]
|
| accountability, bans, omni executive director discussion
|-
|-
|-
| [[Meeting Notes 2024-01-03|2024-01-03]]
|
|
|-
|-
| [[Meeting Notes 2023-12-27|2023-12-27]]
|
| PP co-ownership proposal, future imaginations
|-
|-
| [[Meeting Notes 2023-12-20|2023-12-20]]
|
| PP proposal and counterproposals in advance of omni meeting
|-
|-
| [[Meeting Notes 2023-12-13|2023-12-13]]
|
| PP proposal, proposal to set up LLC
|-
|-
| [[Meeting Notes 2023-11-02|2023-11-02]]
|
| omni collective statement and finances
|-
|-
| [[Meeting Notes 2023-10-05|2023-10-05]]
|
| informal, how to make sudoroom more welcoming, delegate position and duties
|-
| [[Meeting Notes 2023-09-27|2023-09-27]]
|
|
|-
| [[Meeting Notes 2023-09-20|2023-09-20]]
|
|
|-
| [[Meeting Notes 2023-09-06|2023-09-06]]
|
|
|-
| [[Meeting Notes 2023-08-02|2023-08-02]]
|
| event planning
|-
| [[Meeting Notes 2023-07-05|2023-07-05]]
|
| cnc router, organizing ourselves
|-
| [[Meeting Notes 2023-06-07|2023-06-07]]
| none
| member stats, save omni, keeping space clean, event ideas
|-
| [[Meeting Notes 2023-03-01|2023-03-01]]
| Our big March Meeting
| Plans for March
|-
| [[Meeting Notes 2023-01-25|2023-01-25]]
| low stakes meeting
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2023-01-11|2023-01-11]]
| Start of the new year
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2022-04-06|2022-04-06]]
| Arthur Eva PWM PB
| Four new members, plus two proposals
|-
| [[Meeting Notes 2021-06-02|2021-06-02]]
| kabirdas
| electrical and ventilation
|-
| | [[Meeting Notes 2021-05-26|2021-05-26]]
|
| Reopening, project and event ideas
|-
| [[Meeting Notes 2021-05-19|2021-05-19]]
| Nik
| Reopening, access control, computers
|-
| [[Meeting Notes 2021-05-12|2021-05-12]]
|
| Sudo Room decides to continue existing and stuff
|-
| [[Sudoroom_Meeting_2019_04_03|2019-04-03]]
|
| discussion & consensus about GCEA proposals & paying Jenny for bookkeeping
|-
| [[Meeting_Notes_2018-04-11|2018-04-11]]
| Rich
| Steve banned, omni proposals mentioned but not discussed
|-
| [[Meeting_Notes_2018-03-14|2018-03-14]]
| Tom Levine Andrew Vaziri
| Change to membership process passed, endorsing statement from The Village to City, discussion of conflict w/ Steve
|-
| [[Meeting_Notes_2018-01-10|2018-01-10]]
| Jacques Noah
| melissa and sierk as new omni delegates;
|-
| [[Meeting_Notes_2017-12-13|2017-12-13]]
| * Adam Bredenberg Melissa Crow Pato Adam Eric Jan
| discussion of finances, omni cafe proposal discussion
|-
| [[Meeting_Notes_2017-11-29|2017-11-29]]
|
| Another irregular meeting, with two topics of interest.
|-
| [[Meeting_Notes_2017-11-08|2017-11-08]]
|
|
|-
| [[Meeting_Notes_2017-11-01|2017-11-01]]
|
| Not a usual meeting date, but notes were taken.
|-
| [[Meeting_Notes_2017-08-13|2017-08-13]]
|
|
|-
| [[Meeting_Notes_2017-08-09|2017-08-09]]
| Kyle Matt Rayc
|
|-
| [[Meeting_Notes_2017-07-12|2017-07-12]]
|
|
|-
| [[Meeting_Notes_2017-05-10|2017-05-10]]
| Corey Travis
|
|-
| [[Meeting_Notes_2017-04-12|2017-04-12]]
|
|
|-
| [[Meeting_Notes_2017-03-08|2017-03-08]]
|
|
|-
| [[Meeting_Notes_2017-02-08|2017-02-08]]
|
|
|-
| [[Meeting_Notes_2017-01-25|2017-01-25]]
|
|
|-
| [[Meeting_Notes_2017-01-11|2017-01-11]]
|
|
|-
| [[Meeting_Notes_2017-01-04|2017-01-04]]
|
|
|-
| [[Meeting_Notes_2016-12-14|2016-12-14]]
|
|
|-
| [[Meeting_Notes_2016-11-16|2016-11-16]]
|
|
|-
| [[Meeting_Notes_2016-11-09|2016-11-09]]
|
|
|-
| [[Meeting_Notes_2016-10-12|2016-10-12]]
| Vienna
|
|-
| [[Meeting_Notes_2016-09-14|2016-09-14]]
| T Maes Evan Short
|
|-
| [[Meeting_Notes_2016-08-17|2016-08-17]]
|
|
|-
| [[Meeting_Notes_2016-08-10|2016-08-10]]
|
|
|-
| [[Meeting_Notes_2016-07-20|2016-07-20]]
|
|
|-
| [[Meeting_Notes_2016-07-13|2016-07-13]]
|
|
|-
| [[Meeting_Notes_2016-06-15|2016-06-15]]
| Eric Wen-qing Alex Yvonne
|
|-
| [[Meeting_Notes_2016-06-08|2016-06-08]]
| Tim Chris Lindsey
|
|-
| [[Meeting_Notes_2016-05-11|2016-05-11]]
| James Corey Benjamin Huang
|
|-
| [[Meeting_Notes_2016-04-27|2016-04-27]]
| Elliot
|
|-
| [[Meeting_Notes_2016-04-20|2016-04-20]]
| Syd
|
|-
| [[Meeting_Notes_2016-04-13|2016-04-13]]
| Abhiram Pete Forsyth Dirty Bill Chris Jamie
|
|-
| [[Meeting_Notes_2016-04-06|2016-04-06]]
| Jacob Jason
|
|-
| 2016-03-30
|rowspan=6 colspan=2 align=center|We totally flaked for the entire month of March.
|-
| 2016-03-23
|-
| 2016-03-23
|-
| 2016-03-16
|-
| 2016-03-09
|-
| 2016-03-02
|-
| [[Meeting_Notes_2016-02-24|2016-02-24]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-17|2016-02-17]]
| bstack
|
|-
| [[Meeting_Notes_2016-02-10|2016-02-10]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-03|2016-02-03]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-27|2016-01-27]]
| Jay
|
|-
| [[Meeting_Notes_2016-01-20|2016-01-20]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-13|2016-01-13]]
|
| cancelled-ish
|-
| [[Meeting_Notes_2016-01-06|2016-01-06]]
| nathan Nick
|
|-
| [[Meeting_Notes_2015-12-30|2015-12-30]]
| Charley
|
|-
| 2015-12-23
|
| no signs of having happened
|-
| [[Meeting_Notes_2015-12-16|2015-12-16]]
| Daisy
|
|-
| [[Meeting_Notes_2015-12-09|2015-12-09]]
|
|
|-
| [[Meeting_Notes_2015-12-02|2015-12-02]]
| Max
|
|-
| [[Meeting_Notes_2015-11-25|2015-11-25]]
|
| didn't really happen, blame thanksgiving
|-
| [[Meeting_Notes_2015-11-18|2015-11-18]]
| morgan
|
|-
| [[Meeting_Notes_2015-11-11|2015-11-11]]
| Kwaku Gracie Micolah
|
|-
| [[Meeting_Notes_2015-11-04|2015-11-04]]
| dane
|
|-
| [[Meeting_Notes_2015-10-28|2015-10-28]]
| Andrew
|
|-
| [[Meeting Notes 2015-10-21|2015-10-21]]
| Merry
|
|-
| [[Meeting Notes 2015-10-14|2015-10-14]]
| Alex Lef Mari
|
|-
| [[Meeting Notes 2015-10-07|2015-10-07]]
| Tom Daron
|
|-
| [[Meeting Notes 2015-09-30|2015-09-30]]
|
| Insufficient critical mass
|-
| [[Meeting Notes 2015-09-23|2015-09-23]]
| Ari
|
|-
| [[Meeting Notes 2015-09-16|2015-09-16]]
| david
|
|-
| [[Meeting Notes 2015-09-09|2015-09-09]]
|
|
|-
| [[Meeting Notes 2015-09-02|2015-09-02]]
| Benji
|
|-
| [[Meeting Notes 2015-08-26|2015-08-26]]
|
|
|-
| 2015-08-19
|
| nobody showed up
|-
| [[Meeting Notes 2015-08-12|2015-08-12]]
|
|
|-
| [[Meeting Notes 2015-08-05|2015-08-05]]
|
|
|-
| [[Meeting Notes 2015-07-29|2015-07-29]]
|
|
|-
| [[Meeting_Notes_2015-07-22|2015-07-22]]
|
|
|-
| [[Meeting_Notes_2015-07-15|2015-07-15]]
|
|
|-
| [[Meeting_Notes_2015-07-08|2015-07-08]]
|
|
|-
| [[Meeting_Notes_2015-07-01|2015-07-01]]
|
|
|-
| [[Meeting_Notes_2015-06-24|2015-06-24]]
|
|
|-
| [[Meeting_Notes_2015-06-17|2015-06-17]]
|
|
|-
| [[Meeting_Notes_2015-06-10|2015-06-10]]
|
|
|-
| [[Meeting_Notes_2015-06-03|2015-06-03]]
|
|
|-
| [[Meeting_Notes_2015-05-27|2015-05-27]]
|
|
|-
| [[Meeting_Notes_2015-05-20|2015-05-20]]
|
|
|-
| [[Meeting_Notes_2015-05-13|2015-05-13]]
|
|
|-
| [[Meeting_Notes_2015-05-06|2015-05-06]]
|
|
|-
| [[Meeting_Notes_2015-04-29|2015-04-29]]
|
|
|-
| [[Meeting_Notes_2015-04-22|2015-04-22]]
|
|
|-
| [[Meeting_Notes_2015-04-15|2015-04-15]]
|
|
|-
| [[Meeting_Notes_2015-04-08|2015-04-08]]
|
|
|-
| [[Meeting_Notes_2015-04-01|2015-04-01]]
|
|
|-
| [[Meeting_Notes_2015-03-25|2015-03-25]]
|
|
|-
| [[Meeting_Notes_2015-03-18|2015-03-18]]
|
|
|-
| [[Meeting_Notes_2015-03-11|2015-03-11]]
|
|
|-
| [[Meeting_Notes_2015-03-04|2015-03-04]]
|
|
|-
| [[Meeting_Notes_2015-02-25|2015-02-25]]
|
|
|-
| [[Meeting_Notes_2015-02-18|2015-02-18]]
|
|
|-
| [[Meeting_Notes_2015-02-11|2015-02-11]]
|
|
|-
| [[Meeting_Notes_2015-02-04|2015-02-04]]
|
|
|-
| [[Meeting_Notes_2015-01-28|2015-01-28]]
|
|
|-
| [[Meeting_Notes_2015-01-21|2015-01-21]]
|
|
|-
| [[Meeting_Notes_2015-01-14|2015-01-14]]
|
|
|-
| [[Meeting_Notes_2015-01-07|2015-01-07]]
|
|
|-
| [[Meeting_Notes_2014-12-31|2014-12-31]]
|
|
|-
| [[Meeting_Notes_2014-12-24|2014-12-24]]
|
|
|-
| [[Meeting_Notes_2014-12-17|2014-12-17]]
|
|
|-
| [[Meeting_Notes_2014-12-10|2014-12-10]]
|
|
|-
| [[Meeting_Notes_2014-12-03|2014-12-03]]
|
|
|-
| [[Meeting_Notes_2014-11-26|2014-11-26]]
|
|
|-
| [[Meeting_Notes_2014-11-19|2014-11-19]]
|
|
|-
| [[Meeting_Notes_2014-11-12|2014-11-12]]
|
|
|-
| [[Meeting_Notes_2014-11-05|2014-11-05]]
|
|
|-
| [[Meeting_Notes_2014-10-29|2014-10-29]]
|
|
|-
| [[Meeting_Notes_2014-10-27|2014-10-27]]
|
| Board of Directors Meeting
|-
| [[Meeting_Notes_2014-10-22|2014-10-22]]
|
|
|-
| [[Meeting_Notes_2014-10-15|2014-10-15]]
|
|
|-
| [[Meeting_Notes_2014-10-08|2014-10-08]]
|
|
|-
| [[Meeting_Notes_2014-10-01|2014-10-01]]
|
|
|-
| [[Meeting_Notes_2014-09-24|2014-09-24]]
|
|
|-
| [[Meeting_Notes_2014-09-17|2014-09-17]]
|
|
|-
| [[Meeting_Notes_2014-09-10|2014-09-10]]
|
|
|-
| [[Meeting_Notes_2014-09-03|2014-09-03]]
|
|
|-
| [[Meeting_Notes_2014-08-27|2014-08-27]]
|
|
|-
| [[Meeting_Notes_2014-08-20|2014-08-20]]
|
|
|-
| [[Meeting_Notes_2014-08-13|2014-08-13]]
|
|
|-
| [[Meeting_Notes_2014-08-06|2014-08-06]]
|
|
|-
| [[Meeting_Notes_2014-07-30|2014-07-30]]
|
|
|-
| [[Meeting_Notes_2014-07-23|2014-07-23]]
|
|
|-
| [[Meeting_Notes_2014-07-16|2014-07-16]]
|
|
|-
| [[Meeting_Notes_2014-07-09|2014-07-09]]
|
|
|-
| [[Meeting_Notes_2014-07-02|2014-07-02]]
|
| First meeting in our new space @ 4799 Shattuck!
|-
| 2014-06-25
|
| big moving day, no meeting notes
|-
| [[Meeting_Notes_2014-06-18|2014-06-18]]
|
|
|-
| [[Meeting_Notes_2014-06-11|2014-06-11]]
|
|
|-
| [[Meeting_Notes_2014-06-04|2014-06-04]]
|
|
|-
| [[Meeting Notes 2014-05-28|2014-05-28]]
|
|
|-
| [[Meeting Notes 2014-05-21|2014-05-21]]
|
|
|-
| [[Meeting Notes 2014-05-14|2014-05-14]]
|
|
|-
| [[Meeting Notes 2014-05-07|2014-05-07]]
|
|
|-
| [[Meeting Notes 2014-04-30|2014-04-30]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-23|2014-04-23]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-16|2014-04-16]]
|
|
|-
| [[Meeting Notes 2014-04-09|2014-04-09]]
|
|
|-
| [[Meeting Notes 2014-04-02|2014-04-02]]
|
| mostly reboot
|-
| [[Meeting Notes 2014-03-26|2014-03-26]]
|
|
|-
| [[Meeting Notes 2014-03-19|2014-03-19]]
|
|
|-
| [[Meeting Notes 2014-03-12|2014-03-12]]
|
|
|-
| [[Meeting Notes 2014-03-05|2014-03-05]]
|
| Special edition on reboot
|-
| [[Meeting Notes 2014-02-26|2014-02-26]]
|
|
|-
| [[Meeting Notes 2014-02-19|2014-02-19]]
|
|
|-
| [[Meeting Notes 2014-02-12|2014-02-12]]
|
|
|-
| [[Meeting Notes 2014-02-05|2014-02-05]]
|
|
|-
| [[Meeting Notes 2014-01-29|2014-01-29]]
|
|
|-
| [[Meeting Notes 2014-01-22|2014-01-22]]
|
|
|-
| [[Meeting Notes 2014-01-15|2014-01-15]]
|
|
|-
| [[Meeting Notes 2014-01-08|2014-01-08]]
|
|
|-
| [[Meeting Notes 2014-01-01|2014-01-01]]
|
|
|-
| [[Meeting Notes 2013-12-25|2013-12-25]]
|
|
|-
| [[Meeting Notes 2013-12-18|2013-12-18]]
|
|
|-
| [[Meeting Notes 2013-12-11|2013-12-11]]
|
|
|-
| [[Meeting Notes 2013-12-04|2013-12-04]]
|
|
|-
| [[Meeting Notes 2013-11-27|2013-11-27]]
|
|
|-
| [[Meeting Notes 2013-11-20|2013-11-20]]
|
|
|-
| [[Meeting Notes 2013-11-13|2013-11-13]]
|
|
|-
| [[Meeting Notes 2013-11-06|2013-11-06]]
|
|
|-
| [[Meeting Notes 2013-10-30|2013-10-30]]
|
|
|-
| [[Meeting Notes 2013-10-23|2013-10-23]]
|
|
|-
| [[Meeting Notes 2013-10-16|2013-10-16]]
|
|
|-
| [[Meeting Notes 2013-10-02|2013-10-02]]
|
|
|-
| [[Meeting Notes 2013-09-25|2013-09-25]]
|
|
|-
| [[Meeting Notes 2013-09-18|2013-09-18]]
|
|
|-
| [[Meeting Notes 2013-09-11|2013-09-11]]
|
|
|-
| [[Meeting Notes 2013-09-04|2013-09-04]]
|
|
|-
| [[Meeting Notes 2013-08-28|2013-08-28]]
|
|
|-
| [[Meeting Notes 2013-08-21|2013-08-21]]
|
|
|-
| [[Meeting Notes 2013-08-14|2013-08-14]]
|
|
|-
| [[Meeting Notes 2013-08-07|2013-08-07]]
|
|
|-
| [[Meeting Notes 2013-07-30|2013-07-30]]
|
|
|-
| [[Meeting Notes 2013-07-24|2013-07-24]]
|
|
|-
| [[Meeting Notes 2013-07-17|2013-07-17]]
|
|
|-
| [[Meeting Notes 2013-07-10|2013-07-10]]
|
|
|-
| [[Meeting Notes 2013-07-03|2013-07-03]]
|
|
|-
| [[Meeting Notes 2013-06-26|2013-06-26]]
|
|
|-
| [[Meeting Notes 2013-06-19|2013-06-19]]
|
|
|-
| [[Meeting Notes 2013-06-12|2013-06-12]]
|
|
|-
| [[Meeting Notes 2013-06-05|2013-06-05]]
|
|
|-
| [[Meeting Notes 2013-05-29|2013-05-29]]
|
|
|-
| [[Meeting Notes 2013-05-22|2013-05-22]]
|
|
|-
| [[Meeting Notes 2013-05-15|2013-05-15]]
|
|
|-
| [[Meeting Notes 2013-05-08|2013-05-08]]
|
|
|-
| [[Meeting Notes 2013-05-01|2013-05-01]]
|
|
|-
| [[Meeting Notes 2013-04-24|2013-04-24]]
|
|
|-
| [[Meeting Notes 2013-04-17|2013-04-17]]
|
|
|-
| [[Meeting Notes 2013-04-11|2013-04-11]]
|
|
|-
| [[Meeting Notes 2013-04-03|2013-04-03]]
|
|
|-
| [[Meeting Notes 2013-03-27|2013-03-27]]
|
|
|-
| 2013-03-20
|
| no notes?
|-
| [[Meeting Notes 2013-03-13|2013-03-13]]
|
|
|-
| [[Meeting Notes 2013-03-06|2013-03-06]]
|
|
|-
| [[Meeting Notes 2013-02-27|2013-02-27]]
|
|
|-
| [[Meeting Notes 2013-02-20|2013-02-20]]
|
|
|-
| [[Meeting Notes 2013-02-13|2013-02-13]]
|
|
|-
| [[Meeting Notes 2013-02-06|2013-02-06]]
|
|
|-
| [[Meeting Notes 2013-01-30|2013-01-30]]
|
|
|-
| [[Meeting Notes 2013-01-23|2013-01-23]]
|
|
|-
| [[Meeting Notes 2013-01-16|2013-01-16]]
|
|
|-
| [[Meeting Notes 2013-01-09|2013-01-09]]
|
|
|-
| [[Meeting Notes 2013-01-02|2013-01-02]]
|
|
|-
| [[Sudo room/12-26-2012 Meetup|2012-12-26]]
|
|
|-
| [[Sudo room/12-19-2012 Meetup|2012-12-19]]
|
|
|-
| [[Sudo room/12-12-2012 Meetup|2012-12-12]]
|
|
|-
| [[Sudo room/12-05-2012 Meetup|2012-12-05]]
|
|
|-
| [[Sudo room/11-28-2012 Meetup|2012-11-28]]
|
|
|-
| [[Sudo room/11-21-2012 Meetup|2012-11-21]]
|
|
|-
| [[Sudo room/11-14-2012 Meetup|2012-11-14]]
|
|
|-
| [[Sudo room/11-7-2012 Meetup|2012-11-07]]
|
|
|-
| [[Sudo room/10-31-2012 Meetup|2012-10-31]]
|
|
|-
| [[Sudo room/10-24-2012 Meetup|2012-10-24]]
|
|
|-
| [[Sudo room/10-17-2012 Meetup|2012-10-17]]
|
|
|-
| [[Sudo room/10-10-2012 Meetup|2012-10-10]]
|
|
|-
| [[Sudo room/10-03-2012 Meetup|2012-10-03]]
|
|
|-
| [[Sudo room/09-26-2012 Meetup|2012-09-26]]
|
|
|-
| [[Sudo room/09-19-2012 Meetup|2012-09-19]]
|
|
|-
| [[Sudo room/09-12-2012 Meetup|2012-09-12]]
|
|
|-
| [[Sudo room/09-05-2012 Meetup|2012-09-05]]
|
|
|-
| [[Sudo room/08-29-2012 Meetup|2012-08-29]]
|
|
|-
| [[Sudo room/08-22-2012 Meetup|2012-08-22]]
|
|
|-
| [[Sudo room/08-13-2012 Meetup|2012-08-13]]
|
|
|-
| [[Sudo room/08-08-2012 Meetup|2012-08-08]]
|
|
|-
| [[Sudo room/08-01-2012 Meetup|2012-08-01]]
|
|
|-
| [[Sudo room/07-25-2012 Meetup|2012-07-25]]
|
|
|-
| [[Sudo room/07-18-2012 Meetup|2012-07-18]]
|
|
|-
| [[Sudo room/07-11-2012 Meetup|2012-07-11]]
|
|
|-
| [[Sudo room/07-04-2012 Meetup|2012-07-04]]
|
|
|-
| [[Sudo room/06-27-2012 Meetup|2012-06-27]]
|
|
|-
| [[Sudo room/06-20-2012 Meetup|2012-06-20]]
|
|
|-
| [[Sudo room/06-13-2012 Meetup|2012-06-13]]
|
|
|-
| [[Sudo room/06-06-2012 Meetup|2012-06-06]]
|
|
|-
| [[Sudo room/05-30-2012 Meetup|2012-05-30]]
|
|
|-
| [[Sudo room/05-23-2012 Meetup|2012-05-23]]
|
|
|-
| [[Sudo room/05-16-2012 Meetup|2012-05-16]]
|
|
|-
| 2012-05-09
|
| no notes?
|-
| 2012-05-02
|
| no notes?
|-
| [[Sudo room/04-25-2012 Meetup|2012-04-25]]
|
|
|-
| 2012-04-18
|
| no notes?
|-
| 2012-04-11
|
| no notes?
|-
| 2012-04-04
|
| no notes?
|-
| 2012-03-28
|
| no notes?
|-
| 2012-03-21
|
| no notes?
|-
| 2012-03-14
|
| no notes?
|-
| 2012-03-07
|
| no notes?
|-
| 2012-02-29
|
| no notes?
|-
| [[Sudo room/02-22-2012 Meetup|2012-02-22]]
|
|
|-
| 2012-02-15
|
| no notes?
|-
| 2012-02-08
|
| no notes?
|-
| [[Sudo room/02-01-2011 Meetup|2012-02-01]]
|
|
|-
| [[Sudo room/01-25-2011 Meetup|2012-01-25]]
|
|
|-
| [[Sudo room/01-18-2011 Meetup|2012-01-18]]
|
|
|-
| [[Sudo room/01-11-2011 Meetup|2012-01-11]]
|
|
|-
| [[Sudo room/01-04-2011 Meetup|2012-01-04]]
|
|
|-
| [[Sudo room/12-28-2011 Meetup|2011-12-28]]
|
|
|-
| [[Sudo room/12-21-2011 Meetup|2011-12-21]]
|
|
|-
| [[Sudo room/12-14-2011 Meetup|2011-12-14]]
|
|
|-
| [[Sudo room/12-07-2011 Meetup|2011-12-07]]
|
|
|-
| [[Sudo room/First Wed Meetup|2011-11-30]]
|
| @ Cafe Mediterraneum
|-
| [[Sudo room/Initial Meeting| Initial Meeting]]
|
| 2011-11-18, 12pm @ Actual Cafe
|}

[[Category:SudoRoom Organization]][[Category:Meetings]]

ModularSynthesizer

2026-08-29T18:00:37Z

Indoorjetpacks: Added that we are intentionally not putting a picture, in case someone misses it in the deletion log, with a bit of humor and encouragement to come visit.

[[File:Analog Synthesizer at SudoRoom.jpg|frameless|right]]
We have an analog modular synthesizer at Sudo Room. We would show a picture, but one of the stipulations of us having it is "no pictures online" - it's better experienced in person anyway!

See also: [[Synthesis]], which records sessions on this modular synth!

== How to use it ==
# Zero out (move to the bottom) all volume sliders
# Turn on the power strip under the synth table
# Plug and play

''We are working on building quick start and "how to" guides that include videos and cartoons on using the synthesizer.'' 

=== Manual ===
There is a printed manual of the synthesizer.

[[File:Synthezier Manual.jpg|frameless|left|upright=1]]

[[Category:Music]]
[[Category:MusicalInstruments]]

Hack Cowork Nite

2026-07-26T20:56:36Z

Indoorjetpacks:

__NOTOC__
'''Every first and third Thursday'''
'''19:00 (7 PM) — 21:00 (9 PM)'''

== Overview ==
Every first and third Thursday, we meet up to do some additional co-hacking, similar to Tuesday's [[HardwareHackNight]]! Bring a project, work on it, we'll try to keep the area with enough space to work, albeit some [[hacker dust]]!

Current hosts are: [[User: Indoorjetpacks]] and [[User: Julios]]

5th Thursdays happen on a "TBD, ping one of the hosts sometime the week before/week of" basis.

Luma: TBD

Hack Cowork Nite

2026-07-26T20:53:26Z

Indoorjetpacks: clarifying first and third thursdays bc sometimes there's a fifth and that would wonk things w other thursday events

Membermatters

2026-06-05T03:05:19Z

Indoorjetpacks: /* TODO */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* RechnerFox setup a staging instance for us!
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-06-04 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps

Ivan signed up, paid, and got to the post-signup page

Julio signed up, paid, and go to the post-signup page

= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== Membermatters-related workflow ===
# User submits Intent to join form
# User creates an account / signs up on member matters. They land on a 'Contact Us' page for next steps - Membership Status: noob. Subscription Status: inactive
# User adds payment info to member matters and selects a payment plan - Membership Status: noob. Subscription Status: active
# User gets 3 endorsements achieved. Membership Status: noob. Subscription Status: active
# Current members have next member meeting, check for new forms, review Taiga. For any members that meet all reqs, add them to members mailing list, reply to their request form email, move them in Taiga as needed, and on MM, change user's Membership Status. Membership Status: active. Subscription Status: active
# User is a member!

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers - done? we only have one
# Set up payment plans - also done, mirroring the ones on sudohumans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?
# '' UX: The ending page takes someone to Contact Us page, kinda unclear what the actual steps are
# '' UX: Welcome email sent from MM says "here are some next steps" but it's empty, ha.
# '' see also maybe [https://github.com/sudoroom/MemberMatters/issues the github issues page]

Membermatters

2026-06-05T03:03:45Z

Indoorjetpacks: /* TODO */

Membermatters

2026-06-05T02:59:30Z

Indoorjetpacks: /* Membermatters-related workflow */

Membermatters

2026-06-05T02:39:36Z

Indoorjetpacks: /* MEMBERSHIP PROCESS- DISCUSSION */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* RechnerFox setup a staging instance for us!
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-06-04 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps

Ivan signed up, paid, and got to the post-signup page

Julio signed up, paid, and go to the post-signup page

= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== Membermatters-related workflow ===
# User submits Intent to join form
# User creates an account / signs up on member matters. They land on a 'Contact Us' page for next steps - Membership Status: noob. Subscription Status: inactive
# User adds payment info to member matters and selects a payment plan - Membership Status: noob. Subscription Status: active
# User gets 3 endorsements achieved. Membership Status: noob. Subscription Status: active
# Current members have next member meeting, review Taiga and email list. For any members that meet all reqs, on MM, change user's Membership Status. Membership Status: active. Subscription Status: active
# User is a member!

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers - done? we only have one
# Set up payment plans - also done, mirroring the ones on sudohumans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?

Membermatters

2026-06-05T02:14:54Z

Indoorjetpacks: /* github */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* RechnerFox setup a staging instance for us!
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-06-04 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps

Ivan signed up, paid, and got to the post-signup page

Julio signed up, paid, and go to the post-signup page

= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers - done? we only have one
# Set up payment plans - also done, mirroring the ones on sudohumans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?

Membermatters

2026-06-05T02:12:58Z

Indoorjetpacks: /* Currently ( 2026-06-04 ) */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-06-04 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps

Ivan signed up, paid, and got to the post-signup page

Julio signed up, paid, and go to the post-signup page

= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers - done? we only have one
# Set up payment plans - also done, mirroring the ones on sudohumans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?

Membermatters

2026-06-05T02:12:11Z

Indoorjetpacks: /* Currently ( 2026-02-07 ) */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-06-04 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
Ivan signed up, paid, and got to the post-signup page
Julio signed up, paid, and go to the post-signup page

= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers - done? we only have one
# Set up payment plans - also done, mirroring the ones on sudohumans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?

Hack Cowork Nite

2026-05-31T21:20:42Z

Indoorjetpacks: Created page with "__NOTOC__ '''Every other Thursday''' '''21:00 (7 PM) — 23:00 (9 PM)''' == Overview == Every other Thursday, we meet up to do some additional co-hacking, similar to Tuesday's HardwareHackNight! Bring a project, work on it, we'll try to keep the area with enough space to work, albeit some hacker dust!"

__NOTOC__
'''Every other Thursday'''
'''21:00 (7 PM) — 23:00 (9 PM)'''

== Overview ==
Every other Thursday, we meet up to do some additional co-hacking, similar to Tuesday's [[HardwareHackNight]]! Bring a project, work on it, we'll try to keep the area with enough space to work, albeit some [[hacker dust]]!

Recurring Meetings

2026-05-31T21:10:28Z

Indoorjetpacks: /* Once or Twice a Month */

:''For the most recently-updated list of upcoming events, see: [https://sudoroom.org/calendar/ Sudo Room Calendar] and [https://omnicommons.org/calendar/ Omni Commons Global Calendar]''

== Weekly Events ==

{| class="wikitable"
| '''[[WomenNonBinaryCoding|Women / NonBinary Coding nights]]'''
'''Mondays''' (7pm - 9pm or even later)
|
The Sudo Room, a creative community and hackerspace at Omni Commons, invites all Women/NB people for “Coding Owls – A WNB Coding Night”: bring your computer and a coding project and have fun! We can help each other if you have coding related questions/bugs or just keep company while hacking!
and if you can't make it there physically, we have an [https://meet.waag.org/turtlesturtlesturtles ONLINE JITSI PORTAL]
|-
| '''[[HardwareHackNight | Hardware and SoftWEAR Project Night]] & [[FixitClinic | Fixit Clinic]]'''
'''Tuesdays''' (8pm - 11pm or even later)
| <noinclude>[[image:SudoRoom_hardware_hacknight.jpg|thumb|120px|A large animal will lead you through real life stuff, you digital wimps ;)]]</noinclude>
Tinker and toil, fiddle and play, hack away at hardware and electronics, affect flair or repairs on textiles and fabric. The Hardware and SoftWEAR Project Night runs alongside the Fixit Clinic, come join a plethora of creative, kind, smart, and knowledgeable nerds as we fix and make things!

If you can't make it physically, you can join us virtually in our [https://meet.waag.org/turtlesturtlesturtles online Jitsi video conference]
|-
| '''[[Radio_Wednesdays|Radio Wednesdays]]'''
'''Wednesdays''' (7pm - 9pm)
|
Wednesdays are for p2p decentralized communications for emergency preparedness and anti-surveillance! We talk ham and Meshtastic and other protocols. See also: https://leftyrad.io & https://bayme.sh
|}

== Once or Twice a Month ==

{| class="wikitable"
|-
| '''''<ON HIATUS>'' [[Darkmode]]'''
'''Last Sunday of each month''' (6pm - 8pm)
|
Enter the world of audio visuals, light projections and TouchDesigner workshops.
|-
| '''[[Hack Cowork Nite]] (formerly [[Smorgasbord]] )'''
'''1st and 3rd Thursdays''' (7pm - 9pm)
|
Every other Thursday, we meet up to do some co-hacking! Bring a project, work on it, we'll try to keep the area with enough space to work, albeit some [[hacker dust]]!

Software, Hardware, LLM hacking (see [[CommunityInfra]]), wiki editing (for any and all wiki!), and stitch 'n bitch (fabric arts and chat).
|-
| '''[[Meetings]]'''
'''2nd Thursday''' (7pm) '''and last Sunday''' (4pm)
|
Sudo Room's official meetings are twice a month (second Thursday at 7pm, and last Sunday at 4pm). We meet in a hybrid format, in-person at Sudo Room and remote using our [https://meet.waag.org/turtlesturtlesturtles online Jitsi video conference]

We keep our agenda on an [https://pad.riseup.net/ etherpad] and then [[Meetings#Meeting_Notes_Archive|archive the meeting minutes]]. We're a California non-profit. See our [[Articles of Association]].
|-
| '''[[SudoParty]]'''
'''4th Thursdays''' (7pm - midnight)
|
$ sudo party --hard
|}

Recurring Meetings

2026-05-31T21:09:29Z

Indoorjetpacks: /* Once or Twice a Month */

:''For the most recently-updated list of upcoming events, see: [https://sudoroom.org/calendar/ Sudo Room Calendar] and [https://omnicommons.org/calendar/ Omni Commons Global Calendar]''

== Weekly Events ==

{| class="wikitable"
| '''[[WomenNonBinaryCoding|Women / NonBinary Coding nights]]'''
'''Mondays''' (7pm - 9pm or even later)
|
The Sudo Room, a creative community and hackerspace at Omni Commons, invites all Women/NB people for “Coding Owls – A WNB Coding Night”: bring your computer and a coding project and have fun! We can help each other if you have coding related questions/bugs or just keep company while hacking!
and if you can't make it there physically, we have an [https://meet.waag.org/turtlesturtlesturtles ONLINE JITSI PORTAL]
|-
| '''[[HardwareHackNight | Hardware and SoftWEAR Project Night]] & [[FixitClinic | Fixit Clinic]]'''
'''Tuesdays''' (8pm - 11pm or even later)
| <noinclude>[[image:SudoRoom_hardware_hacknight.jpg|thumb|120px|A large animal will lead you through real life stuff, you digital wimps ;)]]</noinclude>
Tinker and toil, fiddle and play, hack away at hardware and electronics, affect flair or repairs on textiles and fabric. The Hardware and SoftWEAR Project Night runs alongside the Fixit Clinic, come join a plethora of creative, kind, smart, and knowledgeable nerds as we fix and make things!

If you can't make it physically, you can join us virtually in our [https://meet.waag.org/turtlesturtlesturtles online Jitsi video conference]
|-
| '''[[Radio_Wednesdays|Radio Wednesdays]]'''
'''Wednesdays''' (7pm - 9pm)
|
Wednesdays are for p2p decentralized communications for emergency preparedness and anti-surveillance! We talk ham and Meshtastic and other protocols. See also: https://leftyrad.io & https://bayme.sh
|}

== Once or Twice a Month ==

{| class="wikitable"
|-
| '''''<ON HIATUS>'' [[Darkmode]]'''
'''Last Sunday of each month''' (6pm - 8pm)
|
Enter the world of audio visuals, light projections and TouchDesigner workshops.
|-
| '''[[Hack Cowork Nite]] (formerly [[Smorgasbord]] )'''
'''1st and 3rd Thursdays''' (7pm - 9pm)
|
Every other Thursday, we meet up to do some co-hacking! Bring a project, work on it, we'll try to keep the area mostly free of [[hacker dust]], but no guarantees!

Software, Hardware, LLM hacking (see [[CommunityInfra]]), wiki editing (for any and all wiki!), and stitch 'n bitch (fabric arts and chat).
|-
| '''[[Meetings]]'''
'''2nd Thursday''' (7pm) '''and last Sunday''' (4pm)
|
Sudo Room's official meetings are twice a month (second Thursday at 7pm, and last Sunday at 4pm). We meet in a hybrid format, in-person at Sudo Room and remote using our [https://meet.waag.org/turtlesturtlesturtles online Jitsi video conference]

We keep our agenda on an [https://pad.riseup.net/ etherpad] and then [[Meetings#Meeting_Notes_Archive|archive the meeting minutes]]. We're a California non-profit. See our [[Articles of Association]].
|-
| '''[[SudoParty]]'''
'''4th Thursdays''' (7pm - midnight)
|
$ sudo party --hard
|}

Breaker

2026-03-26T04:40:25Z

Indoorjetpacks:

How to reset the breaker for the big red laser cutter, and hardware corner, and the rest of the south outlets. Flashlight recommended!!

The breaker is up the stairs:
[[File:Go upstairs.jpg|thumb|The breaker is up the stairs]]

Through the left door:
[[File:Through left door.jpg|thumb|Through the left door]]

Go to the left, to the top of the stage:
[[File:Top of the stage.jpg|thumb|turn left and go to the top of the stage]]

climb the ladder:
[[File:Ladder_top_of_stage.jpg|thumb|climb the ladder]]

and look for the breaker panel:
[[File:Breaker box exterior.jpg|thumb|look for the breaker panel]]

The circuits should be labeled:
[[File:Breaker panel labels.jpg|thumb|Circuits should be labeled]]

And those correspond to the actual breakers.
[[File:Panel actual breakers.jpg|thumb|The actual breakers the labels correspond to]]

Alternately you can look at the panel to see which is flipped (look for what is out of place vs the others). Flip it back toward the other direction (sometimes it will require some force) and you should be good!

Breaker

2026-03-26T04:40:07Z

Indoorjetpacks:

How to reset the breaker for the big red laser cutter, and hardware corner, and the rest of the south outlets. Flashlight recommended!!

The breaker is up the stairs:
[[File:Go upstairs.jpg|thumbThe breaker is up the stairs]]

Through the left door:
[[File:Through left door.jpg|thumb|Through the left door]]

Go to the left, to the top of the stage:
[[File:Top of the stage.jpg|thumb|turn left and go to the top of the stage]]

climb the ladder:
[[File:Ladder_top_of_stage.jpg|thumb|climb the ladder]]

and look for the breaker panel:
[[File:Breaker box exterior.jpg|thumb|look for the breaker panel]]

The circuits should be labeled:
[[File:Breaker panel labels.jpg|thumb|Circuits should be labeled]]

And those correspond to the actual breakers.
[[File:Panel actual breakers.jpg|thumb|The actual breakers the labels correspond to]]

Alternately you can look at the panel to see which is flipped (look for what is out of place vs the others). Flip it back toward the other direction (sometimes it will require some force) and you should be good!

File:Panel actual breakers.jpg

2026-03-26T04:37:27Z

Indoorjetpacks: Indoorjetpacks uploaded a new version of File:Panel actual breakers.jpg

picture of thee inside of a breaker panel

File:Breaker panel labels.jpg

2026-03-26T04:35:20Z

Indoorjetpacks: Indoorjetpacks uploaded a new version of File:Breaker panel labels.jpg

inside of a breaker panel with labels on it

File:Breaker panel labels.jpg

2026-03-26T04:16:17Z

Indoorjetpacks: Indoorjetpacks reverted File:Breaker panel labels.jpg to an old version

inside of a breaker panel with labels on it

File:Breaker panel labels.jpg

2026-03-26T04:15:53Z

Indoorjetpacks: Indoorjetpacks uploaded a new version of File:Breaker panel labels.jpg

inside of a breaker panel with labels on it

File:Breaker panel labels.jpg

2026-03-26T04:07:36Z

Indoorjetpacks: Indoorjetpacks uploaded a new version of File:Breaker panel labels.jpg

inside of a breaker panel with labels on it

File:Breaker panel labels.jpg

2026-03-26T04:01:47Z

Indoorjetpacks: Indoorjetpacks uploaded a new version of File:Breaker panel labels.jpg

inside of a breaker panel with labels on it

File:Breaker panel labels.jpg

2026-03-26T03:49:04Z

Indoorjetpacks: Indoorjetpacks uploaded a new version of File:Breaker panel labels.jpg

inside of a breaker panel with labels on it

Breaker

2026-03-26T03:37:36Z

Indoorjetpacks:

How to reset the breaker for the big red laser cutter, and hardware corner, and the rest of the south outlets

The breaker is up the stairs:
[[File:Go upstairs.jpg|thumb]]

Through the left door:
[[File:Through left door.jpg|thumb]]

Go to the left, to the top of the stage:
[[File:Top of the stage.jpg|thumb]]

climb the ladder:
[[File:Ladder_top_of_stage.jpg|thumb]]

and look for the breaker panel:
[[File:Breaker box exterior.jpg|thumb]]

The circuits should be labeled:
[[File:Breaker panel labels.jpg|thumb]]

And those correspond to the actual breakers.
[[File:Panel actual breakers.jpg|thumb]]

Alternately you can look at the panel to see which is flipped (look for what is out of place vs the others). Flip it back toward the other direction (sometimes it will require some force) and you should be good!

Breaker

2026-03-26T03:37:12Z

Indoorjetpacks: resetting the breaker

# How to reset the breaker for the big red laser cutter, and hardware corner, and the rest of the south outlets

The breaker is up the stairs:
[[File:Go upstairs.jpg|thumb]]

Through the left door:
[[File:Through left door.jpg|thumb]]

Go to the left, to the top of the stage:
[[File:Top of the stage.jpg|thumb]]

climb the ladder:
[[File:Ladder_top_of_stage.jpg]]

and look for the breaker panel:
[[File:Breaker box exterior.jpg|thumb]]

The circuits should be labeled:
[[File:Breaker panel labels.jpg|thumb]]

And those correspond to the actual breakers.
[[File:Panel actual breakers.jpg|thumb]]

Alternately you can look at the panel to see which is flipped (look for what is out of place vs the others). Flip it back toward the other direction (sometimes it will require some force) and you should be good!

File:Breaker panel labels.jpg

2026-03-26T03:35:36Z

Indoorjetpacks:

inside of a breaker panel with labels on it

File:Panel actual breakers.jpg

2026-03-26T03:34:13Z

Indoorjetpacks:

picture of thee inside of a breaker panel

File:Breaker box exterior.jpg

2026-03-26T03:24:37Z

Indoorjetpacks:

exterior view of breaker box

File:Ladder top of stage.jpg

2026-03-26T03:22:38Z

Indoorjetpacks:

image of the ladder at the top of the stage

File:Top of the stage.jpg

2026-03-26T03:21:29Z

Indoorjetpacks:

top of the stage

File:Through left door.jpg

2026-03-26T03:20:20Z

Indoorjetpacks:

door on the left

File:Go upstairs.jpg

2026-03-26T03:19:25Z

Indoorjetpacks:

image of the stairs in sudoroom

Big red laser cutter

2026-03-26T03:14:45Z

Indoorjetpacks: /* General Info */

== General Info ==

The big red laser cutter is a no-name model using a Ruida 644XG control board. Its bed dimensions are about 730mm wide by 500mm deep. It looks like a 100 W CO2 laser.

The Melbourne Makerspace has the same laser and have a [https://wiki.melbournemakerspace.org/Laser%20Cutter nicely written wiki page on it].

[[File:Caution-danger-sign.jpg|thumb]]
''Be aware:'' lasers are very dangerous! Review these [https://ehs.mit.edu/workplace-safety-program/laser-cutter-safety/ safety guidelines], and carry an appropriate level of fear of the laser at all times. Hazards include:

'''Fire hazard'''

Lasers create high heat, and can cause materials to catch on fire. Certain materials and types of designs (i.e very dense/small objects) are more prone to fire.

To minimize fire risk, remember to...
# Never leave laser unattended. Be prepared to respond promptly in case of fire. Familiarize yourself with where the fire extinguisher and water spray bottle are before using. You should never see a prolonged flame while using the laser cutter.
# If you see a candle sized flame for more than 3 seconds while cutting, stop the laser, check/adjust bed height, power/speed settings, or use a different material.

'''Respiratory Hazard'''

Laser cutters create fumes and small particulates.

To minimize respiratory hazards, remember to...
# Only cut and engrave [[LASER SAFE material]]. Some materials can emit toxic fumes when laser cut, and should never be used in the laser cutter!
# Always have the ventilation fan on while using the laser cutter, and for a few minutes after you are done. Even laser safe materials aren't good to breathe in. There is also an air purifier next to the laser cutter that is nice to have on.
# Check in with other people in the room before using the laser cutter to see if they are sensitive to fumes. Be accommodating!

'''Laser Hazard'''

To minimize laser exposure hazards, remember to..
# Never look directly at the laser beam. While wearing eye protection, you may look at the point that the laser is cutting your material. However, you should NEVER look directly into a laser beam, even if wearing safety goggles.
# Never run the laser cutter while the lid is open.

'''Help I tripped the breaker'''

This is how to reset the [[breaker]] that the laser (and sewing/3dprinting/hardware corner) is on

== Operation Instructions ==
# First turn on the laser cutter control switch, located on the right side of the machine.
[[File:Laser_control_switch.jpg|showing laser control switch on|thumb]]

=== Preparing Material ===
# Put [[LASER SAFE material]] on the bed
# Use the control pad arrow keys to move the laser head above your material. We want it above the material to properly set the bed height
# Once laser head above material, use the knob inside the laser cutter to move the bed up and down. The correct height is about 3/4" above your material. You can use the "laser focus height" tool as reference.

[[File:Laser_bed_z_adjust.jpg|showing where Z adjust height is for laser|frameless]]

[[File:Laser_bed_correct_bed_height.jpg|showing correct bed height for laser|frameless]]

[[File:Laser_bed_correct_bed_height_with_tool.jpg|showing correct bed height for laser with tool|frameless]]

=== Turning on the laser and exhaust ===
# Turn on the exhaust fan by switching on the power strip on top of the laser cutter. You should hear the exhaust fan turn on. Also, switch on the air purifier on the desk.
[[File:Laser_exhaust_fan.jpg|exhaust fan for laser cutter|thumb]]

[[File:Laser_air_purifier.jpg|air purifier near the laser cutter|thumb]]

# Enable the laser by turning on the laser switch on the left side of the machine, and turning the key on the front of the machine.
[[File:Laser_switch.jpg|showing laser switch on|thumb]]

[[File:Laser_key_switch.jpg|showing laser key switch on|thumb]]

=== Preparing the file ===
The following steps should be done on the computer near the laser cutter, which has LightBurn installed on it.

# Open LightBurn on computer next to the laser cutter
# Import a vector file (dxf, pdf, etc) or image (rastering), or use LightBurn to create a design.
# Set the color of items to define how you want them cut or engraved, then double click the colors in the pane on the right to set the laser speed, power, and other features associated with that color. Black can be used to cut and red to etch, for instance. Use this chart to get a ballpark reference for speed and power settings: [[Big red laser cutter settings]]. It is recommended to do a "test cut" before cutting out a large file to be sure your speed and power settings are good.

[[File:Lightburn layer tips.png|frameless|LightBurn layer settings]]

# Select "absolute coordinates" to define the placement relative to the bed. Select "user origin" to set the placement on the bed manually. The device should be set to ttyUSB0, Ruida664GX.
# Once happy with design, click “Send”
# Enter a name (or just use default to override) and press enter.
# Wait for the file to send.

=== Running the laser ===
The following steps should be done using the control panel on the laser cutter itself.

# On the laser cutter control panel, press "File" to see available files.
# Scroll and press “Enter” to select a file.
# Set the origin if necessary.
# Press “Frame" to confirm placement. When you press this, the laser cutter head will trace around the max coordinates, to show you where your design will be cut.
# If the frame is correct press “Start”, and the laser will run.

=== Having Trouble Setting the Origin? ===
If you are using LightBurn to compose your project, be sure to use the setting "Current Position". 
Otherwise, LightBurn may override any origin you set at the laser cutter.

Setting the origin on the laser cutter is easy. 
On the front panel there are 4 arrow keys. You can use these to move the "head" around.
Pressing the "Origin" button sets that spot to be the origin of where cutting starts. Typically, this is the upper left
of the bounding rectangle around your artwork.
You may find that moving the "head" is much easier than moving the material placed on the bed!

== Other software ==

As mentioned, RDWorks can also be used. We haven't tried it yet but it seems it's a free download [https://www.thunderlaser.com/laser-download from here].

Some of the software (downloaded from the above link) is on the hard drive of wasp.local which is a desktop computer under the 3D printer desk, in a folder called ~/laser-backup/

[https://spaz.org/~jake/sudoroom/Big_red_laser_cutter/ The above software has also been downloaded and stored here]

it was setup with an IP address of 100.64.64.69 (by pressing buttons through the menu) but it had no ports open and then we just switched over to USB to the computer and it was working fine. The same software might work over ethernet but we didn't try.

== Trying other things ==
Andy is trying to find software to control the laser cutter. I can generate gcode instructions in Inkscape, but I don't know how to send them to the printer over USB.

I'm trying to install [https://laserweb.yurl.ch/|LaserWeb].

I ran the commands here : https://laserweb.yurl.ch/documentation/installation/36-install-raspberry-pi. But the server gave an error when started:

Server binding to all local IP addresses on port: 8000
internal/modules/cjs/loader.js:818
throw err;
^

Error: Cannot find module 'node-hid'
Require stack:
- /home/laser/Programs/lw.comm-server/server.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.exports.LWCommServer (/home/laser/Programs/lw.comm-server/server.js:168:13)
at Object.<anonymous> (/home/laser/Programs/lw.comm-server/server.js:4141:13)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/home/laser/Programs/lw.comm-server/server.js' ]
}

== Stuff made on the big red laser cutter ==

* I cut some 1/4 clear plastic suspected to be acrylic. Used .5mm/sec 100%/40% power. It cut all the way through but the edge was rough.

== Stuff seen around the space ==

== ventilation ducting ==

=== Cleaning ===

Clean the lens monthly

If the exhaust fan is not working well, it might need to be cleaned.

To clean, detach the fan and base from the laser cutter. The area circled in the below picture is where you need to get access.

[[File:Laser_fan_detach.jpg|showing where to detach laser exhaust fan|frameless]]

This is what the fan looks like detached

[[File:Laser_fan_detached.png|detached laser exhaust fan|frameless]]

This is dirty and needs to be cleaned

[[File:Laser_fan_dirty.jpg|dirty laser exhaust fan|frameless]]

Use a vacuum and toothbrush/wire brush to clean. A n95 mask is recommended too.

[[File:Laser_fan_clean.jpg|clean laser exhaust fan|frameless]]

=== history ===
a plastic adaptor was 3D printed to connect the 6" outlet of the exhaust fan to the 8" flexible duct leading to the roof hole:
<code>laserduct.scad
THICKNESS=1.5*25.4;
ID=5.75*25.4;
ID_LIP=ID-(0.25*25.4);
ID_LIP_THICK=0.2*25.4;
OD=7.75*25.4;
OD_LIP=OD+0.2*25.4;
OD_LIP_THICK=0.2*25.4;
difference() {
color("BLUE") cylinder(d1=OD_LIP, d2=OD, h=THICKNESS, $fn=100);
{
translate([0,0,ID_LIP_THICK]) cylinder(d=ID, h=THICKNESS, $fn=100);
translate([0,0,-0.5]) cylinder(d=ID_LIP, h=THICKNESS, $fn=100);
}
}</code>
[[File:Laserduct.png|3D printing exhaust duct adaptor|thumb]]

 
Also the duct/roof interface was improved and a new stand was made for the extractor fan. Yay for milkcrates! 

[[File:Fan-holder.jpg|thumb]]
[[File:new-vent-top.jpg|thumb]]

Big red laser cutter

2026-03-26T03:14:04Z

Indoorjetpacks: /* General Info */

== General Info ==

The big red laser cutter is a no-name model using a Ruida 644XG control board. Its bed dimensions are about 730mm wide by 500mm deep. It looks like a 100 W CO2 laser.

The Melbourne Makerspace has the same laser and have a [https://wiki.melbournemakerspace.org/Laser%20Cutter nicely written wiki page on it].

[[File:Caution-danger-sign.jpg|thumb]]
''Be aware:'' lasers are very dangerous! Review these [https://ehs.mit.edu/workplace-safety-program/laser-cutter-safety/ safety guidelines], and carry an appropriate level of fear of the laser at all times. Hazards include:

'''Fire hazard'''

Lasers create high heat, and can cause materials to catch on fire. Certain materials and types of designs (i.e very dense/small objects) are more prone to fire.

To minimize fire risk, remember to...
# Never leave laser unattended. Be prepared to respond promptly in case of fire. Familiarize yourself with where the fire extinguisher and water spray bottle are before using. You should never see a prolonged flame while using the laser cutter.
# If you see a candle sized flame for more than 3 seconds while cutting, stop the laser, check/adjust bed height, power/speed settings, or use a different material.

'''Respiratory Hazard'''

Laser cutters create fumes and small particulates.

To minimize respiratory hazards, remember to...
# Only cut and engrave [[LASER SAFE material]]. Some materials can emit toxic fumes when laser cut, and should never be used in the laser cutter!
# Always have the ventilation fan on while using the laser cutter, and for a few minutes after you are done. Even laser safe materials aren't good to breathe in. There is also an air purifier next to the laser cutter that is nice to have on.
# Check in with other people in the room before using the laser cutter to see if they are sensitive to fumes. Be accommodating!

'''Laser Hazard'''

To minimize laser exposure hazards, remember to..
# Never look directly at the laser beam. While wearing eye protection, you may look at the point that the laser is cutting your material. However, you should NEVER look directly into a laser beam, even if wearing safety goggles.
# Never run the laser cutter while the lid is open.

'''Help I tripped the breaker''
This is how to reset the [[breaker]] that the laser (and sewing/3dprinting/hardware corner) is on

== Operation Instructions ==
# First turn on the laser cutter control switch, located on the right side of the machine.
[[File:Laser_control_switch.jpg|showing laser control switch on|thumb]]

=== Preparing Material ===
# Put [[LASER SAFE material]] on the bed
# Use the control pad arrow keys to move the laser head above your material. We want it above the material to properly set the bed height
# Once laser head above material, use the knob inside the laser cutter to move the bed up and down. The correct height is about 3/4" above your material. You can use the "laser focus height" tool as reference.

[[File:Laser_bed_z_adjust.jpg|showing where Z adjust height is for laser|frameless]]

[[File:Laser_bed_correct_bed_height.jpg|showing correct bed height for laser|frameless]]

[[File:Laser_bed_correct_bed_height_with_tool.jpg|showing correct bed height for laser with tool|frameless]]

=== Turning on the laser and exhaust ===
# Turn on the exhaust fan by switching on the power strip on top of the laser cutter. You should hear the exhaust fan turn on. Also, switch on the air purifier on the desk.
[[File:Laser_exhaust_fan.jpg|exhaust fan for laser cutter|thumb]]

[[File:Laser_air_purifier.jpg|air purifier near the laser cutter|thumb]]

# Enable the laser by turning on the laser switch on the left side of the machine, and turning the key on the front of the machine.
[[File:Laser_switch.jpg|showing laser switch on|thumb]]

[[File:Laser_key_switch.jpg|showing laser key switch on|thumb]]

=== Preparing the file ===
The following steps should be done on the computer near the laser cutter, which has LightBurn installed on it.

# Open LightBurn on computer next to the laser cutter
# Import a vector file (dxf, pdf, etc) or image (rastering), or use LightBurn to create a design.
# Set the color of items to define how you want them cut or engraved, then double click the colors in the pane on the right to set the laser speed, power, and other features associated with that color. Black can be used to cut and red to etch, for instance. Use this chart to get a ballpark reference for speed and power settings: [[Big red laser cutter settings]]. It is recommended to do a "test cut" before cutting out a large file to be sure your speed and power settings are good.

[[File:Lightburn layer tips.png|frameless|LightBurn layer settings]]

# Select "absolute coordinates" to define the placement relative to the bed. Select "user origin" to set the placement on the bed manually. The device should be set to ttyUSB0, Ruida664GX.
# Once happy with design, click “Send”
# Enter a name (or just use default to override) and press enter.
# Wait for the file to send.

=== Running the laser ===
The following steps should be done using the control panel on the laser cutter itself.

# On the laser cutter control panel, press "File" to see available files.
# Scroll and press “Enter” to select a file.
# Set the origin if necessary.
# Press “Frame" to confirm placement. When you press this, the laser cutter head will trace around the max coordinates, to show you where your design will be cut.
# If the frame is correct press “Start”, and the laser will run.

=== Having Trouble Setting the Origin? ===
If you are using LightBurn to compose your project, be sure to use the setting "Current Position". 
Otherwise, LightBurn may override any origin you set at the laser cutter.

Setting the origin on the laser cutter is easy. 
On the front panel there are 4 arrow keys. You can use these to move the "head" around.
Pressing the "Origin" button sets that spot to be the origin of where cutting starts. Typically, this is the upper left
of the bounding rectangle around your artwork.
You may find that moving the "head" is much easier than moving the material placed on the bed!

== Other software ==

As mentioned, RDWorks can also be used. We haven't tried it yet but it seems it's a free download [https://www.thunderlaser.com/laser-download from here].

Some of the software (downloaded from the above link) is on the hard drive of wasp.local which is a desktop computer under the 3D printer desk, in a folder called ~/laser-backup/

[https://spaz.org/~jake/sudoroom/Big_red_laser_cutter/ The above software has also been downloaded and stored here]

it was setup with an IP address of 100.64.64.69 (by pressing buttons through the menu) but it had no ports open and then we just switched over to USB to the computer and it was working fine. The same software might work over ethernet but we didn't try.

== Trying other things ==
Andy is trying to find software to control the laser cutter. I can generate gcode instructions in Inkscape, but I don't know how to send them to the printer over USB.

I'm trying to install [https://laserweb.yurl.ch/|LaserWeb].

I ran the commands here : https://laserweb.yurl.ch/documentation/installation/36-install-raspberry-pi. But the server gave an error when started:

Server binding to all local IP addresses on port: 8000
internal/modules/cjs/loader.js:818
throw err;
^

Error: Cannot find module 'node-hid'
Require stack:
- /home/laser/Programs/lw.comm-server/server.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.exports.LWCommServer (/home/laser/Programs/lw.comm-server/server.js:168:13)
at Object.<anonymous> (/home/laser/Programs/lw.comm-server/server.js:4141:13)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/home/laser/Programs/lw.comm-server/server.js' ]
}

== Stuff made on the big red laser cutter ==

* I cut some 1/4 clear plastic suspected to be acrylic. Used .5mm/sec 100%/40% power. It cut all the way through but the edge was rough.

== Stuff seen around the space ==

== ventilation ducting ==

=== Cleaning ===

Clean the lens monthly

If the exhaust fan is not working well, it might need to be cleaned.

To clean, detach the fan and base from the laser cutter. The area circled in the below picture is where you need to get access.

[[File:Laser_fan_detach.jpg|showing where to detach laser exhaust fan|frameless]]

This is what the fan looks like detached

[[File:Laser_fan_detached.png|detached laser exhaust fan|frameless]]

This is dirty and needs to be cleaned

[[File:Laser_fan_dirty.jpg|dirty laser exhaust fan|frameless]]

Use a vacuum and toothbrush/wire brush to clean. A n95 mask is recommended too.

[[File:Laser_fan_clean.jpg|clean laser exhaust fan|frameless]]

=== history ===
a plastic adaptor was 3D printed to connect the 6" outlet of the exhaust fan to the 8" flexible duct leading to the roof hole:
<code>laserduct.scad
THICKNESS=1.5*25.4;
ID=5.75*25.4;
ID_LIP=ID-(0.25*25.4);
ID_LIP_THICK=0.2*25.4;
OD=7.75*25.4;
OD_LIP=OD+0.2*25.4;
OD_LIP_THICK=0.2*25.4;
difference() {
color("BLUE") cylinder(d1=OD_LIP, d2=OD, h=THICKNESS, $fn=100);
{
translate([0,0,ID_LIP_THICK]) cylinder(d=ID, h=THICKNESS, $fn=100);
translate([0,0,-0.5]) cylinder(d=ID_LIP, h=THICKNESS, $fn=100);
}
}</code>
[[File:Laserduct.png|3D printing exhaust duct adaptor|thumb]]

 
Also the duct/roof interface was improved and a new stand was made for the extractor fan. Yay for milkcrates! 

[[File:Fan-holder.jpg|thumb]]
[[File:new-vent-top.jpg|thumb]]

Membermatters

2026-03-13T03:17:00Z

Indoorjetpacks: /* Need to Setup, Immediate Actions */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-02-07 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers - done? we only have one
# Set up payment plans - also done, mirroring the ones on sudohumans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?

Membermatters

2026-03-13T03:16:31Z

Indoorjetpacks: /* TODO */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-02-07 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?

Membermatters

2026-03-13T03:16:15Z

Indoorjetpacks: /* Pain points: We need to fix these issues ... later */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-02-07 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Where's the place to change the Membership Plan Tier? Martin tried to do this and didn't find an easy way to do it
# '' Seems like some timedate setting is still configured to be DD/MM/YYY somehow?

Membermatters

2026-03-11T07:06:52Z

Indoorjetpacks: /* Making a dev environment */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-02-07 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Where's the place to change the Membership Plan Tier? Martin tried to do this and didn't find an easy way to do it
# '' Seems like some timedate setting is still configured to be DD/MM/YYY somehow?

3D Modeling

2026-03-02T17:33:28Z

Indoorjetpacks: /* Slicing */

= 3D Models =

We love open-source and use open-source 3D modelling software (mostly Blender) to create everything from spare parts to be 3D printed to virtual reality utopias featuring walkable streets in Oakland to cool museum exhibits on science targeting adults.

= 3D Models for 3D-Printing =

This page is about creating models for 3D-printing. At Sudoroom we have a [[Type_A_Machine|Type-A Machine]] 3D printer, and a [[TAZ_4|TAZ 4]] 3D printer, but models can be made by anyone anywhere, just like word documents don't have to be made on a machine attached to a 2D printer.
[[File:Taz4-3d-printer.jpg|thumb|left|link=TAZ_4]]
[[File:Type-A-Machines-series-1-3d-printer.png|thumb|link=Type_A_Machine]]
== STL Models ==

STL files are wireframe/polygonal representations of a 3D model. There's a number of ways to get them:

=== Write OpenSCAD (recommended) ===

[http://www.openscad.org/ OpenSCAD] is a programming language for describing 3D shapes. You write code on the left, and it renders your model on the right. Then you can export an STL file. It has many benefits:
* free, open source, cross-platform
* keyboard-centric, less mouse dragging
* your models are deterministic
* you can easily track your changes with git
* the [https://en.wikibooks.org/wiki/OpenSCAD_User_Manual manual] is pretty straightforward
* there's even a [http://openjscad.org/ browser javascript version]!

But the software still has a long way to go. Some annoying things about OpenSCAD:
* single-threaded rendering, so complex models take a long time
* no persistent cache, so if you close it, you must render all over again
* GUI blocks on rendering, so if your render takes too long you must kill it (save often)
* volatile syntax - for example, child() is deprecated in git master, but the alternative children() is not even supported by latest stable (2013.06)

=== Use other modeling software ===

* [http://blender.org Blender] is open-source and popular, and Sudoroom members have been offering workshops on how to use it!
* Google Sketchup is exceptionally easy to use because they profit when you map buildings for them.
* [http://tinkercad.com Tinkercad] (in Google Chrome)

=== Download them ===

You can find premade STL files:
* On [http://thingiverse.com/ Thingiverse]
* On the [smb://space/sudoroom%20public%20data/Projects/3DPrinting local file server]
* On sudoroom's [https://github.com/sudoroom github] ([https://github.com/sudoroom/magnets magnets], [https://github.com/sudoroom/sudo-blocks blocks], etc)
* [https://grabcad.com/ GrabCAD] is requires a login but has interesting stuff

== Slicing ==

3D Printers don't understand OpenSCAD or STL. They understand an extension of gcode, which is a decades-old language which sends direct instructions such as "heat to 100 degrees, move here, do this, move there, do that, cool down". In order to print a model you have to turn it into a series of 2D layers or "slices", using a program called a "slicer". Slicers output gcode. They need to be configured for a particular printer, with settings such as melting tempurature, bed size, fill style, overhang compensation, etc. Examples of slicing software:
* [[OrcaSlicer|Orca Slicer]] (installed on the [[Wasp.local|Sudoroom 3d printing desktop computer]]
* Ultimaker Cura (installed on the [[Wasp.local|Sudoroom 3d printing desktop computer]]
* Slic3r
* KISSlicer
* Skeinforge

Slicing for a particular machine such as our [[Type_A_Machine|Type-A]] should be documented at its own page.

[[Category:3DPrinting]]

Creality Ender-3 S1

2026-03-02T17:33:11Z

Indoorjetpacks: /* Overview */

==Overview==
'''Printer Name:''' Creality Ender-3 S1

'''Preferred Slicer:''' [[OrcaSlicer|Orca Slicer]]

'''Nozzle:''' 0.4mm

'''Bed Type:''' Textured PEI Plate

'''Filament:''' PLA

'''Octoprint:''' http://100.64.64.197/ (this will only work if you're on the local network / wifi)

==Status==
Working as of 11/19/2025

==Printing Tips==
Use 0.20 Standard slice profile

==Documentation==
* [https://wiki.creality.com/en/ender-series Creality Wiki]

==Maintenance Log==
Levelled bed on 11/19/2025

3D Modeling

2026-03-02T17:32:36Z

Indoorjetpacks: /* Slicing */

= 3D Models =

We love open-source and use open-source 3D modelling software (mostly Blender) to create everything from spare parts to be 3D printed to virtual reality utopias featuring walkable streets in Oakland to cool museum exhibits on science targeting adults.

= 3D Models for 3D-Printing =

This page is about creating models for 3D-printing. At Sudoroom we have a [[Type_A_Machine|Type-A Machine]] 3D printer, and a [[TAZ_4|TAZ 4]] 3D printer, but models can be made by anyone anywhere, just like word documents don't have to be made on a machine attached to a 2D printer.
[[File:Taz4-3d-printer.jpg|thumb|left|link=TAZ_4]]
[[File:Type-A-Machines-series-1-3d-printer.png|thumb|link=Type_A_Machine]]
== STL Models ==

STL files are wireframe/polygonal representations of a 3D model. There's a number of ways to get them:

=== Write OpenSCAD (recommended) ===

[http://www.openscad.org/ OpenSCAD] is a programming language for describing 3D shapes. You write code on the left, and it renders your model on the right. Then you can export an STL file. It has many benefits:
* free, open source, cross-platform
* keyboard-centric, less mouse dragging
* your models are deterministic
* you can easily track your changes with git
* the [https://en.wikibooks.org/wiki/OpenSCAD_User_Manual manual] is pretty straightforward
* there's even a [http://openjscad.org/ browser javascript version]!

But the software still has a long way to go. Some annoying things about OpenSCAD:
* single-threaded rendering, so complex models take a long time
* no persistent cache, so if you close it, you must render all over again
* GUI blocks on rendering, so if your render takes too long you must kill it (save often)
* volatile syntax - for example, child() is deprecated in git master, but the alternative children() is not even supported by latest stable (2013.06)

=== Use other modeling software ===

* [http://blender.org Blender] is open-source and popular, and Sudoroom members have been offering workshops on how to use it!
* Google Sketchup is exceptionally easy to use because they profit when you map buildings for them.
* [http://tinkercad.com Tinkercad] (in Google Chrome)

=== Download them ===

You can find premade STL files:
* On [http://thingiverse.com/ Thingiverse]
* On the [smb://space/sudoroom%20public%20data/Projects/3DPrinting local file server]
* On sudoroom's [https://github.com/sudoroom github] ([https://github.com/sudoroom/magnets magnets], [https://github.com/sudoroom/sudo-blocks blocks], etc)
* [https://grabcad.com/ GrabCAD] is requires a login but has interesting stuff

== Slicing ==

3D Printers don't understand OpenSCAD or STL. They understand an extension of gcode, which is a decades-old language which sends direct instructions such as "heat to 100 degrees, move here, do this, move there, do that, cool down". In order to print a model you have to turn it into a series of 2D layers or "slices", using a program called a "slicer". Slicers output gcode. They need to be configured for a particular printer, with settings such as melting tempurature, bed size, fill style, overhang compensation, etc. Examples of slicing software:
* [[OrcaSlicer|OrcaSlicer]] (installed on the [[Wasp.local|Sudoroom 3d printing desktop computer]]
* Ultimaker Cura (installed on the [[Wasp.local|Sudoroom 3d printing desktop computer]]
* Slic3r
* KISSlicer
* Skeinforge

Slicing for a particular machine such as our [[Type_A_Machine|Type-A]] should be documented at its own page.

[[Category:3DPrinting]]

Membermatters

2026-03-02T02:35:49Z

Indoorjetpacks: /* Pain points: We need to fix these issues ... later */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# 'echo "MM_ENV=Development" > ./docker/.env` - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `docker pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

== Some in-progress notetaking ==
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

some updates:
RechnerFox made a github action to update prod from a staging instance after that was [https://github.com/sudoroom/MemberMatters/commit/88529eec2418afd56302e7deaa4ccf2b3471aa88 added by jake]
2026-01-28: Martin and Nicholas did some work hacking on the vps to backup, delete, and recreate the database so we could start from scratch. This required doing a pg_dump of the existing db, and then entering the postgres docker container with exec, using pgsl -U membermatters. Then we renamed the existing database, and then went back to the [https://membermatters.org/en/latest/GETTING_STARTED.html getting started page of the mm docs and picking up after the "docker start" commands to load the initial data to the database.

Then Martin added himself and Judy, both times it threw errors because the email wasn't setup. MM says you need postmark, but in our fork we have code to get around that, but requires the postmark api key to be blank and the email default to be changed.
2026-01-30: Jake did those two fixes and confirmed he got a password reset email!
2026-02-05: Martin double confirmed email setup by sending a welcome email to himself and started trying to configure the logos, which he got from looking at the old mm email when it was setup and seeing what url was embedded in that email.

Django logs are doing a bunch of Warnings about not finding various /api stuff?
Logo changes aren't loading to the page :( Looks like it is attempting to load but no dice. Confirmed a matching format (png) and square size within favicon specs when linking to one from the wiki's logo page, and then linked to the old one but neither seem to be taking. --- Possible this is still due to all the Not Found /api stuff?

Nicholas suggested that was just some scrapers or bots hitting the page, tested with him trying to load /api/nicksun and that also showed in the logs the same warning.

Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.

== Currently ( 2026-02-07 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
= Membership Plan Setup =
== Adding a Membership Payment Plan ==
Left Side Bar > Admin Tools > Membership Plan > Plus Icon, make sure you click the checkbox for 'visible to members'

== Adding a new tier to the existing payment plans ==
Click the plan you made, click ''that'' plus icon.
The popup window shows up, Name your plan, CHANGE THE CURRENCY TO USD, and then add the amount
Notes: Make sure you also click the checkbox for 'visible to members' - if you don't do this, you have to go to the django page to set it (ie its not changeable by in the front end)

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

* 2026-02-10
ivan and martin and nick did a truth table to figure out statuses:

Membership Status / Subscription status
* Active / Active -> Member
* Active / Inactive -> Email to talk about payment (card error, payment lapse etc)
* Noob / Active -> Induction
* Noob / Inactive -> Induction
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''

= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Where's the place to change the Membership Plan Tier? Martin tried to do this and didn't find an easy way to do it
# '' Seems like some timedate setting is still configured to be DD/MM/YYY somehow?