On 01/14/2012 10:23 PM, Hamish wrote:
Jarek wrote:
Ok, it explains everything. So if I want to publish code with any GPL
privileges granded, but keep code integrity in one official place which
I can put in paper as link to OFFICIAL source code, with guarantee that
it won't be accidentaly
Hi
I have a question about putting into add-on repository the code
containing completly new terrain analysis system.
Code will be on classic GPL license, however I would like to TEMPORARILY
restrict the name of module, scientific idea (completely new) and
permission to code modification. It
Jarek Jasiewicz wrote:
I have a question about putting into add-on repository the code
containing completly new terrain analysis system.
Code will be on classic GPL license, however I would like to TEMPORARILY
restrict the name of module, scientific idea (completely new) and
permission
On 01/14/2012 07:23 PM, Glynn Clements wrote:
Jarek Jasiewicz wrote:
I have a question about putting into add-on repository the code
containing completly new terrain analysis system.
Code will be on classic GPL license, however I would like to TEMPORARILY
restrict the name of module,
Jarek wrote:
Ok, it explains everything. So if I want to publish code with any GPL
privileges granded, but keep code integrity in one official place which
I can put in paper as link to OFFICIAL source code, with guarantee that
it won't be accidentaly changed, I must put it outside GRASS
