2 Matching Annotations
- Feb 2021
-
2019.trailblazer.to 2019.trailblazer.to
-
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.
Tags
- annotation meta: may need new tag
- wording designed to be more palatable/pleasing/inoffensive
- well-written
- neutral/dispassionate/impartial/objective wording
- software licensing
- proprietary software
- loophole/escape hatch
- good point
- open-source software: not contributing new code back to project
- reminder
- LGPL
Annotators
URL
-
- Nov 2019
-
news.ycombinator.com news.ycombinator.com
-
the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.
-