- Feb 2021
note that TRB source code modifications are not proprietary
In other words, you can build on this software in your proprietary software but can't change the Trailblazer source unless you're willing to contribute it back.
loophole: I wonder if this will actually just push people to move their code -- which at the core is/would be a direction modification to the source code - out to a separate module. That's so easy to do with Ruby, so this restriction hardly seems like it would have any effect on encouraging contributions.
- wording designed to be more palatable/pleasing/inoffensive
- good point
- neutral/dispassionate/impartial/objective wording
- open-source software: not contributing new code back to project
- proprietary software
- annotation meta: may need new tag
- loophole/escape hatch
- software licensing
- Jan 2021
We can certainly explain the issues snap cause without using political or religious arguments. We did so in the documentation I linked to above.