- abotest 2017/04/14 20:36
Dies ist eine alte Version des Dokuments!
Autor: Daniel Pätzold
Der Beginn: Diese Idee kam mir am 16.09.2018
Kurzfassung der Idee: Github und ein zusätzliches System zur Konsensierung wird zur Erstellung von Abstimmungen und Prozessen genutzt. Die Entwicklung selbst wir auf Github vorgenommen, deshalb erfolgt die geneuere Detailabstimmung dort.
Erster Entwurf auf englisch hier:
Over the years, Github has proven as very efficient and powerful Tool for developing Applications in all ways that programs are build. It offers the ability for everyone in any project to contribute its own sourcecode, without messing up other users work and and to have good work merged into final applications in an easy way.
That way, big applications have evolved, outscaling conservative programs in a considerable degree.
Unfortunatelly, as of now, all those good benefits of github are starting at the point where sourcecode is written and improved. (Except of „Issues“, which are pointing in the right direction.)
But programming starts much earylier: When there are many people involved and working together in groups for projects, the process is beginning with an idea of what to do (change or invent new). Most Members of those Groups do not have developing Backgrounds, but their ideas may be very inspiring for Developers and the project may strongly benefit from those ideas.
So when discussing those ideas, basically a „github thing“ happens in the minds of each individual:
Starting from the existing situation (master-branch), each one proposes its own point of few as idea. This could be called „idea-fork“, as they base on the actual situation and suggest what to change to improve it.
While the discussion is evolving, some idea-forks may combine to an aggregated idea, some forks may split from others when there are oppositional, competing against the other ideas.
At the end of that discussion, all forks will be reviewd (code compare) and rated - maybe by the group or by a leading member.
So the best rated „idea-fork“ will be „merged“ to the old process. Everyone would now know, what to archive.
Now, programming can start in an structured way.
So my proposal is, to extend github to support „idea-forking“, which could be used for all larger descissions even in private, or having non- programming background to evolve existing situations.
There are some differences in „idea-forks“ to current „program-forks“, as of
At first, the
Often People are in need to find Solutions for
Differences between programms and ideas: - ideas may not „work“, they are not technical. It will not be the goal of this project, to deliver working ideas as programs are (do they compile ;)?). If they do prove as bad, they can be changed starting with a new „fork“ -