From: Andrew Lunn <andrew@lunn.ch>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Alex Schuilenburg <alexs@ecoscentric.com>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCosCentric copyright hold in headers
Date: Thu, 08 Apr 2004 15:21:00 -0000 [thread overview]
Message-ID: <20040408152255.GN29940@lunn.ch> (raw)
In-Reply-To: <407567A2.3040106@eCosCentric.com>
On Thu, Apr 08, 2004 at 03:54:26PM +0100, Jonathan Larmour wrote:
> Andrew Lunn wrote:
> >Should we propose what the new banner looks like?
> >
> >Is the basic format of the current banner OK?
>
> I'd like it to be changed actually. Some of the information parts of the
> banner are _very_ frequently poorly maintained and/or inaccurate and do us
> a disservice. I think the Authors/Contributors bits are ambiguous; and the
> Purpose/Description ditto. It's never really been clear what Date the Date
> is for. I think I fill these in more than most people, but still rarely.
> Contributions very frequently have inaccurate fields here, most annoyingly
> the author.
>
> I think something like the following fields would be better/clearer:
>
> Maintained by: <person responsible for _this_ file, irrespective of what it
> was derived from>
>
> Contributors: <anyone else who's worked on it and wants a mention>
> Derived from: <what file/package it was derived from if relevant
> Description:
>
> I propose dropping the date entirely partly due to the ambiguity and partly
> because it doesn't tell us anything we can't find out more accurately from
> the changelogs.
>
> I propose dropping the mini-description underneath the filename at the top,
> as it is usually no better than the description further down.
Just to make that a bit more concrete i've made an example.
//==========================================================================
//
// common/kapi.cxx
//
//==========================================================================
//####ECOSGPLCOPYRIGHTBEGIN####
// -------------------------------------------
// This file is part of eCos, the Embedded Configurable Operating System.
// Copyright (C) 2004 Free Software Foundation, Inc.
//
// eCos is free software; you can redistribute it and/or modify it under
// the terms of the GNU General Public License as published by the Free
// Software Foundation; either version 2 or (at your option) any later version.
//
// eCos is distributed in the hope that it will be useful, but WITHOUT ANY
// WARRANTY; without even the implied warranty of MERCHANTABILITY or
// FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
// for more details.
//
// You should have received a copy of the GNU General Public License along
// with eCos; if not, write to the Free Software Foundation, Inc.,
// 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
//
// As a special exception, if other files instantiate templates or use macros
// or inline functions from this file, or you compile this file and link it
// with other works to produce a work based on this file, this file does not
// by itself cause the resulting work to be covered by the GNU General Public
// License. However the source code for this file must still be made available
// in accordance with section (3) of the GNU General Public License.
//
// This exception does not invalidate any other reasons why a work based on
// this file might be covered by the GNU General Public License.
//
// -------------------------------------------
//####ECOSGPLCOPYRIGHTEND####
//==========================================================================
//#####DESCRIPTIONBEGIN####
//
// Maintained by: nickg, dsm
// Contributors: nickg
// Derived from:
// Description: C++ implementation of the C API
//
//####DESCRIPTIONEND####
//
//==========================================================================
I don't think this is going to be easy. Does dsm maintain this file?
Andrew
next prev parent reply other threads:[~2004-04-08 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040408101602.GJ29940@lunn.ch>
[not found] ` <4075305D.8020101@eCosCentric.com>
[not found] ` <20040408111939.GK29940@lunn.ch>
[not found] ` <407556D4.8080407@ecoscentric.com>
2004-04-08 14:02 ` Jonathan Larmour
2004-04-08 14:20 ` Andrew Lunn
2004-04-08 14:54 ` Jonathan Larmour
2004-04-08 15:21 ` Andrew Lunn [this message]
2004-04-08 15:27 ` Jonathan Larmour
2004-04-08 14:49 ` Alex Schuilenburg
2004-04-08 15:40 ` Jonathan Larmour
2004-04-08 16:31 ` Alex Schuilenburg
2004-05-07 17:11 Frank Ch. Eigler
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=20040408152255.GN29940@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexs@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=jifl@eCosCentric.com \
/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).