Re: KDE/kdebase

On Mon, 26 Jul 2010 17:20:59 +0200, Markus <[email protected]> wrote:
> On Monday 26 July 2010 16:06:33 John Layt wrote:
> 
>> Changing the names and
> dates is not OK without confirming with the authors.
> 
> I did not change
> names.
> I occasionally changed from "The xxx Developers" to "The xxx
> authors", because that's what the Authors tab is called. I did not modify
> any single name there!
> Additionally, when someone forgets to bump the
> copyright year, it's a bug and not something that needs confirmation.

The diff for r1154600 has lines like:
-                     ki18nc("@info:credit", "(C) 2006-2010 Peter Penz"));
+                     ki18nc("@info:credit", "Copyright © 2006–2011
Dolphin authors"));
-            ki18n("Copyright (c) 1998-2000 Geert Jansen, Pietro Iglio"));
+            ki18n("Copyright © 1998-2011 “KDE su” authors"));
and others.  See http://websvn.kde.org/?view=revision&revision=1154600.

This is what I'm referring to.  They are still listed under "authors", but
they or the maintainers chose to have their names in the copyright notice
rather than some meaningless semi-tautology (it's not surprising that
dolphin's copyrights are held by its authors).

You can't claim copyrights for next year, either.

If you think that these should change, please (as a matter of courtesy, if
nothing else) speak to the maintainers.  Or, if you think we need a
KDE-wide policy, discuss it on k-c-d or kde-licensing (I'm not entirely
sure what remit this comes under, since we kind of decided that it was
rather meaningless from a legal point of view).

On the other hand, if you simply want to replace "(C)", "Copyright (c)" and
similar strings with "Copyright ©" everywhere, I'm sure nobody would
object.  Bear in mind the issues of non-ASCII characters in C strings,
though - see http://doc.qt.nokia.com/4.6/qstring.html#initializing-a-string

> 
> In
> addition, siply reverting all my typo fixes is not tollerable!

They were mainly the removal of spaces at the end of lines, so I didn't put
in the work to separate out the parts of the patch.

Also, this was not a unilateral decision on my part - it was the result of
a discussion on #kde-devel on IRC.

Alex
_______________________________________________
Kde-licensing mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-licensing