I am a bit surprised that you had not decided to join the organization.
(i did sent you a github invitation that you had not accepted)
But in spite of, you had been recently so vocallly critical of what I do or dont do with FGMEMBERs. Basically questioning every step I take.
I can't understand what is that coming from. Since as an outsider, you still don't understand the "mechanics" of how we operate, and thus it seem awkard that you are posting "how you think we should do"
In the case of the reversal of the commit of the liveries.
I am ok with making a branch for you to take a plane with no liveries, phil. But keep in mind I am not an employee of yours.
I can do that for you as a favor, but nothing prevents you from forking an aircraft, revert the commit, and take the zip from your own fork. And at least the basic ethics and respect should prevent you to command me to do the job for you.
I am ok with showing you a solution to your problem with the liveries. And also ok with creating a branch for you in FGMEMBERS. But I would appreciate much more if instead of volunteer with venomous critiques, if you join the "organization" and provide some aircraft maintenance, and make branches you require too. Specially since you are a knowledgeful git user --which I am not
In the case of forcing pull requests instead of allowing writting access to FGMEMBERS. Non-sense. It would defeat the whole purpose of FGMEMBERS. That being, foster cooperative development. If everyone can write to the repo (the FGMEMBERS one) that puts us all in the same level of creative minds, with equal capabilities. Forking is allowed, and encouraged, for other technical reasons. But on my watch, there will not be limitations upon when/where/what to write by any FGMEMBER.
If you want limitations, luckily, the alternative exists. And it is call FGADdon.
When an user forks any repo in github. The resulting fork is "owned" by who forks. And such, he/she decides his own limited collaborators, and decides the commits and pull requests he wants there. In that case, it exits my domain. FGMEMBER is the community domain. And I strongly oppose anyone taking "ownership" over a given branch.
If you want a protected castle. Fork and send pull requests.
If you are a gregarious monster, choose yourself. Fork or write directly (onto the master branch)
A few topic branchs may be reserved to follow other people's forks.
Most importantly, FGMEMBERs is not what you think it is. Not it will be. FGMEMBERs is not a collection for others to pull, and a few to keep their personal "maintained" aircraft.
FGMEMBERS are repositories with aircrafts where the complete community can write into, pull to and pull from, at wish.
Whomever wants to take planes for us, it is free to do it. Whomever does not want, it is free to do it as well.
And that is the case of the liveries.
I decided I wanted to transfer them. Why do you intend to stop me, or create an argument about it, about gatekeepers? No-one can gate keep me from introducing them. Nor I will gate keep anyone from the same.
Inclussion. Not exclussion. That's the moto.
If I were to prevent making changes because it does not suit you, or suit other, or because someone like Helijah or HerbyW cryes amok, then FGMEMBERS need not to exist. It exist, because there, ANYONE can cooperate, and send the commit that person agrees important. If you have a different perspective of a plane, feel free to make it, and allow us to copy that as well.
==as you can see, so far you have no idea what FGMEMBERs is about==
And it will not change because you don't get it, either.
About HerbyW.
Yes. I did pull a request over his zone in github.
I did not "COPY or PUSH directly" as you venomously indicated. I send pull requests!
See
https://github.com/HerbyW/Antonov-An-12 ... 0c6a380f35
https://github.com/HerbyW/Antonov-An-22 ... be3e4d8518
https://github.com/HerbyW/AN-225/commit ... 2336e02a65
https://github.com/HerbyW/shuttle/commi ... a121557af8
They are ALL pull requests to his forks.
The point is I merged them myself! Why? because HerbyW had me added as a collaborator to his fork.
He may had done that unintendenly, but having me as a collaborator implied to me he was OK with me doing so.
He send me an email saying he is not ok. I send him an email saying how he can remove me from the collaborator's list. I apologize, too, because I misinterpreted the signal of me being a collaborator on his repo. And I offered my help to revert the merge if he wants me to.
So KL666 and your point that I had made such a super abuse of super-writting powers is a pile of (sorry to say), s a pile of shit. All it happend was a misunderstanding, very small and correctible between Herbert and I, and we can correct it as gentlemen, if you and others don't make a storm of a glass of water.
I hope you understand,
Best,
Israel