-
As a response to several requests from the community, Embotech has decided to change the license of ECOS and its related repositories (ecos-python etc.) from GPLv3 to Apache v2, to make sure it is use…
-
Hi,
I am a little bit confused how to apply the GPLv3 licence to a backend connected to jetconf. Jetconf itself is GPL, that is clear... but the backend does NOT link to jetconf, but is loaded from…
-
- [ ] Which license to use?
- GPLv3 (or later)?
- AGPLv3 (or later)?
- Apache 2?
- [ ] Put the license header into every file.
-
speed : shinyproxy? or python dashboard? or flask?
licence : GPLv3, commercial use of shiny?
OpenCPU, alternative to shiny?
-
The file states "@license For open source use: GPLv3", but this package is licensed under Expat.
-
Dear @Thinkofname , @Mowstyl and @TfT-02
Words are powerless to express my gratitude. Thanks you for bringing us such a powerful plugin which I'm devoting to.
We maintains our own fork at [RPGi…
-
Per another developers recommendation, an AGPL3.0 would give us more protection due to the "cloud" loophole.
https://stackoverflow.com/questions/2127246/difference-between-affero-gpl-and-gplv3
-
In your repository, it is labeled "Javascript". It is not Javascript; it is Python and C++. Furthermore, you should add the GNU GPLv3 license as a label too.
-
This source code should be made GPLv3 so any project with a while loop should be required to share their source code.
-
Licence should be GPLv3 in a file named "COPYING" and referenced at the top of each file.
;-)