I'm interested in a system that allows distributed development with a part of authentication. What I mean?
So, let's take SVN, SVN keeps track of changes and does not care about who submits, as long as you have the right to submit, you can actually send any part to the repository. Where does my system come into play? The ability to granulate access control and provide stackoverflow overflow as a sense of the environment.
In the system that I am describing, we have 4 users Bob, Alice, Dan, Joe. Bob is a managed project, Alice and Dan are programmers under Bob, and Joe is an occasional programmer on the Internet who wants to help. Ideally, in this system, Bob can make any changes and does not require approval. Alice and Dan can make branches or branches, but Bob requires the approval of the chest. This is where Joe comes in, wants to help, however, you just don’t want to give him the keys to the kingdom, but say so for now, so on my system you set up a low-user account. Any commits Joe makes must be approved by Dan, Alice, or both. However, in the system, Joe can create Karma, where after so many approved commits it will only be the approval of one of the programmers, and then, ultimately,there will be no need for approval.
It makes sense, and do you know if such a system exists? Or am I just crazy to even think that such a system / environment would be possible?
source
share