FGUK version is the current version (without sound issue fixed), FGAddon version is outdated and they probably need to be merged. I don't upload changes to the SVN and this FGUK release is the last one made by me.

pjedvaj wrote in Tue Aug 11, 2015 12:29 pm:FGUK version is the current version (without sound issue fixed), FGAddon version is outdated and they probably need to be merged. I don't upload changes to the SVN and this FGUK release is the last one made by me.

Hi Petar,

I feel like I'm stepping on a land mine here Let me see if I can avoid the minefield with a few questions. I can see that you have made many, many changes to FGAddon already. So, my questions are:

You say you "don't upload changes to the SVN" - should this be "didn't", or you have given up on FGData/FGAddon? Is there a mailing list thread, FG or FGUK forum topic link I should read to understand the current situation? Or you will no longer make FGAddon changes as you've retired? Would you like me or someone else to merge the 1.4.2 version into FGAddon for you, so that it is up to date with your latest improvements and has the stereo-sound file fix? How do I get the stereo-sound fix pushed upstream back to FGUK? The "last one made by me" statement, does that imply that someone else is working on it?

Cheers,

Edward

Edit: One last question, why is the version in the *-set.xml file set to 1.9.1 and not to 1.3.2 of your last commits in 2014?

I'm a retired developer, this last few versions of MiG-21bis were only small fixes and livery updates. I did upload the package to Git and later to SVN but I didn't mantain it regulary (due to technical issues).

The project is GPLv3 and everybody is welcome to contribute, so don't worry about such things. To upload it to FGUK hangar you need to reupload the whole ZIP package again and to create developer account at FGUK.

pjedvaj wrote in Tue Aug 11, 2015 1:45 pm:I'm a retired developer, this last few versions of MiG-21bis were only small fixes and livery updates. I did upload the package to Git and later to SVN but I didn't mantain it regulary (due to technical issues).

The project is GPLv3 and everybody is welcome to contribute, so don't worry about such things. To upload it to FGUK hangar you need to reupload the whole ZIP package again and to create developer account at FGUK.

Cheers, at some point I'll look at updating the MiG-21bis in the official FG aircraft hangar for you, and then at pushing the fixed sound files to the extensive FGUK private hangar. Though if you were to simply copy the 2 new mono sound files from here and create a 1.4.3 stereo-sound fix version for the FGUK page, that would likely be a lot quicker. I have one question though, could you clarify if this is GPLv3 or GPLv3+ (i.e. GNU General Public License v3 "or any later version")? I can't find this mentioned in the aircraft files. This little addition is quite important for the future evolution of the FG project.

pjedvaj wrote in Wed Aug 19, 2015 3:45 pm:I'll do that in few days when I get back from the coast. License.txt in the MiG-21bis root folder should contain the GPLv3.

Cheers! The GPLv3 licence is there, but I couldn't find any licence header in a readme or other file to say if it is GPLv3 or GPLv3+. The '+' part - meaning "or any later version" and which is very useful for distant-future maintenance - is not in the licence itself.