Admin Committee Shared
- Admin Office Hours Calendar
- Admin Committee Office Hours Notes
- RC Office Hours - Programming - 4/12/26
- RC Office Hours - Tech-Comms - 4/19/26
- RC Office Hours - Facilities- 4/26/26
- RC Office Hours - Finance - 5/17/26
- RC Office Hours - All-Hands - 5/31/26
- RC Office Hours - Programming and Rentals - 6/07/26
- RC Office Hours - Tech-Comms - 6/14/26
- RC Office Hours - Facilities- 6/21/26
- RC Office Hours - Comms - 6/28/26
- RC Office Hours - Fundraising - 7/12/26
- RC Office Hours - Finance - 7/19/26
- RC Office Hours - All Hands - 7/12/26
- RC Office Hours - Programming - 8/2/26
- RC Office Hours - Tech - 8/9/26
- RC Office Hours - Facilities - 8/16/26
- RC Office Hours - Outside Comms - 8/23/26
- RC Office Hours - Fundraising - 8/30/26
- RC Office Hours - Finance - 9/6/26
- RC Office Hours - All Hands - 9/13/26
- RC Office Hours - Tech - 9/17/26
- SOP: RC Patronage and Social Reach Tracking
Admin Office Hours Calendar
Ridgewood Commons Admin Open Office Hours
Admin office hours meetings are held Sundays before dinner, 6-7pm, in the couch area unless stated otherwise.
Each Sunday is hosted by a different admin committee, with an all-hands meeting at the end of 8 week cycle.
These meetings serve to:
- Coordinate ongoing work within the group.
- Allow cross-committee work (meetings are open, pop-ins are encouraged).
- Be a space for people interested in admin work to come and meet existing members, get a feel for the work and group dynamics before they commit to taking on RC labor.
April | May |
4/12 Programming | 5/3 Outside Comms |
4/19 Tech | 5/10 Fundraising |
4/26 Facilities | 5/17 Finance |
5/24 All Hands | |
5/31 Off! No meet | |
June | July |
6/7 Programming | 7/5 Off! No meet |
6/14 Tech | 7/12 All hands |
6/21 Facilities | 7/19 Finance |
6/28 Outside Comms | 7/26 Fundraising |
August | September |
8/2 Programming | 9/6 Finance |
8/9 Tech | 9/13 All Hands |
8/16 Facilities | 9/20 Programming |
8/23 Outside Comms | 9/27 Tech |
8/30 Fundraising | |
October | |
10/4 Facilities | |
10/11 Outside Comms | |
10/18 Fundraising | |
10/25 Finance | |
Admin Committee Descriptions
Programming - Coordinates use of space across both free RC-hosted events and rentals. Reviews programming & rental form submissions (ridgewoodcommons.nyc), develops programming based on committee goals, community interest & feedback.
Tech - Manages tech infrastructure: Site framework and deployment, collaborative tools.
Facilities - Repairs and replaces space equipment and fixtures, develops layouts and strategies for space organization, coordinates garbage/recycling/compost, coordinates consumables purchasing and storage.
Outside Comms - Collects event info and produces weekly calendar graphics, poster, and flyers. Manages instagram, bluesky., mailing-list.
Fundraising - Organizes fundraising events and grant opportunities.
Finance - Pays bills, reimburses expenses, coordinates with fiscal sponsor and payment platforms, reports financial information.
All hands - Meeting of reps from all admin committees. All-hands are broader reviews of both suggestions and problems raised at individual committee meetings.
Notes for past meetings can be found on this wiki.
Flyers for admin meeting promotion:
Programming
Tech Admin
Facilities
Outside Comms
Fundraising
Finance
All-hands
Admin Committee Office Hours Notes
There's no clear place for notes or agendas for the newly created weekly Admit Committee Office Hours, so I made this.
RC Office Hours - Programming - 4/12/26
Programming (6): S, J, V, I, C, K
Outside (4): L, A, Z, A
Topics discussed:
--- Booking overlaps + structure & decision making + coordination across groups
--- SOPs
--- Basement
--- RC onboarding materials / flow
--- Block party
--- Open Studios
--- Booking overlaps + structure & decision making + coordination across groups
Diffuse engagement with booking requests, based on who gets to the proposal first/engagement with submitter.
Grandfathered events
If/how to prioritize across RC-emergent events vs outside proposals
+ balancing with space financial needs.
Trial 5 week run of J poli-ed sundays didn't have great experience in space, loud, other stuff still going on...
Upranking criteria have been:
- political content
- proposed by RC community
Downranking or denying criteria:
?
Overlapping events means overlapping *audiences* which could conflict in some cases. Duality of mixed events, can be synergistic, can be problematic.
-- Coordination across groups
Ideas:
Weekly "leads" - someone to take a week in the future - could help build calendar further into the future, requires more people - could also get confusing (how to record/indicate week-lead)
Per day chats:
Signal chats per day could help coordinate across a specific day, and create a point of contact if you know the day an event happens.
Centralized chat:
The spokescouncil WG chat could be repurposed.
Another chat could be made.
In any chat setup, Signal group member labels (new feature) could be very useful here, allowing people to indicate WG/AC membership
--- SOPs
https://wiki.commons.nyc/books/rc-programming/page/programming-sops
Needs review + additions for some specifics: advertising and cross-promo for sensitive programming
https://wiki.commons.nyc/books/rc-programming/page/best-practices-for-screenings-and-projected-amplified-presentations
SOPs and onboarding materials need to be agreed on/seen/read/referenced - lonely wiki pages are not sufficient:
- QR links and signage in locations (e.g. on PA, computer)
- Physical material: zines, trifolds
- Actual in-person sessions
--- RC onboarding materials / flow
Dinner has been working to address: food safety zine
Could be addressed via WG/AC onboarding, or general RC onboarding
--- Block party
- got permit account
- get 50% of neighbors to sign off (physically)
- Application needs to be physically delivered to meeting
- block map: https://wiki.commons.nyc/books/rc-programming/page/block-maps
--- Open Studios
- Tutoring -> Kids crafting studio Sat/Sun led by different groups
- Food
- 3 vendors, maybe one dropped out
RC Office Hours - Tech-Comms - 4/19/26
Committee attendance (#) - Mi, P, L
Outside attendance (#) - Mo
Resulting Next Action Items
- TODO set up a self-signup form for emails
- this will ping a number of people over email who have admin access to the the account system and will manually create an account
- needs some copy explaining the potential risks in submitting the info & encourage using burner emails
- need people to volunteer to be the account creators
- TODO move vikunja project management software from projects.beta.ridgewoodcommons.nyc to projects.ridgewoodcommons.nyc
- TODO migrate the data from the bookstack instance at wiki.commons.nyc to wiki.ridgewoodcommons.nyc
Topics:
- "Tech" issues that are holding us back as an organization
-
Cross group coordination
-
Site/URL confusion
-
Account creation
-
Lack of movement on core "space replication" functions
-
-
Opportunities for clarity
- Individualized pain points - What could change that would make your life easier?
-
Things to put a bow (if temporary) on
"Tech" issues that are holding us back as an organization
Cross group coordination
- There's no "many to many communication" channel that isn't scoped in a way to cause people to wonder "is this the right place for this?" e.g. Spokescouncil chat is unclear.
- The entire wall has become this, but mostly in an "attention extractive" way, like "come to my thing," vs "Does anyone want to x/yz?" and there's no delimiter between RC, RC community, and outside stuff.
- Admin committees and working groups are Signal silos
Proposals gathered from various chats…
- Day-scoped chats - Signal chats for M/Tu/W/Th/F/Sa/Su
- Gives very clear structure, tightly integrates different events
- Probably pretty quiet.
- Great for WGs and recurring events
- Bad for ACs, e.g. facilities, programming, finance.
- "Grand Central Chat" - A unified chat, with members from various ACs, WGs, and otherwise.
- Probably noisier. Member labels might let it function on mute. (Do @s override mutes?)
All of the above would benefit from using the new-ish Signal "member label" system. So Whether day-chats, or a unified
All chats still suffer from the fact that almost nobody reads group descriptions. Not sure about pinned messages, but in any case they're not visible to new members?
Site/URL confusion
wiki.commons.nyc
*.beta.ridgewoodcommons.nyc
ridgewoodcommons.nyc
Having tools broken up across domains hurts both use and utility
Account creation
Lack of an account makes tools read-only, increases confusion & sense of social capital.
Lack of movement on core "space replication" functions
- programming and rentals management
- mailing list
- finance
Opportunities for clarity
- Division of work
- Network connectivity
- Hosted applications
- Semi-hosted tools
- Site
- Group names
- Tech Comms ->
- Tech & Intranet
- Tech & Coordinating
- Tech & inside comms
- Tech Infrastructure
- This could mean that the site becomes a collab between Tech Infra & Outside Comms
- RC IG coord ->
- Comms
- Outside Comms
- Tech Comms ->
What could change that would make your life easier?
These meetings are a good start for me, gives a time & place to send people. - LP
Things to put a bow (if temporary) on
- Outline vs bookstack
- Knowledge store ACLs and visibility
Raw Notes from meeting
https://wiki.ridgewoodcommons.nyc/books/admin-committee-shared/page/rc-office-hours-tech-comms-41926
Topics:
"Tech" issues that are holding us back as an organization
Cross group coordination
Site/URL confusion
Account creation
Lack of movement on core "space replication" functions
Opportunities for clarity
Individualized pain points - What could change that would make your life easier?
Things to put a bow (if temporary) on
Domain Name
Working group software User Testing (e.g. pantry try riseup?)
Excitement on
nyc mesh
ny mesh
visibility of invisible work - roles board
removal of Proposals label on board
meta note if not in chat, can't see chat-shared agendas
Things working well
* What's Going On? I go to https://ridgewoodcommons.nyc
Notes:
- We need many to many communication channel
- seems like the giant physical wall is the channel
- Micro has explored some wall hierarchies
- Zulip/Mattermost+
- consensus on signal: skepticism, willingness to experiment, try Signal solutions before bigger project of alt software solution
-
What situations where someone can't find a channel, or there doesn't appear to be a chat.
Story: New to space: where is everybody? how do I get involved? Where do I find people interested in x/y/z
- next action item: move bookstack to wiki.ridgewoodcommons.nyc & migrate data. decide what to do about
- next action item: move vikunja off beta subdomain
-
- invite code
- self-signup (open)
- self-signup (moderated)
- form submission + manual accout creation
- unlisted/obscured URL
- Against 3rd party auth (Google, etc)
- MVP for self-signup:
- form at a hidden URL that pings a small list of email addresses that have admin access and can create an account for them
- bot worries
- human worries
- vandals
- deletion
- false engagement
- polution of user database
MVPs
/register
ACLs
- next action item: create a secret endpoint that allows users to submit a form that asks for their desired username & email, email a small number of admins who will then create the account for them. make sure to include some copy the relays the risks of submitting their info
Tech Infrastructure
RC Office Hours - Facilities- 4/26/26
Committee attendance (3) - L, R, I
Outside attendance (0)
Topics
Discussion:
- Delivering to friendly 9-5 business: bodega, nail salon
- Could be an unwelcome burden for a business - but as a backup delivery option seems a good fallback.
-
- In later conversation someone pointed out to me that USPS typically has a key to a lockbox, and even then can only access the entry way, not enter the building. ~LP
RC Office Hours - Finance - 5/17/26
Group attendance: D
Outside attendance: S, P, L
Topics
- Getting people into RC Finance Consensus Signal group
- Fiscal Sponsor, etc.
- Account balance and access
- W9(?) status
- Nonprofit consultation
- Floating Expenses
- Finance AC
- Attrition
- Workflow development
- Better chart workflow
- Better chart workflow
RC Finance Consensus Signal group representation:
Facilities
Tech
Basement
Finance
Sunday Dinner
Pantry
Programming
Kids Crafts
Fundraising & Grants
Yearbook
Liability
Writing Workshop
Fiscal Sponsorship
3 months since last account check
Monthly would be good, to catch problems (change in platform payouts, etc) before they become big problems.
S will meet w/sponsor and bring up monthly reconciliation
W9 status: good on both platforms
P reached out to M re: a consultation on process to gain nonprofit status
Floating Expenses
Made a page for potential expenses: https://wiki.commons.nyc/books/rc-finance-home/page/potential-expense-backlog
TODO/Done (P): follow up with M re nonprofit consultation
TODO/Done (P): Monkey followup
TODO: S to shadow finance operations -
TODO: Shea monkworx meeting
Finance AC
Attrition
Since RC swap, finance has gone from 4 ppl to essentially 1.
S to shadow finance operations - potentially document current process?
Might be nice to create specifically scoped roles, eg:
- Monthly reporting
- Rent, bills, fines, reimbursement
- Reconciliation and data entry
Workflow development
Current workflow is functional, sophisticated, but possibly would be good to mimic established conventions?
L at BCF is an accountant, has been contacted by P for consult.
Chart workflow
Might be nice to have scripts which process CSV input and create standardized reporting graphics.
RC Office Hours - All-Hands - 5/31/26
Didn't meet
Comms / Outside Comms / IG coord
RC Office Hours - Programming and Rentals - 6/07/26
Attendance
Inside: 2
Sh, Sh
Outside: 3
Ch, L, Ca
Topics
- Block party updates
- What to pair C screenprinting event with?
- Storage and electrical guidance for Mercado
- Reiterate kitchen closing standards to all groups / recurring programming
- Ask C (pantry) to join programming?
- Outline scoped programming group roles to advertise to community
Todos
- Do a measured sound volume check w/neighbors (schedule or pass on contact info @v)
- Make a circuit chart to show how power should be run for events. (@L)
- Share pic of table & banner location to mercado (@L)
- Refine and share programming "role" for sharing to community announcements and flyers
Maybe Todos
- Make "not Ridgewood Commons trash" sign? (@L?)
Discussions
Block Party Updates
What to pair C screenprinting event with?
Storage and electrical guidance for Mercado
Tables
Left in space without reply to question of if it's ok
They were placed behind booth
Garbage
L+Mar removed Mercado trash from 585 residential garbage, moved to RC garbage bins
Electrical routing
Power was run to basement, to an extension cord. Not great, and not what was explained. Asked organizer, they didn't know how it happened.
Reiterate kitchen closing standards to all groups / recurring programming
Ask C (pantry) to join programming?
Outline scoped programming group roles to advertise to community
- End of night closing checker
- frig temps
- furniture reset
- dishes
- Wellness check on equipment (facilities?)
- Advertising location list (outside comms?)
- Online promotion (outside comms?)
- In-space signage and calendar cleanup and management
- proposals / nyc-mesh / painting wall posters
- door
- frig
- towards categorizing info in space
- Try to start categorizing what type of info gets taped up, start thinking about how it might be categorized, and what stuff we can prune, e.g.
- Local call to action
- National call to action
- Personal service advert
- RC event advert
- Commercial advert
- Try to start categorizing what type of info gets taped up, start thinking about how it might be categorized, and what stuff we can prune, e.g.
RC Office Hours - Tech-Comms - 6/14/26
Attendance
Inside: 3
P, L, V
Outside: 0
Topics overview
- wiki migration
- https://wiki.commons.nyc/books/rc-tech-admin/page/june-2026-state-of-the-infra
- Self-hosting workflows
- mailing lists
Todos
- WIKI
- Migrate books to wiki.ridgewoodcommons.nyc (@p)
- Async use pads to create new hierarchy (@all - https://pad.disroot.org/p/zXn2eoK2Ta8ZTHOs5vw-)
- Move books to match agreed upon structure (unassigned)
- State of RC tech 2026
- Group members read over doc (https://wiki.commons.nyc/books/rc-tech-admin/page/june-2026-state-of-the-infra)
- Offer comments in chat or on wiki
- Discuss at next meet
- MAILING LISTS
- Post potential services (koumbit / may first) to signal chat
Discussion
Wiki Migration
Very little progress over last 9 weeks. One ad-hoc workday.
Probably good to change our structure re: shelves/books
Plan:
- Migrate books to wiki.ridgewoodcommons.nyc
- async use pads to create new hierarchy
- lp move books to match agreed upon structure
We will lose history, but that's ok.
2026 state of the infra
https://wiki.commons.nyc/books/rc-tech-admin/page/june-2026-state-of-the-infra
Actions:
- group members read over doc
- offer comments in chat or on page
- discuss at next meet
Self-hosting workflows
For various reasons: Discussion of using Ansible for initial server config, either in conjunction with coop cloud, or possibly with coolify.
Mailing Lists
Potential to use koumbit or may first $125/annual plan for pretty namespaced mailing lists + shared hosting fringe benefits.
Tabled
Bitwarden/vaultwarden improvements
Upgrading plan or exploring options
RC Office Hours - Facilities- 6/21/26
Attendance
Inside: 2
L, R
Outside: 2
C, E
Topics overview
- Flooding (backflow valve)
- Consumables (again)
- <topic>
Todos
- Backflow research
- Make script for plumber calls -
- Call plumbers
- Todo: Call webstaurantstore.com and see if we can get a business account such that we're invoiced, to make ordering easier.
Discussion
Flooding (backflow valve)
List of licensed plumbers here: https://wiki.commons.nyc/books/rc-facilities-homepage/page/list-of-licensed-plumbers
Riseup pad version here for those without wiki logins, and to make script: https://pad.riseup.net/p/ysLaTSmzA-DJ22ve1dbO
Suggested we make a rough script outline to make it easier to divvy up calls..
Consumables (again)
Todo: Call webstaurant store and see if we can get a business account such that we're invoiced, to make ordering easier.
Discussion of using "roof" of bathroom to store larger orders of TP, 4x+ our normal purchase.
Discussion of building a small hutch in bathroom to store full package of TP, help clear out shower area. Convo started around a hutch style plan, but the area behind toilet is narrow and 47" wide, so might be easier to run shelf along left wall (as seated on toilet), could be 12" deep, 53" max length.
RC Office Hours - Comms - 6/28/26
Attendance
Inside: 2+1
C, M, L
Outside:
Topics overview
- "First touch info"
- Display case
- In space signage
- Promo outlets
- Website
- Hello World posts
Todos
- Hello World Posts: table to brainstorm copy that would be shareable around our values/structure/governance
-
- Promo Outlet Wiki: Set access permissions to not need account (@LP). Communicate to ppl on how to use.
- Display Case: Async iteration with wireframes (@all)
- Draft proposal for using pantry space to host welcoming signage
Discussion
External Promotion Locations
Other physical places to promote RC events? General agreement: Let's make a wiki to collect bulletin boards around town
Display Case & Outdoor Signage
How do we want to greet people who first encounter us physically?
"Hello, World" Posts: Maintaining an occasional Bluesky Presence
What if we occassionally showed up on socials to share that we exist and what we're about? Kinda like a way to let people who are looking for spaces like ours can share and disseminate to their networks?
——————————————————————————————————————————————————-
LP
- 1/2 page paper flyers vs web images
-- Tool could generate 2-ups for printing, and standard 4x5 for online?
-- 2-ups could be either orientation
-- Could strip event details from 4x5?
- Event promo outlets
-- Wiki list with contextual guidance as to what for where?
-- Location list as well, also useful for fundraising
- Information hierarchy in space
-- More bulletin boards? Larger board with tape strips to break up space?
-- Where
-- Hatch gate mounted board?
- Use of outside display case
-- Weekly schedule limited to 8.5x11
-- Larger regular programming poster could be larger?
-- Solar LED lighting strip?
- Use of door space
- Pools events
-- more consistent
-- +1w ahead
- Promotions as list vs forward
-- Pro: self-managed or collectively moderated membership vs tech bottleneck
-- Risk: people forgetting it's a list and doing an oops?
- Periodic "Hello World" post
-- Post an occasional intro style post: Hello world, for those who don't know, Ridgewood Commons is....
Website
How to easily donate
Over-signage - > info hierarchy
RC Office Hours - Fundraising - 7/12/26
Attendance
Inside: <number of committee members present>
<initials>
Outside: <number of people from other groups or otherwise new to group>
<initials>
Topics overview
- <topic>
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
RC Office Hours - Finance - 7/19/26
Attendance
Inside: 1
D
Outside: 2
Sh, L
Topics overview
- <topic>
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
RC Office Hours - All Hands - 7/12/26
Attendance
Inside: 6
Sh, D, V, Sh, I, L
Topics overview
- Removal
- Calendar conflict
- Waivers
- ments
Todos
- F
- Waiver printing/signing process
- Admin groups to create longer blurb and/or flyer to be shared alongside weekly cal in community announcements.
Discussion
Removal
- Reporting process
- Currently depends on individual high-trust connections / whispers
- Improvement: Include link to feedback form in current signage development project.
- Conflict / Safety process creation
-
Calendar conflict
CSA wasn't listed on calendar. Blood-drive was booked. Conflict between two had negative effect on both.
Waivers
RC Office Hours - Programming - 8/2/26
Attendance
Inside: <number of committee members present>
<initials>
Outside: <number of people from other groups or otherwise new to group>
<initials>
Topics overview
- <topic>
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
RC Office Hours - Tech - 8/9/26
Attendance
Inside: <number of committee members present>
<initials>
Outside: <number of people from other groups or otherwise new to group>
<initials>
Topics overview
- <topic>
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
RC Office Hours - Facilities - 8/16/26
No meeting.
RC Office Hours - Outside Comms - 8/23/26
Attendance
Inside: <number of committee members present>
<initials>
Outside: <number of people from other groups or otherwise new to group>
<initials>
Topics overview
- Signage development review
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
RC Office Hours - Fundraising - 8/30/26
Attendance
Inside: <number of committee members present>
<initials>
Outside: <number of people from other groups or otherwise new to group>
<initials>
Topics overview
- <topic>
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
Notes from outside meeting
RC Office Hours - Finance - 9/6/26
Attendance
Inside: <number of committee members present>
<initials>
Outside: <number of people from other groups or otherwise new to group>
<initials>
Topics overview
- <topic>
- <topic>
- <topic>
Todos
- <todo>
- <todo>
- <todo>
Discussion
Topic
Topic
Topic
RC Office Hours - All Hands - 9/13/26
Attendance
Inside: 3
I, M, D
Outside: 4
A, G, S, E
Topics overview
- Admin open meetings review
- RC Office Hours - Programming - 8/2/26 - no notes
- RC Office Hours - Tech - 8/9/26 - no notes
- RC Office Hours - Facilities - 8/16/26 - no meeting, no notes
- RC Office Hours - Outside Comms - 8/23/26 - signage
- RC Office Hours - Fundraising - 8/30/26 - no notes
- RC Office Hours - Finance - 9/6/26 - no notes
- Legal & Liability has no admin meetings scheduled.
- Orientation for new people: committee summaries, four points of unity, space history, current needs
- Spokescouncil meeting preview (next week): review of inactive working groups, drafting a list of principles, "what is this space?", International Cooperative Alliance
- Committee summaries: Fiscal Admin (HungryMonk sponsor, seeking new fiscal sponsor), Programming/Rentals (community events + space rentals), Fundraising & Grants (bake sales, zine/craft fair idea, relationship with future space across the street), Facilities (supply lists, bulk buying), Legal/Liability (lease signatories, waivers), Comms/Tech (Instagram, mailing list, website, Signal/Discord issues)
- Space history: origins at Woodbine, the split, Spokescouncil + Working Group/Committee "two wheel" structure, declining attendance at Spokescouncil
- Needs discussion: burnout/fresh faces, shared Google Drive, unclear org chart, clearer proposal process, dynamic charter needs/wants, Points of Unity, General Assembly as internal meeting format
- Recruiting into admin committees: publicizing meetings, calls to action, onboarding/offboarding process, labeling meetings by function
Full Notes
Agenda
- Overview for the new people (25min)
Admin committees brief summaries, four points unity, history, what does the space need - Spokescouncil Meeting: Next week (25min)
- Overview of working groups not working/falling
- Drafting a proper list principles
What is this space?
S. Brings up international cooperative alliance - General Discussion/Questions
Defining Working Group
- Has 5 ppl, a charter, meets regularly
- Fiscal Admin Commitee:
HungryMonk, 501c3 is our sponsor, aren't charging us a fee.
We are looking for a new fiscal sponsor - Programming/Rentals Committee
- Free Community events
- Rentals: ppl shot film here, bday parties, shabbat dinners
- Deliberates mostly as a group chat
Fundraising & Grants
- Could use more support (grant writers)
- Bake Sales are a big pull for us
- No zine fair or craft fair, make stuff and sell
- Bringing up a more intentional relationship with future space across the street
Facilities
- Big grab bag of stuff
- We have lists of where to get stuff (L compiled)
- S brings up bulk buying
Legal/Liability Committee
- Two people whose names are on the lease
- waivers, anything with children
Comms/Tech Committee
- Instagram, mailing list, flyers, information display, way finding, communicating to our base
- Website, online
- Signal is really not working for discord
History:
- Convos around last summer while it was still woodbine was a desire to have some sort of democratic, collectivist structure.
- Once the split happened, Spokescouncil was already on the table and there was an emergency committee meeting
- A two wheel structure, Working Groups and Committees.
- Fewer and fewer ppl came to the spokes council meeting. There was less to talk about.
- The proposal model was so that people could make proposals
- We wanted to maximize democracy and transparency,
S: bring up the point of bringing up solidarity between groups
Since Woodbine was built on a decision-maker that afforded people to do their own thing, now we are trying to desilo without the urgency of saving the space
time-banking
allocation
M doesn't want to dissaude people from sharing new ideas, but is asking us to stay on agenda before we start throwing out ideas on how to restructure the space.
Needs
= allocation
E discussing: what if the charter had needs and wants being dynamic
I: brings up General Assembly also as a internal type of meeting
I: Points of Unity would help to foster this more collectivist structure
Needs:
What does the space as a whole need?
- D: Fresh faces and help. BURNOUT.
- Shared Google Drive
- Unclear Org Chart
- Reliable, clear process to submit proposals
D: Concern about defining structures so that members are stuck in roles.
Challenge: Volunteer
Post all three drafts in the community announcements channel,
Check in with the chat to ask if there are any final additions.
Not chair person model, but rather identify the skills needed for that tas
E: What is the strategy to recruiting into admin?
I: Publicizing these meetings, but doesn't have more in the way of ideas. Drawing attention to the structure itself.
E: Creating a call to the action for people to direct people into admin committees, putting the history and structure in writing
G: Onboarding / Offboarding members of the community
E & M: Labeling the meetings
To-Do's
- D: Put the pie chart in the wiki
- M: Add S to Comms
- M: Bring up zines to Comms
- E: Send M the zine
- M: Bring up to Comms adding a summary of meetings
- Next meeting: Sunday the 20th, 3–5pm
Discussion
Topic: Committee/Working Group structure review and history
Topic: Space needs (burnout, org chart clarity, proposal process)
Topic: Recruiting and onboarding into admin committees
Pre-meet topic dump
- Need for secretarial person/group? ~LP
- 2-part ACs (work/dev) ~LP
RC Office Hours - Tech - 9/17/26
Attendance
Inside: 1
L
Outside: 1
I
Topics overview
- Authentik / Wiki new user flow
- Scheduled admin meeting reminders via android signal
Todos
- P to set up batch of admin meeting reminders
- LP to make basic SOP for new wiki users
Discussion
Authentik / Wiki new user flow
L now doing some Authentik / Wiki user management
Some very basic SOP might be helpful for adding new people, or passing on work
Scheduled admin meeting reminders
P is fine with taking on the work of scheduling a batch of admin meeting reminders.
P in all admin chats? There's both CA+AC messages to send.
Tabled
Tabled
- Calender rewrite tool
- i would add https://www.pikapods.com/ to the list, not able to login rn
SOP: RC Patronage and Social Reach Tracking
Docs and sources
In drive: “RC Patronage & Social Tracking”
https://pools.events - “Memberships” tab
https://patreon.com - “Insights” tab, set to “tiers”
RC Patronage & Social Tracking sheets/tabs
-
p tally - weekly snapshot of patreon tier subscriptions
-
wf tally - weekly snapshot of withfriends tier subscriptions
-
platform 📊 - stacked bar chart showing platform usage split
-
tier tally - sum of platforms by tier, with small constants added for better charting
-
tier tally (📈) - chart of tiers
-
revenue tally - uses tier tally with multipliers (tier cost) to create $ per tier listing
-
revenue % by tier - breaks down tiers by % of total revenue
-
socials - data for a range of social media and outreach platforms
-
socials (📈) - chart of social media and outreach #s
Process
p tally - populated by manually updating counts, date is manually entered
wf tally - populated by manually updating counts
All other subscription tracking sheets are automatically populated via cell formulas
Date on all sheets aside from 'p tally' is populated via array formula referencing 'p tally' sheet