377 lines
20 KiB
JSON
377 lines
20 KiB
JSON
{
|
|
"_comment": "Guide to CommunityRule on /how-it-works. Banner, byline, sections, figures and closing buttons follow the Figma Content page Template frame.",
|
|
"banner": {
|
|
"title": "When your community sits down to write its Rule",
|
|
"description": "Sketch your Rule in CommunityRule, then make it your community's own over five short meetings.",
|
|
"author": "CommunityRule Creative Team",
|
|
"date": "2027-02-18"
|
|
},
|
|
"byline": {
|
|
"template": "By {author}. {date}. {minutes} minute read. ",
|
|
"beforeYouStart": "Before you start"
|
|
},
|
|
"relatedArticles": {
|
|
"title": "Related articles"
|
|
},
|
|
"relatedSlugs": [
|
|
"resolving-active-conflicts",
|
|
"operational-security-mutual-aid",
|
|
"making-decisions-without-hierarchy"
|
|
],
|
|
"teamRule": {
|
|
"title": "CommunityRule Creative Team",
|
|
"description": "We build and maintain CommunityRule for the communities that use it. It is free for every community that wants to write down how it decides.",
|
|
"caption": "The CommunityRule Creative Team's Rule on one page with its five parts labeled.",
|
|
"categories": {
|
|
"values": {
|
|
"name": "Values",
|
|
"chips": [
|
|
"Transparency",
|
|
"Forkability",
|
|
"Documentation",
|
|
"Maintenance",
|
|
"Voluntarism"
|
|
]
|
|
},
|
|
"communication": {
|
|
"name": "Communication",
|
|
"chips": [
|
|
"GitHub / GitLab",
|
|
"Matrix / Element",
|
|
"Email distribution list",
|
|
"How we run meetings"
|
|
]
|
|
},
|
|
"membership": {
|
|
"name": "Membership",
|
|
"chips": ["Join by contributing", "Companions"]
|
|
},
|
|
"decisionMaking": {
|
|
"name": "Decision-making",
|
|
"chips": [
|
|
"Consensus decision-making",
|
|
"Lazy consensus",
|
|
"Do-ocracy",
|
|
"Changing this Rule"
|
|
]
|
|
},
|
|
"conflictManagement": {
|
|
"name": "Conflict management",
|
|
"chips": ["Conflict ladder", "Hearing panel", "Restorative practices"]
|
|
}
|
|
}
|
|
},
|
|
"share": {
|
|
"send": "Send this to your community",
|
|
"copyWiki": "Copy into your wiki",
|
|
"print": "Print the card",
|
|
"copiedTitle": "Copied to clipboard",
|
|
"copyFailedTitle": "Could not copy"
|
|
},
|
|
"closing": {
|
|
"createRule": "Create rule",
|
|
"createRuleHref": "/create/informational",
|
|
"downloadKit": "Download the kit",
|
|
"downloadKitHref": "/kit"
|
|
},
|
|
"sections": [
|
|
{
|
|
"id": "what-you-will-have-by-the-end",
|
|
"heading": "What you will have by the end",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "A Rule is a short document your community can read aloud in a few minutes. [Confirm how long a typical Rule runs.] It has five parts. The first part names what your community values and the plain signs that a value is slipping. CommunityRule calls those signs signals of violation. The other four parts say how you talk, who belongs, how you decide and what happens when you disagree. Every community has answers to those four already, written or not."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "Here is ours. The CommunityRule Creative Team, the people who build CommunityRule, adopted its own Rule on 30 October 2026. One of its values is Documentation, which pulls against speed. One sign it is slipping is that only one person knows how to deploy. Whoever does the work decides a small change, and anything bigger is approved after 72 hours with no objection."
|
|
},
|
|
{
|
|
"type": "ruleFigure"
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "Nobody starts from a blank page. CommunityRule puts cards in front of your community, drawn from a deck of hundreds, and each card is one way to answer a question. A card is a starting text. Your community can rewrite its words or write a card of its own."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "CommunityRule comes from the Media Economies Design Lab at the University of Colorado Boulder and it is free for every community."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "A Rule is an agreement between people and it sits beside your bylaws if you have them. [One line for co-ops on what to do when practice and bylaws differ.]"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "what-a-rule-costs",
|
|
"heading": "What a Rule costs",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "A Rule costs five short meetings and at least one real argument. It also costs somebody some quiet power. Somebody has been making decisions the community never handed them and a Rule takes those back. That person will feel it and it may be you."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "A Rule needs upkeep too. Leave it alone and your community has hidden rules again plus a document that says something else."
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "before-you-start",
|
|
"heading": "Before you start",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "Your community settles five things before anyone sketches. Any member can raise them."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Check that your community is not in the middle of a dispute.",
|
|
"text": "A community in a dispute cannot write fair rules. Everyone is arguing about an outcome and a Rule is about method. Write it after the dispute and start with [the conflict guide's title] for now."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Choose whose email goes in.",
|
|
"text": "The tool keeps your place in one browser until someone adds an email. That email becomes the login and only that login can change the Rule later. Use your community's shared inbox if it has one. The Rule stays with whichever email logs in, and deleting that account deletes the Rule. If your community has no shared inbox, choose the person on purpose."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Decide where to start.",
|
|
"text": "Your community can pick card by card, start from one of the thirteen templates or start from a copy of a Rule another community shared with you. On a template's page choose Customize, which shows the template's cards question by question so your community can change what does not fit. The other button, Use without changes, skips the cards. Changing a template is how a community finds out where it differs."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Find what is already written.",
|
|
"text": "Bring your bylaws or the pinned message in your chat to the first meeting. The screens take a logo or a photo and no documents, so keep them on the table beside the sketch."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Decide what stays out.",
|
|
"text": "Leave out rosters, meeting places and legal names if your community's work puts people at risk. Every Rule starts private. Only the people you invite can read it until the person who holds the pen turns on a link. A Rule is public and featured only when a group asks us in writing. [Say who can see a draft and an upload and whether a group can delete them.]"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "sketch-it-in-communityrule",
|
|
"heading": "Sketch it in CommunityRule",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "The screens are the quick part. One or two people can sketch a whole Rule in one sitting, and nothing is shared until you invite people. [Confirm by timing a sketch through the screens.] Answer for the community you are today and pick what is closest to what you do now. The meetings are where your community decides whether to keep it."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "1. Say who you are.",
|
|
"text": "The first screens ask your community's name, what it does, its kind, how far it reaches, how established it is and how many people have a say in its big decisions. A short screen of yes or no questions follows, such as whether you pay anyone for the work. The answers sort the cards and are never published."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "2. Add a logo and save your progress.",
|
|
"text": "Add your community's logo or a photo, or skip it. Then add the email your community chose. A login link goes to that address so you can come back to the sketch."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "3. Name your values.",
|
|
"text": "Pick the values your community already lives by, up to six, or skip them for now and add them later. Each value asks what it means to your community and how you will know you are not living up to it. The second answer is your signals of violation. Keep a value only if your community can say what breaking it looks like."
|
|
},
|
|
{
|
|
"type": "figure",
|
|
"src": "value-dialog",
|
|
"caption": "A value in CommunityRule with one row for what it means and one for the signs it is slipping."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "The four questions come next, each on its own screen of cards. They run how you talk, who belongs, how you decide and what happens when you disagree. The cards suggested for a community like yours come first, tagged Recommended. See all shows the rest with a search, and no card is hidden. Open a card to read the whole policy and change its words. Each question needs at least one card before you move on, and your community can pick more than one."
|
|
},
|
|
{
|
|
"type": "figure",
|
|
"src": "decisions-deck",
|
|
"caption": "A screen of cards for how you decide with the suggested cards tagged Recommended."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "4. Say how you talk.",
|
|
"text": "Start with where your community really makes its decisions. Say so if that is the group chat. One card is Signal. Your community coordinates in encrypted Signal groups with messages that disappear on a timer. Another is Code of conduct. One code covers how members treat each other in every channel, meeting and space."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "5. Say who belongs.",
|
|
"text": "The cards cover who can join, how they join and what the community asks of a member. One card is Open admission. Anyone who agrees to follow your Rule can join and start on the work the same day. Another is Vouching. Two members who know someone in person vouch for them before they join. Pick the card closest to what your community did the last time someone asked to join. Leave and return lets a member step back for up to six months and come back without starting over."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "6. Say how you decide.",
|
|
"text": "This question has the most cards. A vote on every small thing stalls a community. One person changing a big thing breaks trust. So pick one card for everyday calls and one for decisions that touch everyone. One card is Do-ocracy. Whoever does the work decides how it gets done. Another is Supermajority rule. A proposal passes only when your community's supermajority share of the active members who vote says yes, such as three quarters. Stop reading cards when one sounds like your last meeting."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "7. Say what happens when you disagree.",
|
|
"text": "One card is Conflict ladder. The two people talk first, then each brings a friend to negotiate, and the people your community names step in last. Another is Conflict working group. Two to five members named in advance hear what the first steps could not settle and propose a plan the members approve. Pick now while nobody is angry."
|
|
},
|
|
{
|
|
"type": "figure",
|
|
"src": "final-review",
|
|
"caption": "Final review in CommunityRule with the Rule as one card and a chip for each part."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "8. Read it through.",
|
|
"text": "This screen shows your Rule as one card with a chip for each card and value. Open a chip to change its words or use a section's add chip to pick another card. A question with no card and a card with no words are flagged. Fix each flag before you go on."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "9. Invite people or finish.",
|
|
"text": "Enter an email for each person who should read the Rule, or paste a list. Ask before you add anyone. Each person gets a private link by email and can read the Rule. Only the login your community chose can change it. The Rule and its exports never show names. While the Rule is still a sketch choose Finish without inviting. You can invite everyone from your profile at the last meeting."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "10. Finish.",
|
|
"text": "Your community has a sketch of its Rule. Rules stay private until you share them. Print it or save it as a PDF for the first meeting. A RULE.md file is there for a repo. To change it later, whoever holds the login opens Edit and goes back to the final review."
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "turn-the-sketch-into-your-rule",
|
|
"heading": "Turn the sketch into your Rule",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "A sketch is not a Rule until your community has argued with it. The kit spreads that argument over five short meetings, each inside a meeting you already hold, and any member can run it. The kit is free for volunteer-run groups and it lives at [communityrule.info/kit](/kit)."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "Before the first meeting book all five and choose who takes the three roles. The facilitator keeps the room on the question and speaks last. The scribe types only what the room agreed and reads it back. The timekeeper calls time. The roles rotate each meeting. Ask everyone to bring one question your community has never asked out loud. Print the worksheets, or use the kit's online board if you meet on a call. Paper is safer for a community whose work puts people at risk."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "Every meeting opens the same way. Someone reads aloud the kit's short rule for how the room decides, before the first proposal. Every meeting closes the same way too. In the last 10 minutes the scribe enters what the room agreed, logged in with the address your community chose, while everyone checks the wording. Nothing else goes into CommunityRule."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Meeting 1, 60 minutes.",
|
|
"text": "Everyone writes one question your community has never asked out loud, without a name, and the facilitator reads them all. Sort them under the four questions and start with the one that has the most. Spend the rest of the meeting on it. Say how it works now, read what your sketch says and agree what you can."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Meetings 2 to 4, 45 minutes each.",
|
|
"text": "Take one question each, in whatever order your community chooses. Read back what you agreed last time. Then say how it works now, read what the sketch says and what else you could try and agree what you can. Have more time? Take two questions in one 90-minute meeting."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Meeting 5, 45 minutes.",
|
|
"text": "Start with values while the room is fresh. For each one say what it looks like when it is slipping. Then someone who wrote the least reads the whole draft aloud. Fix anything that sounds wrong while everyone is there. Agree how the draft reaches every member and when objections close."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Send it out.",
|
|
"text": "Nothing counts until every member has seen the draft and had time to object. Invite every member from your profile so each gets a private link, and send the draft wherever members actually read, not only the main chat. Objections close the day before your next regular meeting, with at least seven days to respond. That meeting decides any objections the way the draft says. If nobody objects in time the Rule counts. Write down the date it took effect."
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "when-your-community-gets-stuck",
|
|
"heading": "When your community gets stuck",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "Most meetings stall in one of a few ways and each has a short fix."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Your community splits on a card.",
|
|
"text": "This is the argument the meetings are for. It costs less now than in the middle of a dispute. Ask what the community did the last time it came up and pick that card. Give the other card a meeting of its own."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Nobody knows the answer.",
|
|
"text": "Then nobody decided and somebody has been handling it anyway. Ask who dealt with it last time and pick the card closest to what they did. Then ask the community whether to keep doing it that way. Anything your community does not settle can wait and you can add it to your Rule later."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Time runs out.",
|
|
"text": "Agree what you can, park the rest with a date and keep the full 10 minutes for the close."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "One or two people do all the talking.",
|
|
"text": "Go around the room once before opening it up. The facilitator speaks last."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "The room starts reliving an old conflict.",
|
|
"text": "Bring it back to method. Ask what you would want the Rule to say next time."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Only a few people come.",
|
|
"text": "Go ahead. Sending the draft out is how everyone else gets a say."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "Still stuck?",
|
|
"text": "Send your question through [Ask an organizer](#ask-organizer). A person will write back within two working days. You can also bring your draft to office hours. The times are at [communityrule.info/kit](/kit)."
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "after-it-counts",
|
|
"heading": "After it counts",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"lead": "1. Put it where the next new member will find it.",
|
|
"text": "That could be the doc new members read or the wall where you meet."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "2. Use it once on purpose.",
|
|
"text": "Open the Rule the next time a decision comes up. Do what it says."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "3. Set a date to read it again.",
|
|
"text": "Read the signals aloud and ask whether anyone has seen one. Change the Rule if someone has."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"lead": "4. Tell us what it changed.",
|
|
"text": "Write to us through [Ask an organizer](#ask-organizer)."
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "what-we-are-not-sure-about",
|
|
"heading": "What we are not sure about",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "We are the lab and the organizers working with it. We rebuilt CommunityRule because of what we learned about the earlier version. Early versions confused people. Many struggled to understand the modules, find the right ones and customize them. Uptake was slow. Many people tried the editor, often alone or in a workshop, and few groups are known to have adopted a Rule and kept it."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "Andy DiLallo rebuilt the tool around what we learned. We think the meetings are the rest of the fix, because a community that argued over its Rule is more likely to keep it. We cannot show that yet."
|
|
},
|
|
{
|
|
"type": "p",
|
|
"text": "Tell us how yours went. The form is called [Ask an organizer](#ask-organizer)."
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "updates-from-groups",
|
|
"heading": "Updates from groups",
|
|
"blocks": [
|
|
{
|
|
"type": "p",
|
|
"text": "[Dated entries from groups. Empty at launch.]"
|
|
},
|
|
{
|
|
"type": "shareRow"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|