I guess we can summarize now? :-)
1) If you are the author of software, it's a bad idea to simply release code
into the Public Domain, mainly because you can't protect your self from
litigation by placing disclaimers in your code.
2) Public Domain means you relinquish your copyright control over your work
(but, you can still claim to be the author). Regaining control could be
difficult, you can't simply take something and license it if it's not
"different enough". E.g. adding comments or a license isn't changing the
work enough to give you or anyone else copyright control. The amount of
difference required could come down to local law interpretations.
3) Actually abandoning copyright can be difficult. Some countries don't
allow or recognise Public Domain.
4) Some countries require registration for copyright to be granted, others
don't, some do both.
5) Some people incorrectly think that Public Domain is synonymous with
OpenSource or Shareware.
6) Source Licenses are a way to remove or loosen restrictions already
implicitly granted because of copyright laws.
7) Some countries don't have copyright laws so 1-6 are moot points in those
countries anyway.
8) Noone contributing to this thread is a copyright lawyer.
--
Totally Holistic Enterprises Internet| | Andrew Milton
The Internet (Aust) Pty Ltd | |
ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon
PO Box 837 Indooroopilly QLD 4068 |[EMAIL PROTECTED]|
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
