Remove confusing note about license compatibility

principles.qmd

@@ -129,7 +129,7 @@ As an open-source initiative, Epiverse-TRACE will benefit from numerous other OS
 - We take, but we give back: we use and build upon OSS projects, but we give back to the community by developing new OSS tools, and contributing to existing ones
 - We prioritize contributions to existing projects over forks, and forks over project duplications
 - When code re-use is needed, we duly credit authors and point to the source, and invite authors as contributors on our project. We give credits by prefacing reused code by a comment e.g.: `// credits: this code was adapted from SOURCE_URL`, where `SOURCE_URL` is the URL we obtained the code from (*e.g.* stackoverflow, etc.). Using a fixed syntax for credits can be used to summarize such contributions programmatically.
-- When reusing licensed code, we ensure that third-party licenses are compatible with our project's license. For instance, we may want to avoid reusing GPL code if our project uses MIT, since we would then have to change our license to GPL. See [this article](https://www.gnu.org/licenses/license-list.html) by the Free Software Foundation for more information on free software licenses.
+- When reusing licensed code, we ensure that third-party licenses are compatible with our project's license. See [this article](https://www.gnu.org/licenses/license-list.html) by the Free Software Foundation for more information on free software licenses.
 - We prioritize the integration of existing tools over development from scratch of new tools
 - We welcome external contributions and promote transparency on all our projects
 - When contributing to external projects, we observe their contributor code of conduct