OpenOakland subscribes to Code for America’s tenet that no one is coming; it’s up to us. We strive for consensus as much as possible and are continually working to build a collaborative community where members have the flexibility to lean into action, while maintaining accountability to each other and our broader Oakland community.
Brigade membership is open to all, regardless of expertise or skill level. We have a core team of elected representatives (known as Elects), supported by a Steering Committee that oversees activities and formal decision-making. The Steering Committee consists of the elected leads plus project representatives.
The brigade also has two Ombuds roles who are available to anyone who wishes to provide feedback, express concerns, report a Code of Conduct violation, or otherwise seek support. Ombudspeople are independent of the Steering Committee. These roles are currently vacant while we review our community agreements and Code of Conduct policies
How the Steering Committee works
The Steering Committee follows a set of bylaws that outline leadership roles, project requirements, decision-making processes, and additional brigade policies. All OpenOakland members are welcome to sit in on the committee’s monthly meetings.
What's the purpose of the Steering Committee meeting?
This is our monthly meeting to discuss and make decisions about brigade-wide activities and processes that impact us all.
When does the Steering Committee meet?
Steering Committee meets via Zoom on the third Tuesday of each month. Visit Meetup for upcoming dates. If you need accessibility accommodations to attend, please contact firstname.lastname@example.org in advance.
Who should attend?
Elects and project leads are expected to attend as regularly as possible. Projects may appoint any member of their team to represent the project as a voting member at any given meeting. Elects may appoint an alternate to represent them but the alternate may not vote. A majority of voting members must be present for the meeting to take place.
How is the meeting conducted?
The Chair moderates the meeting according to an agenda that covers general brigade updates, items to be voted on, and items for discussion. We encourage the use of Zoom's "raise hand" feature found in the Reactions toolbar, or placing your name in chat to be added to the speaking queue. We ask attendees to be mindful of the space you take up; please listen at least as much as you speak.
Who can add to the agenda?
Any OpenOakland member can add to the agenda.
What can I add to the agenda?
Agenda items should be relevant to brigade-wide operations. This may include new project submissions or ideas, proposals for policy or process changes, general discussion items about how we work together or specific activities, and questions, concerns, or feedback for the group. Projects who need brigade support can also add discussion items to the agenda.
How do I add to the agenda?
The agenda is pinned to the #oo-steering-committee channel in Slack. You may add your item to the appropriate section of the agenda according to the instructions in the doc. If you don't automatically have edit permissions, contact the Steering Committee Chair.
We recommend adding your items as far in advance as possible, to give members the chance to get familiar with your item. The Steering Committee chair will make a reasonable effort to ensure all items are heard but may limit the agenda or time spent on individual items at their discretion.
What do we vote on?
Any member or group of members may submit a formal proposal to be voted on (see the optional proposal template). Generally speaking, any item added to the Voting Items section of the agenda will be considered, time allowing. This is ultimately at the discretion of the Chair.
When do we vote?
The meeting Chair will review Voting Items according to the agenda sequence (usually after brigade updates). The person introducing the proposal will be asked to summarize, followed by a limited period for questions and clarifications prior to voting.
Each elected lead gets one vote, as does each project via a member of their team.
Projects don't need to send the same team member each month, but their voting rep should be part of the core team. If a project team doesn't send a rep, they're considered to be abstaining from any vote that month.
What are the voting rules?
A simple majority of votes is required for a proposal to pass.
- Once the proposal is introduced, either the chair or another member can "move to vote." This needs to be "seconded" by another member to move forward.
- The Chair will then invite and tally the votes via Zoom chat.
- If a proposal appears to need more discussion, any member may "move to table the proposal," to ensure there's sufficient time to address the rest of the agenda. Ideally, the group will agree to the next step for moving the discussion forward following the meeting at the time the proposal is tabled. This, too, must be "seconded" by another member for the proposal to formally be tabled.
- The Chair is responsible for maintaining this process and the flow of the meeting is at their discretion.
Where is the upcoming agenda?
The agenda is pinned to the #oo-steering-committee channel in Slack.
How are Steering Committee decisions communicated out?
The elect team will attempt to summarize major meeting items within a couple of days in the #oo-general channel in Slack, as well as at the following Hack Night and in the brigade newsletter.
How to contact the Steering Committee
You can reach Steering Committee members by emailing email@example.com.