CommunityRule-archival/_about/faq.md

---

layout: page title: Frequently Asked Questions

permalink: /about/faq/

How does CommunityRule relate to codes of conduct (like the Contributor Covenant) or licesnses (like Creative Commons)?

CommunityRule is focused on an often-missing component in online communities: the governance layer. Typically communities inherit the "implicit feudalism" of the underlying software, which usually centers around an all-powerful administrator. Codes of conduct, the implementation of them, and other features of the community rest on that underlying governance logic. Here is one way of picturing a community "stack":

The purpose of CommunityRule is to make it easier for communities to efficiently replace the default feudalism with a more appropriate and accountable governance system, or Rule. Communities can then use their preferred Rule to fill in other layers of the stack through an explicit process.

What kinds of projects do you take inspiration from?

A bunch of stuff, including but not limited to these:

• Codes of conduct
  • Contributor Covenant
• Community toolkits
  • Loomio Community Group
  • Prototyping Work (see decision-making and structure
  • Virtual Communities for Impact
• Incorporation tools
  • One Click Orgs
• Licensing tools
  • Creative Commons
  • License Zero
  • Polyform Project
• Metagovernance Project
  • "Admins, Mods, and Benevolent Dictators for Life"
  • "Modular Politics"
• Model communities
  • Social.coop bylaws
• Monastic rules
  • Rule of St. Augustine
  • Rule of St. Benedict
  • Rule of St. Clare
  • unMonastery BIOS
• Software communities
  • Apache
  • Debian
  • Python
  • Wikipedia

What's the current project roadmap?

Funny you mention it. Right here:

• Rules (ready-to-deploy presets)
  • Brand preset rules as CommunityRule rules with tools to create badges out of them
• Javascript output button
• Less textual, more visual header for Rule pages
• Further modularity
  • Aim for a logic of progressive disclosure, making templates really simple but facilitating more complex iteration
  • In _modules, develop pseudocode primitives and complex modules with inputs, outputs, and actions
• Compatibility with Loomio?
  • Translate each module into Loomio practices, implicitly or explicitly (e.g., time for a proposal, threshold, voting options)
• Module system with database
  • JavaScript pulling from GDocs?
  • Use Jekyll yaml in _data/ to create modules
  • Jekyll csv data pull? https://jekyllrb.com/docs/datafiles/