Merge pull request #269 from openoakland/ops-updates

Closes #268 and #222.

src/_data/resources-brigadeops.yml

@@ -14,8 +14,8 @@
  name: Steering Committee Bylaws
  author: OpenOakland
  description: The guiding regulations adopted by OpenOakland when we moved to a steering committee leadership model.
- format: Google Doc
- link: https://docs.google.com/document/d/1QR-fr1WnmXkZoVNmWnZ9drzfmaZoPkodEOx-PkExt94/edit?usp=sharing
+ format: Website
+ link: /bylaws
  button-text: View Resource
  secondaryLink:
  secondaryLinkText:

src/_includes/bylaws.html

@@ -0,0 +1,3 @@
+<div class="iframe-container iframe-embed-doc">
+  <iframe class="iframe-embed-doc" src="https://docs.google.com/document/d/e/2PACX-1vQPwPlg1Aq9gXXt6Ri1yN29MZxNgC627IXpK1hev2iyRUle7c8QsnUYW6MlUjUY71oDvi9814Z-i0Ym/pub?embedded=true"></iframe>
+</div>

src/_includes/footer.html

@@ -8,7 +8,7 @@ <h6>Additional Information</h6>
           <br />
           <a href="{{ site.baseurl }}/our-values">Our Values</a>
           <br />
-          <a href="https://docs.google.com/document/d/1QR-fr1WnmXkZoVNmWnZ9drzfmaZoPkodEOx-PkExt94/">Brigade bylaws</a>
+          <a href="/bylaws">Brigade bylaws</a>
           <br />
           <a href="{{ site.baseurl }}/press">Press Page</a>
         </div>

src/_includes/header.html

@@ -1,4 +1,9 @@
 <header class="site-header">
+
+<div style="background-color:alert-danger; width:100%;">
+  {% include home-sections/announcement-warning.html %}
+</div>
+
   <nav class="navbar navbar-expand-lg navbar-light ">
     {%- assign default_paths = site.data.navigation | map: "path" -%}
     {%- assign page_paths = site.header_pages | default: default_paths -%}

src/_includes/home-sections/announcement-warning.html

@@ -1,3 +1,3 @@
 <div class="alert alert-warning" role="alert">
-  OpenOakland condemns the anti-democratic insurrection. <a href="https://openoakland.org/statement-on-capitol-insurrection/">Read our statement</a>.
+  <p style="font-size:.9rem; padding-left:3rem; padding-right:3rem; margin-top:5px; margin-bottom:0px;">OpenOakland has paused upcoming meetups and newcomer onboarding while we revisit our governance structure to better accommodate the realities of an all-volunteer brigade. <a style="font-size:.9rem;" href="/updates/mar-2022-steering-committee-update/">Get the details</a>.</p>
 </div>

src/_posts/2021-10-04-september-steering-committee-recap.md

@@ -54,7 +54,7 @@ While the Steering Committee hopes for clarity from Code for America around its
 
 ## Discussion: Project requirements
 
-The initial pilot of our [Project Team Scan](https://docs.google.com/presentation/d/1lADVpWHaqQKSd05mlCtsYvk8rd2Jlg-iMhSwxQGvBa4/edit?usp=sharing) was intended to gather critical project details to enable Steering Committee oversight and public access to projects, and to gauge the health of project teams. The results revealed that while most projects make their code and documentation publicly accessible per the open source guidelines described in OpenOakland’s bylaws, Councilmatic currently does not have an up-to-date Github repository or recent documentation available to the public. Councilmatic has also not sent a project rep to Steering Committee meetings since January 2021, despite the bylaws [mandating that project teams send a voting representative](https://docs.google.com/document/d/1QR-fr1WnmXkZoVNmWnZ9drzfmaZoPkodEOx-PkExt94/edit#heading=h.djbozkxsdpw8) in an effort to ”give back and actively shape the organization to meet its needs.” September’s discussion focused on how best to address this in a way that enables Councilmatic to become a productive, contributing member of the brigade family of projects.
+The initial pilot of our [Project Team Scan](https://docs.google.com/presentation/d/1lADVpWHaqQKSd05mlCtsYvk8rd2Jlg-iMhSwxQGvBa4/edit?usp=sharing) was intended to gather critical project details to enable Steering Committee oversight and public access to projects, and to gauge the health of project teams. The results revealed that while most projects make their code and documentation publicly accessible per the open source guidelines described in OpenOakland’s bylaws, Councilmatic currently does not have an up-to-date Github repository or recent documentation available to the public. Councilmatic has also not sent a project rep to Steering Committee meetings since January 2021, despite the [bylaws](/bylaws) mandating that project teams send a voting representative in an effort to ”give back and actively shape the organization to meet its needs.” September’s discussion focused on how best to address this in a way that enables Councilmatic to become a productive, contributing member of the brigade family of projects.
 
 ### Clarifying team requirements
 

src/_posts/2022-04-03-mar-2022-steering-committee-update.md

@@ -0,0 +1,105 @@
+---
+title: "Leadership Transition Status: March Steering Committee Recap"
+author: OpenOakland
+layout: post
+date: 2022-04-03 00:00:00 -0800
+permalink: updates/:title/
+feat-img: /assets/images/blog/2021-07-Banner-meetup-Steering.png
+feat-img-alt: Volunteers sit in chairs in a semi-circle in a room in City Hall
+post-excerpt: "OpenOakland is unable to hold an election for brigade leadership, per our bylaws, due to a lack of leadership nominees. The Steering Committee has been working on a contingency plan to address short-term operational needs and long-term structural improvements. We will be putting these to a member-wide vote in the coming weeks..."
+---
+
+**OpenOakland is unable to hold an election for brigade leadership, per our bylaws, due to a lack of leadership nominees. The Steering Committee has been working on a contingency plan to address short-term operational needs and long-term structural improvements. We will be putting these to a member-wide vote in the coming weeks.**
+
+![Green-tinged photo of OpenOakland members seated around tables in City Hall overlaid with the words 'Steering Committee' in white.](/assets/images/blog/2021-07-Banner-meetup-Steering.png)
+
+Although we were planning to hold our annual leadership election this month, the elections team received only two nominations for leadership roles and neither nominee wanted to commit to running as a co-lead. As a result, we're unable to hold an election for brigade leadership, per our bylaws. The Steering Committee is now working on a contingency plan to address short-term operational needs and long-term structural improvements.
+
+***Jump to:***  
+[Potential operational approaches](#approaches-for-resolving-the-lack-of-leadership) | [Lean Ops tasks](#covering-lean-ops-tasks) | [Upcoming membership vote](#putting-lean-ops-mode-to-a-membership-vote) | [Potential speakers](#potential-speakers) | [Comments wanted: Community Commitments](#comments-wanted-on-new-community-commitments) | [Code of Conduct consultation](#update-on-code-of-conduct-consultation-proposal)
+
+March's focus has been on updating the Steering Committee on the status of leadership elections and the implications for brigade operations:
+
+- Our bylaws require co-leads to be elected by general membership.
+- Temporary vacancies may be appointed by a Steering Committee vote but this doesn't solve the failure to hold a general membership election.
+
+The fundamental need is a process for reevaluating the brigade's core purpose and activities, addressing the engagement issue, and revising the brigade structure and governance represented in the bylaws to hopefully mitigate the risk of this situation happening again. Since that will be a significant effort, we need a short-term plan to address what happens during that process.
+
+## Approaches for resolving the lack of leadership
+
+- **Pause mode:** Negotiate with Code for America to hold our funds (about $10k) and IP for a limited time, temporarily suspend operations (no meetups, no project work), and develop a process to reevaluate the brigade's core purpose and activities, address the engagement issue, and revise the brigade structure and governance represented in the bylaws.
+- **Lean Ops mode:** Divide the core [operational tasks](https://docs.google.com/spreadsheets/d/11r1jlQmfpU4YQpnVYydcmRgaiJAmW8t33Ku5DHBjoPA/edit?usp=sharing) required for minimum functionality amongst Steering Committee members (and any other volunteers interested in helping).
+- **Shutting down the brigade**.
+
+Everyone agreed we didn't want to shut down the brigade if a viable alternative could be found. But lean mode essentially means abdicating the membership election required by the bylaws, so we took a quick temperature check to determine how comfortable people were with this. The vote was split, with 4 of 7 committee members indicating they objected to the idea.
+
+### Concerns about Pause mode
+- Some members wanted to ensure that projects could continue even if we had to pause operations in the absence of leadership.
+- Some members were concerned that pausing operations completely would make it harder to restart once a new structure and leadership was in place.
+
+### Concerns about Lean Ops mode
+
+- Finding people willing to serve temporarily is likely to be as much of a challenge as finding election nominees.
+- There is a desire to appoint someone to at least sign the Code for America MOU (required to be a brigade), in order to hold onto the existing funds in our accounts (approx. $10k). This would need to be negotiated with Code for America.
+- One member was concerned about the lack of accountability if projects continued while brigade operations and oversight were paused.
+
+After a short period of breakout discussions, it was clear we needed more time to determine if Lean Ops mode was even a viable option (would we be able to find enough support even for those tasks?). We scheduled a follow-up emergency Steering Committee meeting for the following week.
+
+## Covering Lean Ops tasks
+
+The March 29 follow-up meeting was focused on sorting and assigning [operational tasks](https://docs.google.com/spreadsheets/d/11r1jlQmfpU4YQpnVYydcmRgaiJAmW8t33Ku5DHBjoPA/edit?usp=sharing):
+
+1. Outgoing co-leads shared a list of baseline operational tasks.
+2. Steering Committee reviewed them together and aligned on which were functional requirements, which were "lean," and which were "nice to have."
+3. Members volunteered to cover the tasks they were willing to take on.
+
+Ultimately, we determined that Steering Committee _would_ be able to temporarily manage a Leans Ops mode, particularly if we moved to a reduced meeting schedule. The biggest negatives we identified were:
+
+- Less frequent meetups.
+- Decreased support for member onboarding and project recruiting.
+- Less external communications, which reduces visibility and, potentially, accountability.
+
+### Tracking tasks and to-dos
+
+Jess introduced the [BrigadeOps GitHub repo](https://github.com/openoakland/BrigadeOps/) as a project management tool for staying on top of operational tasks and to-dos. This repo uses [GitHub Projects](https://github.com/openoakland/BrigadeOps/projects) to organize different tracks of work.
+
+- Everyone is encouraged to contribute by following the [ReadMe instructions](https://github.com/openoakland/BrigadeOps/) (which need to be fleshed out, along with workflows and other documentation).
+
+### BrigadeOps Handbook
+
+Jess has updated the [Brigade Ops Handbook](https://docs.google.com/document/d/1LwPiwXy7p9kOUK2Td9wrAPD4TTpCyjfWyMT5iF1j1BQ/edit#), adding more details around managing meetings, Code of Conduct, and communications channels, financials, and other how-tos. The plan is to move the Handbook into a more accessible format, such as an online guide using markdown.
+
+- Anyone can suggest changes or additions to the Handbook by commenting directly on the doc.
+
+## Putting Lean Ops mode to a membership vote
+
+**As a result of all this planning, instead of leadership elections we will hold a general membership vote in the coming weeks to determine whether or not we'll try to proceed with a Lean Ops mode. Stay tuned!**
+
+---
+
+### Other operational updates
+
+#### Potential speakers
+
+Jess has two speakers interested in sharing at an upcoming meetup:
+
+- **Program Coordinator for [Design for America](http://www.designforamerica.com):** Interested in sharing their approach to project scoping, which aligns with a lot of the discussion we've been having around project life cycle management.
+- **Organizer with [Community Ready Corps Allies and Accomplices](https://www.facebook.com/CRCAA/):** This white-run committee of the [CRC](http://www.crc4sd.org/), a Black-led liberation organization that actively builds & supports self determination, is interested in discussing the role of the local tech field in dismantling anti-Black racism.
+
+Because these speakers are not regular members, we would offer them our standard speaker honorarium for their time. A general member in attendance suggested that perhaps the honorarium should not be offered to potential partners. Jess pointed out that the policy currently extends to any non-regular member, and that changes can be introduced through a new proposal to the Steering Committee.
+
+Committee members were enthusiastic about inviting both members, but operational issues will need to be sorted out first.
+
+#### Comments wanted on new Community Commitments
+
+Felicia updated the team on the Embedding Equity group's recent work on a revised set of [Community Commitments](https://docs.google.com/presentation/d/1hQYjGxQqw5q68FcdAqvpSFlOR--soQY5VtB4lZqlbpo/edit?usp=sharing). Dismantling racism and inequity, and even basic collaboration, often requires difficult conversations that ask us to be vulnerable with each other. These community commitments outline the shared values and expectations we hold for ourselves and each other, so we can foster healthy, loving conversations that lead to better work and meaningful change.
+
+The Community Commitments were developed collaboratively during the Embedding Equity group's working sessions, and we would like to get wider input on them before proposing they be adopted and integrated into the Code of Conduct. Anyone (including members of the public) may provide feedback by adding comments directly to the doc, or by emailing Steering Committee at [steering@openoakland.org](mailto:steering@openoakland.org).
+
+#### Update on Code of Conduct consultation proposal
+
+OpenOakland was invited to participate in a pair of discovery meetings with a potential third-party consultant focusing on Code of Conduct review. Following these meetings, OpenOakland received a proposal for a scope of work that exceeds our total reserves. Co-leads recommended that Steering Committee members review the proposal and bring a proposal to Steering Committee if it wishes to pursue the engagement.
+
+---
+
+_Steering Committee meets the third Tuesday of each month and is open to all OpenOakland members. [Read more about how Steering Committee works](/how-we-work) and how to participate. Our next meeting is [April 19](https://www.meetup.com/OpenOakland/events/hmftrsydcfbtb/)._

src/_sass/main.scss

@@ -266,6 +266,17 @@ main {
   border: none;
 }
 
+.iframe-embed-doc {
+  top: 0;
+  left: 0;
+  bottom: 0;
+  right: 0;
+  width: 100%;
+  height:100%;
+  min-height:2000px;
+  border: none;
+}
+
 .responsiveCal {
  position: relative;
  padding-bottom: 75%;

src/about-us.md

@@ -18,7 +18,7 @@ OpenOakland bridges technology and community for a thriving and equitable Oaklan
     We recognize that Oakland has a rich history of activism. We seek to empower all Oaklanders to keep advocating for our community‘s collective well-being.
 
 
-## Part of the Code for America network
+## We're part of the Code for America network
 
 We're a fiscally-sponsored project of [Code for America](https://www.codeforamerica.org/), a 501(c)3 nonprofit dedicated to improving government in meaningful ways. [Donations to OpenOakland](https://www.codeforamerica.org/donate-to-a-brigade?utm_campaign=Open%20Oakland&utm_source=OpenOakland%20site) are tax-deductible through Code for America (be sure to select OpenOakland from the drop-down menu after choosing the amount).
 
@@ -29,21 +29,24 @@ We're a fiscally-sponsored project of [Code for America](https://www.codeforamer
 
 ## How we work
 
-Brigade membership is open to all, regardless of expertise or skill level. The brigade is led by a core team of elected leads. These are generally members who have been actively engaged in OpenOakland activities for an extended period of time. Activities and formal decision-making are overseen by a Steering Committee, which meets monthly and consists of the elected leads plus project representatives.
+Brigade membership is open to all, regardless of expertise or skill level. We work collaboratively, in the open, and strive to ensure those most impacted by our work are included in the decision-making that shapes it.
 
-[Governance Process](/how-we-work){: .btn .btn-primary }
+[Governance Process](/how-we-work){: .btn .btn-primary } [Brigade Bylaws](/bylaws){: .btn .btn-primary }
 
-### 2021 Co-leads
+### 2022 leadership team
 
-<!--- Section: Temporary Alert -->
-{% include home-sections/announcement-neutral.html %}
+The brigade is managed by a Steering Committee made up of one project representative from each project team, plus four co-leads elected by general membership. As of April 2022, we are revisiting our governance structure to explore how we can make participation easier, more effective, and more inclusive. We do not currently have any elected co-leads.
 
-{% include steering-committee.html %}
+Current Steering Committee members:
 
-If you're interested in joining the leadership team, join us for Hack Night and introduce yourself. In the interest of greater representation, our Communications Lead has committed to sharing or turning the role over if you're interested and identify as Black, Indigenous, or a person of color (reach out in #oo-steering-committee if interested).
+- John Baldo (rep, OpenOUSD)
+- Felicia Betancourt/Sean Martinez (alternating reps, Open Budget)
+- Elina Rubuliak (rep, Open Disclosure)
+- Jess Sand (rep, Funding Public Safety)
+- Niels Thorsen (rep, WOAQ)
+- Tom Theimer (rep, Councilmatic)
 
-
-## How you can get involved
+## Get involved
 
 - **Join us at Hack Night.**  
     Every Tuesday from 6:30-9:00pm PST, we meet on Zoom (normally, we meet in City Hall but are working remotely during the coronavirus pandemic). After intros on Zoom, we break off into Slack channels to work and you can bounce around to introduce yourself. Don't be shy about joining in; we're friendly folk. [RSVP on Meetup](https://www.meetup.com/OpenOakland/).
@@ -54,5 +57,4 @@ If you're interested in joining the leadership team, join us for Hack Night and
 - **Contribute to an existing project.**  
     Check out our [active projects](/projects/). You're welcome to contact project leads directly or jump into their Github repos but if you're not a coder or are unsure how you might contribute, we suggest attending Hack Night to get to know our project teams.
 
-
 **We hope to see you soon!**

src/bylaws.md

@@ -0,0 +1,11 @@
+---
+title: Brigade Bylaws
+date: 2022-04-03T12:00:23+00:00
+author: OpenOakland
+layout: page
+---
+
+OpenOakland's Bylaws outline the brigade structure, leadership roles, project requirements, decision-making processes, and additional brigade policies. OpenOakland's Steering Committee is expected to adhere to these Bylaws. However, they may be supplemented by non-binding policies and procedures documented elsewhere.
+
+
+{% include bylaws.html %}

src/calendar/calendar.md

@@ -7,8 +7,6 @@ permalink: /calendar/
 ---
 [Upcoming events](#upcoming-events) \| [Suggest a speaker](#suggest-a-speaker) \| [Past events](#past-events)
 
-<!--- Section: Temporary Alert -->
-{% include home-sections/announcement-neutral.html %}
 
 ## Join us every Tuesday on Zoom
 

src/how-we-work.md

@@ -15,8 +15,6 @@ OpenOakland subscribes to Code for America's [tenet](https://www.codeforamerica.
 
 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.
 
-<!--- Section: Temporary Alert -->
-{% include home-sections/announcement-neutral.html %}
 
 ![Bubble chart depicting the Steering Committee in a large circle containing the four elected leads; several project team circles overlap the steering committee circle and two Ombuds circles sit outside of Steering Committee.](/assets/images/OpenOakland-leadership-structure.png)