Dear vincent
FGMEMBERs is all about open model 2 as well
Every developer should in principle fork the repository and create a "protected" territory, where only he and the one group of people he chooses can write directly. (Not that they need to, since anyone that is a FGMEMBER could work over the FGMEMBERS repository directly too!)
[Added message:
You can see that several of our aircraft have branches that are specifically designed to maintain a separate authors intent, more specifically when changes on the aircraft come as a disagreement with his view, or there are alternative views.
A topic branch is "reserved" for such maintainer.
And such topic branch is "commited to be" exactly what that maintainer is willing to make of it
]
The second phase is to submit the "private fork" modifications to the FGMEMBERs fork. This way allowing all others to co-create. (Some developers (at least 1 directly to me ) had indicated their complete disregard for what FGMEMBERs can provide, and had decided that they will not be attempting doing pushes to the FGMEMBERs repository, too)
It is true that a growing number of contributors can modify and submit pull request over the FGMEMBERS repository. And thus, it is a matter of development processes for the different developers of any given aircraft to maintain and enhance this FGMEMBERS repository.
Open 2 method does not mean to assign an aircraft maintainer that holds the last voice on where an aircraft goes. FGMEMBERs repository remaining the space where different voices and perspective coexist, breed, co-create.
When a developer closes all possible intention to accept other's ability to commit to a given aircraft, and are unwilling to co-create, on the principle that anything different is just a breakage, and are unwilling to look for those commits, and determine what is good on them and what is bad on them, unwilling to establish peer-2-peer contact with other people interested in the same airplane in the name of 'quality', and prefer to look for isolation, when they, in their greatness complex do not even consider the possibility that looking up for a common-property repository is a great approach to foster cooperations, and even teach the next generations of aircraft developers. At that moment, I say, that is when I start loosing all hope.
Sincerely
IH-COL