[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs]  mention that a copyright-holder can be a generic, n
[Savannah-cvs]  mention that a copyright-holder can be a generic, not-legally-extant, identifier; links
Fri, 18 Nov 2016 23:34:07 +0000 (UTC)
Date: 2016-11-18 23:34:02 +0000 (Fri, 18 Nov 2016)
mention that a copyright-holder can be a generic, not-legally-extant,
--- trunk/sviki/HowToGetYourProjectApprovedQuickly.mdwn 2016-11-08 17:28:47 UTC
+++ trunk/sviki/HowToGetYourProjectApprovedQuickly.mdwn 2016-11-18 23:34:02 UTC
@@ -25,10 +25,11 @@
- Give a pointer to your source code, or upload it as an attachment to
-- Apply valid copyright and license notices using our templates to
- each source file in your project; include a copy of the license you
- chose. It is ideal for derived files to carry (generated) notices
- as well. See <http://www.gnu.org/licenses/gpl-howto.html>.
+- Apply valid copyright and license notices ([[ValidNotices]]) using
+ our templates to each source file in your project; include a copy of
+ the license you chose. It is ideal for derived files to carry
+ (generated) notices as well. See
- Refer to the "GNU/Linux operating system" instead of "Linux", which
is the kernel. Advertise the free software movement, which we
@@ -77,9 +78,10 @@
recommend against using LGPL\*-only.)
- Consistent licensing:
- Write appropriate copyright and license notices, at the beginning of
- _all_ of your source (non-derivative) files. Standard templates are
- at <http://www.gnu.org/licenses/gpl-howto.html> and
+ Write appropriate copyright and license notices ([[ValidNotices]]),
+ at the beginning of _all_ of your source (non-derivative) files.
+ Standard templates are at
+ <http://www.gnu.org/licenses/gpl-howto.html> and
please use them to speed up approval. More answers at
<http://www.gnu.org/licenses/gpl-faq.html>. For the GFDL, check
--- trunk/sviki/ProjectApproval.mdwn 2016-11-08 17:28:47 UTC (rev 280)
+++ trunk/sviki/ProjectApproval.mdwn 2016-11-18 23:34:02 UTC (rev 281)
@@ -29,7 +29,7 @@
its programming language and its depencies (with
- Don't forget to give a pointer to the source code.
-- Apply valid copyright and license notices using our templates, and
+- Apply valid copyright and license notices ([[ValidNotices]]), and
include a copy of the license you chose.
- Refer to the GNU/Linux operating system and reserve the name "Linux"
for referring specifically to the kernel that Linus wrote. More
--- trunk/sviki/ValidNotices.mdwn 2016-11-08 17:28:47 UTC (rev 280)
+++ trunk/sviki/ValidNotices.mdwn 2016-11-18 23:34:02 UTC (rev 281)
@@ -1,21 +1,29 @@
+Valid copyright notices
Free software licenses rely on copyright law. The pro is that they are
-enforceable. The cons is that you get all the administrative burden.
+enforceable. The con is that you get the administrative burden.
+Fortunately, this merely means having in all your files:
-Fortunately this just means adding to all your files:
- a copyright notice:
- `Copyright (C) year1, year2, year3 copyright-holder`
+ `Copyright _year1_, _year2_, _year3_ _copyright-holder_`
- a license notice
-For more information on copyright, you may want to check Dave Turner's
-blog entry on *The Basics*:
+About the _year_ list: the FSF recommends listing every relevant year
+individually, but it is acceptable to use ranges (assuming every year in
+the range, inclusive, is covered, of course).
-Richard Stallman's *Legal Matters* is also worth reading (although
-there're a few parts specific to GNU projects):
+About the _copyright-holder_: the FSF recommends listing individual
+(real-world) names, or other entities with legal status, but it is
+acceptable to use ersatz identifiers like "Project Foo
+contributors" even when Project Foo has no legal existence. Using such
+fake identifiers makes the copyright less defendable in court.
+and related messages.)
+Richard Stallman's _Legal Matters_ section in the GNU maintainers guide
+is worth reading (although some parts are specific to GNU projects):
--- trunk/sviki/WhyLegalChecksBeforeRelease.mdwn 2016-11-08 17:28:47 UTC
+++ trunk/sviki/WhyLegalChecksBeforeRelease.mdwn 2016-11-18 23:34:02 UTC
@@ -1,9 +1,14 @@
-Sending code via CVS is publishing your project, since it will be
-available via anonymous CVS access.
+# Why legal checks before release?
+Committing code to a version control system is a form of distribution,
+since it will be available to anyone. Distribution, in any form, is the
+usual trigger for copyright-based licenses, due to the nature of
+copyright in the law.
That's why we want the legal parts of the packaging job to be done
-before the project is approved at Savannah - which notably includes
-proper copyright notices and inclusion of the full text of your
+before the project is approved at Savannah -- notably including valid
+copyright notices ([[ValidNotices]]) and inclusion of the full text of
+your project's license ([[ProjectApproval]],
-`Release` in the legal sense is not just packaging a tarball :)
+In short, "release" in the legal sense is not only packaging a tarball.
|[Prev in Thread]
||[Next in Thread]|
- [Savannah-cvs]  mention that a copyright-holder can be a generic, not-legally-extant, identifier; links,