Okay guys, we hear you!
We know you want to see the contents of undo, how it works, and what the installer does to connect it all. Here are the problems we currently have with doing this:
- DCS EULA strictly forbids us from redistributing game files, modified or not. We can't just copy-paste our altered scripts for the Mission Editor GUI without risking legal trouble. Snowflake believes in doing open-source right, and that means playing fair by the rules.
- Because of problem no. 1, we have to use code injection and generation as our alternative; however, the lack of a trust certificate for the installer allows anyone to reuse our code for malicious purposes. It's a risk too great to ignore, even without one.
I have no intentions of veering away from the dream of open-sourcing our work. We are committed to open-source, as you can see with orbit, markline and even mission environment documentation.
Undo just so happens to be in a unique position where it works, complies with the DCS EULA and produces desired behaviour, but code security is something we will never give up in contrast to "proof" that's solved by opening the Mission Editor. 😉
Sometime this month, we will introduce a Certificate Authority for the installer. "Why is this important? Why do you keep bringing it up?" Well, a trust certificate basically tells your computer's operating system, whether Windows or MacOS, that this file is legitimate, downloaded and safe to use. The DCS Architects Discord, a private group with some of the community's most prominent contributors, have some of us working towards this objective.
In essence: we've always planned on open-source, LGPL 2.1 has zero contingencies stating it must be freely accessible on the Internet, it's only to protect code from being modified privately or without sharing. We're thankful that many of you have been vocal enough to express how much you care about making the code more easily accessible on GitHub, and that is something with active steps being taken.
I welcome any feedback; we value a respectful forum where the legitimacy and safety of our work can be discussed while mitigating presumptions by talking face-to-face with the developer. 😀 Happy mission editing!
Okay guys, we hear you!
We know you want to see the contents of undo, how it works, and what the installer does to connect it all. Here are the problems we currently have with doing this:
I have no intentions of veering away from the dream of open-sourcing our work. We are committed to open-source, as you can see with orbit, markline and even mission environment documentation.
Undo just so happens to be in a unique position where it works, complies with the DCS EULA and produces desired behaviour, but code security is something we will never give up in contrast to "proof" that's solved by opening the Mission Editor. 😉
Sometime this month, we will introduce a Certificate Authority for the installer. "Why is this important? Why do you keep bringing it up?" Well, a trust certificate basically tells your computer's operating system, whether Windows or MacOS, that this file is legitimate, downloaded and safe to use. The DCS Architects Discord, a private group with some of the community's most prominent contributors, have some of us working towards this objective.
In essence: we've always planned on open-source, LGPL 2.1 has zero contingencies stating it must be freely accessible on the Internet, it's only to protect code from being modified privately or without sharing. We're thankful that many of you have been vocal enough to express how much you care about making the code more easily accessible on GitHub, and that is something with active steps being taken.
I welcome any feedback; we value a respectful forum where the legitimacy and safety of our work can be discussed while mitigating presumptions by talking face-to-face with the developer. 😀 Happy mission editing!