c-base / circle

circle protocol app
2 stars 0 forks source link

How should we handle ruling? #9

Open baccenfutter opened 9 years ago

baccenfutter commented 9 years ago

Sorry for doing this, but we will have to discuss this matter eventually, so why not now as the participation list is still rather compact.

The circle makes rules - how should we go about and handle these?

After a long time of thorough thinking, I've come to the conclusion that we shouldn't handle them at all and instead keep our focus on the decision-making process rather than the abstract outcomes of these decisions, such as rules.

I'd like to see some up-votes or down-votes on this or perhaps even a more brilliant idea.

cmile commented 9 years ago

:+1:

XenGi commented 9 years ago

When a rule is formed at circle meetings it should be accessible in the app. We try to work on a wiki page with the basic rules of c-base and a 2nd list with all circle rules would be nice to, because new members don't read the mail archives and so don't know about circle rules before their membership. So if you could implement an interface to get all circle lines that contain rules we could simply build a small script that generates an updated wiki page out of that. Shouldn't be that complicated because there will be a voting system in the app to define a decision and that's a rule then. maybe we can mark them as important so that they land on the wiki page or not if they are only important for a short period of time. i. e. for an event etc. Something like "From now on c-base is smoke free" should be marked important and land on the wiki page.

baccenfutter commented 9 years ago

There are several implications with your request:

1) Considering the very small number of rules we have, it would take an abnormous amount of effort and time to write (and maintain!) a wiki-glue-script compared to just writing the few rules into a wiki and then maintaining them there.

2) You've confused how the voting-system is defined by RFC. Votings are NOT rules! They are decisions - a decision isn't always consequently a rule. Imagine an alien requesting us for an event location. If the circle decides that c-base would like to host the event, this DOES NOT consequently result in a rule that this alient can use the c-base as event location.

3) You are underestimating the effort of establishing rules. Rules are not static. It's not like somebody comes up with a good rule, makes it and we're done with it. In a healthy political environment, rules need to be questionable and discussable. They require formally well defined processes for how rules are established, questioned, reviewed and revised. No wiki-glue-script in the world will be able to handle all edge-cases. Neither will the circle-app.

This is the reason, for our high doubts about rule-making within the circle-app and why we are trying to get around it - at least until somebody comes up with a brilliant idea. No offense, but your idea doesn't have quite the level of brilliance we are hoping for.

4) The circle-app is a tool that aims on brilliantly integrating and implementing the entire real-life process of the circle event. The circle-app doesn't define how the circle should work - the circle defines how the circle-app needs to work. Thus, the circle should develop a formal protocol on rule-making and we will be happy to implement this real-life feature into the app.

XenGi commented 9 years ago

Good point. Than let us analyse the rulemaking process first.