Personal tools

Talk:Public Domain in the middle

From GPLv3 Wiki

Revision as of 03:59, 4 November 2006; view current revision
←Older revision | Newer revision→

The manner in which the interface connects the programs effects whether or not it is covered by the GPL.

Here are my understandings. I will try to find references to back them up:

  • The GPL disallows either of the programs to 'link' (even if dynamically) to the other to allow calling functions directly by operating within the same "address space".
  • The GPL allows either program to 'launch' the other and supply command-line arguments, then parse the output or scrape files for results. This is an unfortunate workaround that can be made very efficient (keep one instance of the CLI program always running and queue the requests per host thread).
  • The GPL allows either program to communicate with the other through a local or networked socket. This is a massive hole that needs to be plugged, especially considering clever advances in delivering remote content - such as through client-side rendering of drawing primitives for smooth interaction even with 3D applications.

Can it be entered into the Public Domain?

This question cannot be separated from whether or not the interface may be held proprietary.

If the interface software is covered by the GPL, then it may not be entered into the Public Domain because Public Domain software is not protected from those that would make it proprietary.

To release software into the Public Domain is to relenquish Copyright ownership of that work, and therefore to give up the ability to impose requirements through a license.

All software licenses have requirements that the user must follow or be in violation of Copyright law.

Most "source available" licenses (whether they are compatible with the GPL or not) have few requirements, and they are mostly mundane (such as a requirement to keep the Copyright notice intact at the beginning of each file).

But the GPL really puts Copyright to work for the benefit of society by requiring users have freedom for all work built upon earlier cooperation. This is called Copyleft.

The Copyleft nature of the GPL guarantees your contributions can never be "held against you" the way Public Domain software might be. Most other software licenses also fail to address this trouble, which is why so much BSD code is in Microsoft and Apple Operating Systems.