Added to FAQ

_about/faq.md

@@ -4,6 +4,14 @@ title: Frequently Asked Questions
 permalink: /about/faq/
 ---
 
+**Can I help contribute to improving this project?**
+
+Absolutely, please do. The best way to start is to contribute bug reports and feature requests through the [Issues system on GitLab](https://gitlab.com/medlabboulder/communityrule/-/issues) (no programming required!). You can also submit code directly there if you're into that.
+
+**Okay, my community has designed its Rule. What tools do we use to implement and enforce it?**
+
+CommunityRule can't help with that. It depends a lot on what would be best for your group. If you're looking for a platform to use, [Loomio](https://loomio.org) pairs very well with a simple Rule created here. CommunityRule is also part of a broader effort, the [Metagovernance Project](https://metagov.org), which seeks to create a robust set of tools for online governance. In the meantime, good governance online tends to require some clever improvisation.
+
 **How does CommunityRule relate to codes of conduct or license agreements?**
 
 CommunityRule is focused on an often-missing component in online communities: the governance layer. Typically communities inherit the "[implicit feudalism](https://ntnsndr.in/implicit-feudalism)" of the underlying software, which usually centers around an all-powerful administrator. Codes of conduct (like the [Contributor Covenant](https://www.contributor-covenant.org/)), license agreements (like [Creative Commons](https://creativecommons.org/)), and other features of a community rest on that underlying governance logic. Here is one way of picturing a community "stack":