Re: Oct and Nov 2012

On Tue, Oct 23, 2012 at 11:23 AM, Keith Marshall wrote:
> 1) What benefit accrues from changing '* filename.c', as an initial
>     comment identifying each source file, to '* @file filename.c'?  IMO,
>     the latter is no more than a cosmetic (i.e. ugly) distraction.

Docblock documentation.  I've gotten used to doing it that way.

>
> 2) Somewhat similarly, but with the usual IANAL disclaimer, likely more
>     serious: I'm fairly sure that '@copy 2012 MinGW.org project' lacks
>     any legal connotation, as would be attributable to a formal statement
>     of copyright:
>
>       Copyright (C) 2012, MinGW.org Project
>

I'm willing to modify the "@copy" to "Copyright (C)" throughout.

>     At the time, I believe Eben also directed us to list each year to
>     which a copyright notice applies *individually*; apparently, year
>     ranges lack the legal standing of such a list, (but again, the UK
>     copyright service advice contradicts this).
>

We've not assigned copyright until recently.  Therefore 2012 alone
works.  Remember Public Domain is the absence of copyright.

> 3) When a developer has gone to the trouble of identifying him/herself,
>     even in code donated to the public domain, you should *not* remove
>     it; in doing so, you are infringing the moral rights of those
>     developers to be identified as the authors of that code, which, if
>     I recall from our own previous discussions, is one of the objections,
>     (possibly even the principal objection), to the concept of public
>     domain in those jurisdictions which decline to recognise it.  With
>     our migration to a more formal statement of copyright, surely it
>     becomes even more important that this moral right be protected?
>

I'll agree that I may have overstepped the bounds on this a bit in
order to be consistent.  However, the rights of Public Domain source
give me the right to do so (not that I should have).  If you identify
that which is troublesome to you I can adjust it.  However the file
preamble should look the same across the board and any additional
comments go below it and not embedded in it.

> [*] And indeed, this recollection is supported by, and enshrined within
> the FSF's guidance notes on using the various forms of GNU licences:
> http://www.gnu.org/licenses/gpl-howto.html

And our license isn't really GPL now is it?

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct