Please note: This is an attempt to summarise and reflect the most recent state of the board and its responsibilities, replacing this outdated document. Comments, questions and PRs to this document are welcome.
ClojureBridge is a non-profit organization formed primarily to:
-
Provide free, beginner-friendly workshops to teach women and other under-represented groups to program in Clojure.
-
Welcome gender minorities and other under-represented groups to the Clojure community. Support, encourage, and celebrate their ongoing contributions to the Clojure ecosystem.
-
Support and provide expertise and resources to new and existing ClojureBridge chapters across many cities worldwide.
-
Build empathy and training skills within the Clojure community.
ClojureBridge is a subsidiary of Bridge Foundry, which is fiscally sponsored by the School Factory umbrella organization.
We expect everyone involved with ClojureBridge to follow the Bridge Foundry Code of Conduct.
Bridget Hillyer and Sean Corfield have written blog posts about the origins of ClojureBridge.
ClojureBridge is a non-hierarchical, decentralized organization full of volunteers who want to make tech better. Everything we do is open source and replicable by volunteers.
The board currently meet remotely, on a quarterly cadence, to discuss and action:
-
New chapter mentorship: walking them through the organizers' documentation and answering questions;
-
Community Outreach & Support: triage and respond to enquiries via:
- [email protected] inbox
- ClojureBridge, ClojureBridge Workshops, & ClojureBridge Alumni Google groups
- Twitter and any other social media accounts
- Mentorship requests via Github Issue
-
Curriculum: Maintain the master curriculum & community docs, including handling pull requests.
-
Web Site & Technical Infrastructure: maintenance and ad-hoc updates to the ClojureBridge website, newsletter and social media accounts.
The typical board rotation is around 12-18 months. ClojureBridge board members may leave anytime any time after an ideal minimum term of one year. The Board should coordinate the term dates of their memberships so that all members of a team don’t change at once.
Members can serve multiple consecutive terms, but we prefer that not be the norm. We want to prevent burnout, cultivate new leaders, and foster a resilient leadership structure. Having the same folks serve in the same positions ad nauseum doesn’t do that.
Financial details, including non-profit status and our relationship to Bridge Foundry, is in this separate document:
The contents of this document will be reviewed and revised, if necessary, by the Board and all Teams twice a year.
-
Railsbridge and Bridge Foundry raisons d’etre
-
The (now deleted) original draft of this document
-
Lynn Grogan’s research on open source foundations
-
Sarah Allen’s blog post about RailsBridge and resilient leadership patterns
-
The Apache Software Foundation: How the ASF Works
-
The conflict resolution patterns section of the Hackerspaces wiki
-
Wikipedia article on consensus-based decision making