All of cod3d's Comments + Replies

There are a few things that sound similar to what you're talking about. The first is the process of writing an RFC: https://github.com/inasafe/inasafe/wiki/How-to-write-an-RFC. Also wikipedia must need to do many of the things you describe, so looking into how they reach consensus may be interesting for you.  Also, there are attempts to have more of a direct democracy style governance in the US, and they have certain procedures that you may want to look into: https://www.newyorker.com/news/the-future-of-democracy/politics-without-politicians I do like the idea of templates for certain types of discussion. That's why I wrote this: https://www.lesswrong.com/posts/xE7F4b34pfTMThYMX/what-questions-should-we-ask-ourselves-when-trying-to.    It's not easy for me to understand how strong of a claim you're making here, because you say "depending on the topic" and "almost." It still feels too strong to me. I'd say most of the time, at best, templates for discussion would just be helpful. Especially if people have different values and beliefs about the world, disagreements are very difficult to settle. I suppose questions in mathematics or something where you can prove an answer is correct may be a type of exception. Check out the polymath project if you haven't seen it already for an example of people collaborating on trying to solve (math) problems. I have a lot of similar ideas to the ones you've presented in this post, so if you'd like to discuss these things anytime, feel free to send me a dm.  

Using version control for law making doesn't change much about citizens ability to suggest changes for laws. What it does do is that it makes it easier to track who proposed a change. If a lobbyist for example sends a congressman a pull request for a law it's a lot easier to understand and track how the law came about. Version control increases transparency and it also has the prospect of making law making more efficient as it's easier to keep track of amendments that way then by mailing Word documents around which is the status quo.  The process of how the law was changed in that instance isn't any different then how you can change the code of an Open Source project. I know of no open source project that's using version control for the discussions about what changes to make and having discussion to find consensus.  Instead of looking at version control it would make more sense to look at software that's actually designed for consensus finding. Various liquid democracy software provides for consensus processes. Taiwan's e-government initiative is also worth checking out.  Here's it's worth noting that judgement and critique is not the necessarily the rational way to come to consensus. If you look at the processes CFAR developed seeking to understand another, identify cruxes and explaining why you hold your position can be a lot better.

It is irrigation actually, not moisture sensors. Or rather, I think it irrigates based on the level of moisture, using a combination of tiny tubes and clay spikes that I admittedly don't fully understand. (It seems to be much better at watering my plants than I am, even ignoring time costs!) I do have to fill up the water container sometimes.

Welcome!