public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>,
	  eCos discussion <ecos-discuss@ecos.sourceware.org>
Subject: Repository copyrights updated
Date: Thu, 29 Jan 2009 17:49:00 -0000	[thread overview]
Message-ID: <4981EC0D.2050305@eCosCentric.com> (raw)

As promised, I have now (finally!) finished updating the copyrights on all
files. Please let me know about any problems or anomalies. I've looked over
lots of it, but can't guarantee to have found everything.

To the maintainers: the trunk is still temporarily frozen until Bart
completes his changes.

Some things of note:

1) your next 'cvs update' will take forever. There are 22MBytes of changes,
with essentially every file changed. It may well be faster to start with a
new checkout (i.e. 'cvs co' to a new direcotry) if you haven't any local
changes.

2) I have slightly clarified the licence text, e.g. the BSDLICENCE
previously said:
// Portions of this software may have been derived from OpenBSD or other
// sources, and are covered by the appropriate copyright disclaimers
// included herein.

and now says e.g.:
// -------------------------------------------
// This file is part of eCos, the Embedded Configurable Operating System.
//
// Portions of this software may have been derived from FreeBSD
// or other sources, and if so are covered by the appropriate copyright
// and license included herein.
//
// Portions created by the Free Software Foundation are
// Copyright (C) 2002, 2003 Free Software Foundation, Inc.

(note that the net stack mentioned has been worked out appropriately).

I have also improved formatting including line lengths in some cases. The
FSF address has changed too.

3) Distinct licence blocks are better marked with an appropriate
fooCOPYRIGHTBEGIN marker.

Maintainers and contributors: please ensure consistency with existing
formats. Do not make up your own. Anything between
COPYRIGHTBEGIN/COPYRIGHTEND markers is allowed to be replaced in future.
Just like they were now.

4) ChangeLogs are now GPL'd. The eCos exception made no sense.

5) I have updated the RedBoot version string to comply with section 2(c) of
the GPL.

6) I have _not_ done anything to make the copyright years more accurate.
This was a can of worms. The copyright years are the same as before (but
now FSF). In future all contributions must make sure that they contain
correct copyright years. Modifications to existing files must update the
copyright year with the current year. Contributors should make sure they do
this in any submitted patch.

Maintainers, please get into the habit of checking that whenever you check
in a file, you check whether the copyright year of all modified files
includes the current year.

7) There are a vast number of other licence related fixes in individual
files. I daren't count the number of special cases there have been, but
there's a lot.  Again in future, please be consistent with existing
formatting. There are no prizes for doing your own thing.

After the trunk is unfrozen, there will be a short time to commit anything
important, and then I will cut a branch for the eCos 3.0 release and then I
will create a first release candidate - there will probably/hopefully only
be one.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

             reply	other threads:[~2009-01-29 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 17:49 Jonathan Larmour [this message]
2009-01-29 22:40 ` John Dallaway
2009-01-30  1:21   ` Jonathan Larmour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4981EC0D.2050305@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ecos-maintainers@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).