Has anyone looked at codifying community control of communities before?
Has anyone looked at codifying community control of communities before?
Hello all, I am just curious if anyone has taken a tool like community rule to define how their instance or community control is handled? Even more so if there has been any effort to make the actual decision-making actionable by the system.
I'm sure it's been tried, but we know by now that anything that is codified gets gamed. You just have to act sensibly, and accept that if a big enough division of opinion on something occurs, the community will fork. That is a natural step of evolution and not something to get upset about.
I read the about and still don't understand what it is or how it tries to accomplish what it's doing. I run a couple communities, I'd be interested in making a structure, but I have no idea what this tool is
It seems to be a no code markdown editor for creating a community high-level description and key aspects. The lack of what to do next with that is bothering me at least personally. I feel like there is some step of taking this a actually plugging in proccess and people that is missing.
I personally, at the moment, just see it as a nice way to make a strategic choice what you WANT a community to be. With the rest of something left as a to-do kind defined by the strategic requirements.
This is a bit of a tangent, but I think there should be options for the type of community you set up. One kind is the traditional, moderator-controlled community. Another kind could be a more democratic community where members have more power (and responsibilities).
That's kind of what I am going for!
I had some rough work but haven't gotten around to posting for feedback. I might be misunderstanding it, but my thing was a "best practices" thing for communities and instances.
Planning to finish it up soon
I'd love to see your work when you're ready!