|
|
@@ -14,6 +14,8 @@ Whether your community is already up and running or still just an ambition, choo
|
|
|
|
|
|
**If you use the modules, be sure to explain what they mean.** When you add a module or click on its name, a field appears that allows you to describe the module in your own words. Text typed there automatically becomes part of the module, and it will appear when you hover the cursor over its name.
|
|
|
|
|
|
+**Add configurations to your modules.** Using the + and - buttons, and the fields alongside them, specify details about how the modules work---for instance, the threshold of votes for a proposal to pass, or the duration of a process. These help you get even more specific about a given module.
|
|
|
+
|
|
|
**Separate the Rule from its data**. Think of your Rule like a constitution as opposed to a code of laws, like a building as opposed to the people who put it to use. Don't try to include all your community's policies in your Rule; explain there how you make and change policies. Don't list out who holds what roles; just define the roles. In your Rule, make clear where people can find that data---the policies, the role-holders, and so forth.
|
|
|
|
|
|
**Read and re-read.** Be sure that all the terminology and processes are consistent. Inevitably there will be loopholes and bugs, but try to resolve as many of them as you can. The "Preview" button provides a clean display for easy reading. Just press "Customize" when you're ready to edit again. Show it to your community for feedback.
|
Nathan Schneider