Re: Copyright
On Tue, Oct 29, 2002 at 11:20:45AM +0100, Andre Poenitz wrote: > Why do we have "1995 Mathias Ettrich" in frontends/qt2 ? Er, it's a homage ? john -- "All photography is accurate - none of it is truth." - Richard Avedon
Copyright
Why do we have "1995 Mathias Ettrich" in frontends/qt2 ? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [PATCH}: src/support/* copyright notice
On Wednesday 25 September 2002 10:45 am, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > | Tedious but done. Ok to apply? [snip fixes] > If you fix up these it is ok to commit. :-) Ok dokey. Angus
Re: [PATCH}: src/support/* copyright notice
Angus Leeming <[EMAIL PROTECTED]> writes: | Tedious but done. Ok to apply? +/** + * \file FileInfo.C + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * - * LyX, The Document Processor + * \author unknown * mine +/** + * \file FileInfo.h + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * - * LyX, The Document Processor + * \author unknown * mine +/** + * \file LAssert.C + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * - * LyX, The Document Processor + * \author unknown * mine +/** + * \file filetools.C + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. + * + * parts Copyright 1985, 1990, 1993 Free Software Foundation, Inc. + * + * \author Ivan Schreter + * \author Dirk Niggemann + * \author Asger Alstrup + * I should be added as well... and Jean-Marc. Possibly others. /** * \file lyxalgo.h - * Copyright 1995-2002 the LyX Team - * Read the file COPYING - * - * A variety of useful templates. + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * * \author unknown + * mine * \file lyxlib.h - * Copyright 1995-2002 the LyX Team - * Read the file COPYING + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * * A selection of useful system functions made * handy for C++ usage. * * \author unknown + * mine I think. +/** + * \file lyxsum.C + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * - * LyX, The Document Processor - * Copyright 2001 The LyX Team. + * \author unknown * mine /** * \file path.C - * Copyright 1995-2002 the LyX Team - * Read the file COPYING + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * * \author unknown + * mine /** * \file path.h - * Copyright 1995-2002 the LyX Team - * Read the file COPYING + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * * \author unknown + * mine /** * \file textutils.h - * Copyright 1995-2002 the LyX Team - * Read the file COPYING + * This file is part of LyX, the document processor. + * Licence details can be found in the file COPYING. * * \author unknown + * Matthias Ettrich and I. If you fix up these it is ok to commit. :-) -- Lgb
[PATCH}: src/support/* copyright notice
Tedious but done. Ok to apply? Angus support.diff.gz Description: GNU Zip compressed data
Re: copyright
Andre Poenitz <[EMAIL PROTECTED]> writes: | On Tue, Sep 10, 2002 at 04:54:14PM +0200, Lars Gullik Bjønnes wrote: | > I'd say yes. | | Ok. Looks like I have to edit the stuff manually anyway *sigh*. | | What's the prefered order for: | | | [1] This emacs stuff? | | // -*- C++ -*- Only in .h files, and at the very top of the file. | [2] the include guard | | #ifndef MATH_ATOM_H | #define MATH_ATOM_H After the author stuff | [3] this stuff I still don't understand | | #ifdef __GNUG__ | #pragma interface | #endif usually right after the include guards. | [4] includes | | #include "math_inset.h" most specific to least specific. after the include guards and the pragma (usually) | [5] the author stuff | | /** |* Wrapper for MathInset * with copy-semantics |* |* \author André Pönitz |* |* Full author contact details are available in file CREDITS |*/ at the top of the file. | [6] Some more verbatim comments | | /** | The 'atom' is the major blob in math typesetting. And 'atom' consists | of a nucleus, an optional superscript, and an optional subscript. | ... Where doxygen would want it. -- Lgb
Re: copyright
On Tue, Sep 10, 2002 at 04:54:14PM +0200, Lars Gullik Bjønnes wrote: > I'd say yes. Ok. Looks like I have to edit the stuff manually anyway *sigh*. What's the prefered order for: [1] This emacs stuff? // -*- C++ -*- [2] the include guard #ifndef MATH_ATOM_H #define MATH_ATOM_H [3] this stuff I still don't understand #ifdef __GNUG__ #pragma interface #endif [4] includes #include "math_inset.h" [5] the author stuff /** * Wrapper for MathInset * with copy-semantics * * \author André Pönitz * * Full author contact details are available in file CREDITS */ [6] Some more verbatim comments /** The 'atom' is the major blob in math typesetting. And 'atom' consists of a nucleus, an optional superscript, and an optional subscript. ... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: copyright
Andre Poenitz <[EMAIL PROTECTED]> writes: | Have we reached consensus on the copyright stuff? > | Would it be ok to run the latest script posted to the list on src/mathed | and add myself as \author in all cases where there isn't one and Alejandro | in those .C where he is mentioned as author in the .h? I'd say yes. -- Lgb
copyright
Have we reached consensus on the copyright stuff? Would it be ok to run the latest script posted to the list on src/mathed and add myself as \author in all cases where there isn't one and Alejandro in those .C where he is mentioned as author in the .h? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: On copyright
On Thu, Sep 05, 2002 at 06:37:07PM +0200, Lars Gullik Bjønnes wrote: > Yes we do. *SQUEEEAK* Ah well. john -- "Take the ideas you find useful. Try not to get hung up on the labels." - Jonathan S. Shapiro
Re: On copyright
John Levon <[EMAIL PROTECTED]> writes: | On Thu, Sep 05, 2002 at 04:21:39PM +0100, Angus Leeming wrote: | | > "Full author contact details available in file CREDITS" | | Do we really need that line everywhere ? People aren't morons | ... Stop those piggish sounds. Yes we do. -- Lgb
Re: On copyright
On Thu, Sep 05, 2002 at 04:21:39PM +0100, Angus Leeming wrote: > "Full author contact details available in file CREDITS" Do we really need that line everywhere ? People aren't morons ... regards john -- "Take the ideas you find useful. Try not to get hung up on the labels." - Jonathan S. Shapiro
Re: On copyright
On Thursday 05 September 2002 3:47 pm, Angus Leeming wrote:
> On Thursday 05 September 2002 3:58 pm, Lars Gullik Bjønnes wrote:
> > | // This file is part of LyX, the document processor.
> > | // Licence details can be found in the file COPYING.
> > |
> > | I think that that cuts it don't you? At least it describes /why/ anyone
> > | would want to read COPYING.
> >
> > Yes, let's do this. I guess this is the most we can reach consensus
> > on...
>
> Modified script is attached.
If you want to see some scary sed, then this was posted to the sed users
list. It is a reply to my question asking how to add that line
"Full author contact details available in file CREDITS"
after the last occurance of \author
/\\author/ !{
x
/\\author/ i\
*\
* Full author ...
x
}
h
The idea is that we on every lap save the line in the hold buffer.
Then we first match a pattern matching the block end-condition, and
then match the block condition before we insert anything. This is a
more general way to do something after a block.
This is in comparison to my hack (below). Ain't some things amazing?
Angus
# extract the number of the last \author line
LINES=`grep -n '[\]author' ${FILE}`
STATUS=$?
EXISTSALREADY=`grep 'Full author contact details' ${FILE}`
if [ ${STATUS} -eq 0 -a $? -ne 0 ]; then
LINES=`echo "${LINES}" | sed 's/\([0-9]*\):\(.*\)/\1/'`
LINE=`echo "${LINES}" | sed '$ !d'`
APPENDSCRIPT
fi
APPENDSCRIPT () {
# Must define ${SED} and ${LINE} in the main body of the script
cat - >> ${SED} <
Re: On copyright
On Thursday 05 September 2002 3:58 pm, Lars Gullik Bjønnes wrote: > | // This file is part of LyX, the document processor. > | // Licence details can be found in the file COPYING. > | > | I think that that cuts it don't you? At least it describes /why/ anyone > | would want to read COPYING. > > Yes, let's do this. I guess this is the most we can reach consensus > on... Modified script is attached. All files in src/frontends, src/frontends/controllers, src/frontends/xforms and src/graphics have been done. Angus rmcopyright.sh Description: application/shellscript
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | On Thursday 05 September 2002 3:50 pm, John Levon wrote: | > On Thu, Sep 05, 2002 at 01:24:53PM +0100, José Abílio Oliveira Matos wrote: | > > This note can be anywhere in the file, the most usual options are begin | > > and end. Also you should note that this is standard. | > | > That's how I navigate. If this yuck gets done I suppose I shall have to | > teach vim how to fold it away (assuming it can). | > | > btw, the blurb you show is wrong - we grant additional rights. | | I've altered the shell scripts that generate the form_xyz.[Ch] files to output | | // This file is part of LyX, the document processor. | // Licence details can be found in the file COPYING. | | I think that that cuts it don't you? At least it describes /why/ anyone would | want to read COPYING. Yes, let's do this. I guess this is the most we can reach consensus on... -- Lgb
Re: On copyright
John Levon <[EMAIL PROTECTED]> writes: | btw, the blurb you show is wrong - we grant additional rights. Not that again... -- Lgb
Re: On copyright
On Thursday 05 September 2002 3:50 pm, John Levon wrote: > On Thu, Sep 05, 2002 at 01:24:53PM +0100, José Abílio Oliveira Matos wrote: > > This note can be anywhere in the file, the most usual options are begin > > and end. Also you should note that this is standard. > > That's how I navigate. If this yuck gets done I suppose I shall have to > teach vim how to fold it away (assuming it can). > > btw, the blurb you show is wrong - we grant additional rights. I've altered the shell scripts that generate the form_xyz.[Ch] files to output // This file is part of LyX, the document processor. // Licence details can be found in the file COPYING. I think that that cuts it don't you? At least it describes /why/ anyone would want to read COPYING. Angus
Re: On copyright
On Thu, Sep 05, 2002 at 01:24:53PM +0100, José Abílio Oliveira Matos wrote: > This note can be anywhere in the file, the most usual options are begin and > end. Also you should note that this is standard. That's how I navigate. If this yuck gets done I suppose I shall have to teach vim how to fold it away (assuming it can). btw, the blurb you show is wrong - we grant additional rights. regards john -- "Take the ideas you find useful. Try not to get hung up on the labels." - Jonathan S. Shapiro
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | On Thursday 05 September 2002 3:38 pm, Lars Gullik Bjønnes wrote: | | > On occasion it might be nice to do as other gpl projects too... | | You mean like using politically correct GUI toolkits ? And we are now, aren't we? (if we only could get the gtk port going...) -- Lgb
Re: On copyright
On Thu, Sep 05, 2002 at 02:59:18PM +0100, Angus Leeming wrote: > This file is part of LyX, the document processor. > It is GPL-ed code. Not true. Like I said, you'll need lines and lines. > See the file COPYING This is more than enough (i.e. what we have already) /** * \file mutt-mrtall-94664-120 * Read the file COPYING * * \author John Levon */ I definitely think this is best. (btw, I would encourage people to add text in that header to say what the file is *for* if needed). regards john -- "Take the ideas you find useful. Try not to get hung up on the labels." - Jonathan S. Shapiro
Re: On copyright
On Thu, Sep 05, 2002 at 04:22:23PM +0200, Lars Gullik Bjønnes wrote: > So that a file taken out of context (i.e. lyx) still has the license > information. Please tell me you don't want 30 lines of license information in every file like Mozilla or something. The rreference to COPYING is fine. regards john -- "Take the ideas you find useful. Try not to get hung up on the labels." - Jonathan S. Shapiro
Re: On copyright
On Thursday 05 September 2002 3:38 pm, Lars Gullik Bjønnes wrote: > On occasion it might be nice to do as other gpl projects too... You mean like using politically correct GUI toolkits ?
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | On Thursday 05 September 2002 3:22 pm, Lars Gullik Bjønnes wrote: | > Angus Leeming <[EMAIL PROTECTED]> writes: | > | On Thursday 05 September 2002 3:12 pm, José Abílio Oliveira Matos wrote: | > | > On Thursday 05 September 2002 15:00, Lars Gullik Bjønnes wrote: | > | > > Hmm da hmm I have some counters stuff to look at first, | > | > > but after that... please somebody beat me to it... | > | > | > | > Should we replace the COPYING reference with the explicit note? | > | | > | Well it's dead easy to do: just modify the script. But personally I quite | > | like the fact that all this copyright notice stuff is in one place too. | > | | > | My philosophy is, we try not to replicate code unnecessarily, so why | > | replicate blurb? | > | > So that a file taken out of context (i.e. lyx) still has the license | > information. | | Then add a line from the old style headers: | This file is part of LyX, the document processor. | It is GPL-ed code. | See the file COPYING or www.lyx.org/COPYING for details On occasion it might be nice to do as other gpl projects too... -- Lgb
Re: On copyright
On Thursday 05 September 2002 3:22 pm, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > | On Thursday 05 September 2002 3:12 pm, José Abílio Oliveira Matos wrote: > | > On Thursday 05 September 2002 15:00, Lars Gullik Bjønnes wrote: > | > > Hmm da hmm I have some counters stuff to look at first, > | > > but after that... please somebody beat me to it... > | > > | > Should we replace the COPYING reference with the explicit note? > | > | Well it's dead easy to do: just modify the script. But personally I quite > | like the fact that all this copyright notice stuff is in one place too. > | > | My philosophy is, we try not to replicate code unnecessarily, so why > | replicate blurb? > > So that a file taken out of context (i.e. lyx) still has the license > information. Then add a line from the old style headers: This file is part of LyX, the document processor. It is GPL-ed code. See the file COPYING or www.lyx.org/COPYING for details Angus
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | On Thursday 05 September 2002 3:12 pm, José Abílio Oliveira Matos wrote: | > On Thursday 05 September 2002 15:00, Lars Gullik Bjønnes wrote: | > > Hmm da hmm I have some counters stuff to look at first, | > > but after that... please somebody beat me to it... | > | > Should we replace the COPYING reference with the explicit note? | | Well it's dead easy to do: just modify the script. But personally I quite | like the fact that all this copyright notice stuff is in one place too. | | My philosophy is, we try not to replicate code unnecessarily, so why | replicate blurb? So that a file taken out of context (i.e. lyx) still has the license information. -- Lgb
Re: On copyright
José Abílio Oliveira Matos <[EMAIL PROTECTED]> writes: | On Thursday 05 September 2002 15:00, Lars Gullik Bjønnes wrote: | > | > Hmm da hmm I have some counters stuff to look at first, | > but after that... please somebody beat me to it... | | Should we replace the COPYING reference with the explicit note? Not yet... let's try to reach consensus on that first. -- Lgb
Re: On copyright
On Thursday 05 September 2002 3:12 pm, José Abílio Oliveira Matos wrote: > On Thursday 05 September 2002 15:00, Lars Gullik Bjønnes wrote: > > Hmm da hmm I have some counters stuff to look at first, > > but after that... please somebody beat me to it... > > Should we replace the COPYING reference with the explicit note? Well it's dead easy to do: just modify the script. But personally I quite like the fact that all this copyright notice stuff is in one place too. My philosophy is, we try not to replicate code unnecessarily, so why replicate blurb? Angus
Re: On copyright
On Thursday 05 September 2002 15:00, Lars Gullik Bjønnes wrote: > > Hmm da hmm I have some counters stuff to look at first, > but after that... please somebody beat me to it... Should we replace the COPYING reference with the explicit note? -- José Abílio
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | Ok, I've "done" all files in the src/graphics, src/frontends/controllers and | src/frontends/xforms dirs. That includes moving all old style headers to the | new style. (I think.) Ok, thanks. | I added an "author unknown" entry to any file that did not have an author | listed. Ok. | I reckon that I've "done my bit" on this front and am now very bored of it. | Feel free to continue. Hmm da hmm I have some counters stuff to look at first, but after that... please somebody beat me to it... -- Lgb
Re: On copyright
Ok, I've "done" all files in the src/graphics, src/frontends/controllers and src/frontends/xforms dirs. That includes moving all old style headers to the new style. (I think.) I added an "author unknown" entry to any file that did not have an author listed. I reckon that I've "done my bit" on this front and am now very bored of it. Feel free to continue. Angus ps the script got a bit more robust. I attach it should anyone else like to have a go. rmcopyright.sh Description: application/shellscript
Re: On copyright
José Abílio Oliveira Matos <[EMAIL PROTECTED]> writes: | Since that is your code I think that you can, that change doesn't apply to | older versions. I cannot give up rights. -- Lgb
Re: On copyright
On Thursday 05 September 2002 12:30, Lars Gullik Bjønnes wrote: > | Why not to replace "Read the file COPYING" with the following? > > I kindo like this too, but it is a farily large blurb. > (I do not buy any size arguments as in bits and bytes) This note can be anywhere in the file, the most usual options are begin and end. Also you should note that this is standard. > Oh, we can just take owership of public domain and release them as > GPL. (or isn't that allowed? on another note: Public domain is not > legal in norway since you cannot give up your copyright) Since that is your code I think that you can, that change doesn't apply to older versions. -- José Abílio
Re: On copyright
José Abílio Oliveira Matos <[EMAIL PROTECTED]> writes: | Why not to replace "Read the file COPYING" with the following? I kindo like this too, but it is a farily large blurb. (I do not buy any size arguments as in bits and bytes) | * This program 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 | * of the License, or (at your option) any later version. | * | * This program 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 this program; if not, write to the Free Software | * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. | | I would add this for most of the files whose license is GPL, we have some | files that are in the public domain. Oh, we can just take owership of public domain and release them as GPL. (or isn't that allowed? on another note: Public domain is not legal in norway since you cannot give up your copyright) -- Lgb
Re: On copyright
On Thursday 05 September 2002 8:08 am, Lars Gullik Bjønnes wrote:
> | Just so I'm perfectly clear:
> |
> | /*
> | * \file PreviewLoader.C
> | * Read the file COPYING
> | *
> | * \author Angus Leeming
> | *
> | * Full author contact details available in file CREDITS
> | */
The script below will modify existing "new style" headers to the format
above. I applied it successfully to files in src/graphics.
Angus
#! /bin/sh
for FILE in $*
do
SED=${FILE}.sed
cat - > ${SED} > ${SED} < ${TMP}
rm -f ${SED}
cmp -s ${FILE} ${TMP}
if [ $? -eq 1 ]; then
diff -u ${FILE} ${TMP}
mv -i ${TMP} ${FILE}
fi
rm -f ${TMP}
done
Re: On copyright
On Thursday 05 September 2002 08:18, Lars Gullik Bjønnes wrote: > You know, this style: > > /* > * \file GraphicsCache.C > * Copyright 2002 the LyX Team > * Read the file COPYING > * > * \author Baruch Even <[EMAIL PROTECTED]> > * \author Angus Leeming <[EMAIL PROTECTED]> > */ > > or a modification on it. Why not to replace "Read the file COPYING" with the following? * This program 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 * of the License, or (at your option) any later version. * * This program 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 this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. I would add this for most of the files whose license is GPL, we have some files that are in the public domain. This is the scheme that we have now for lyx2lyx and in part for reLyX. Also I always thought as bit confusing saying read COPYING, as that file doesn't exist in most directories. But maybe it is me. :-) Since we are talking about this we could do it in the full extension. :-) -- José Abílio
Re: On copyright
Andre Poenitz <[EMAIL PROTECTED]> writes: | On Thu, Sep 05, 2002 at 08:35:51AM +0200, Lars Gullik Bjønnes wrote: | > but it is a lot easier to remember to add self to the top of the very | > same file you are editing, instead of CREDITS or MAINTAIERS... | | But if you have to change it, it is easier to do in a single place, and its | showing "lower profile" for address harvesters. And faster to type... If you are afraid of address harvesters do not be on the net. as said "I can live with it" -- Lgb
Re: On copyright
Andre Poenitz <[EMAIL PROTECTED]> writes: | On Wed, Sep 04, 2002 at 07:29:04PM +0200, Lars Gullik Bjønnes wrote: | > "Copyright The LyX Team." | > | > As there is no real entity with this name. | > | > I would suggest that from now on, that everybody that does some | > substantial¹ work on a file, also add themselves to the copyright | > clause in the same file. (and we should move all files to "new style" | > headings.) | | And how does the new style look like? You know, this style: /* * \file GraphicsCache.C * Copyright 2002 the LyX Team * Read the file COPYING * * \author Baruch Even <[EMAIL PROTECTED]> * \author Angus Leeming <[EMAIL PROTECTED]> */ or a modification on it. -- Lgb
Re: On copyright
On Thu, Sep 05, 2002 at 08:35:51AM +0200, Lars Gullik Bjønnes wrote: > but it is a lot easier to remember to add self to the top of the very > same file you are editing, instead of CREDITS or MAINTAIERS... But if you have to change it, it is easier to do in a single place, and its showing "lower profile" for address harvesters. And faster to type... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: On copyright
Allan Rae <[EMAIL PROTECTED]> writes: | On 5 Sep 2002, Lars Gullik Bjønnes wrote: | | > Allan Rae <[EMAIL PROTECTED]> writes: | [...] | > | Centralising the email addresses etc. in CREDITS means we don't have | > | patches that touch heaps of files like Angus committed recently when | > | he changed his email address. Instead his script could just add a | > | line like: | > | | > | Full author contact details available in file CREDITS | > | > I can live with that as well. | > | > but it is a lot easier to remember to add self to the top of the very | > same file you are editing, instead of CREDITS or MAINTAIERS... | | Just so I'm perfectly clear: | | /* | * \file PreviewLoader.C | * Read the file COPYING | * | * \author Angus Leeming | * | * Full author contact details available in file CREDITS | */ | | So you still add yourself to the top of the file but only once need to | fill in an entry for CREDITS -- and then keep it updated as your | contact details change. | | You only have to remember your name when you have a CREDITS entry ;-) | Less typing too. As said, I can live with it. But I am not sure that this centralizing of information is good. -- Lgb
Re: On copyright
On Wed, Sep 04, 2002 at 07:29:04PM +0200, Lars Gullik Bjønnes wrote: > "Copyright The LyX Team." > > As there is no real entity with this name. > > I would suggest that from now on, that everybody that does some > substantial¹ work on a file, also add themselves to the copyright > clause in the same file. (and we should move all files to "new style" > headings.) And how does the new style look like? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: On copyright
On 5 Sep 2002, Lars Gullik Bjønnes wrote: > Allan Rae <[EMAIL PROTECTED]> writes: [...] > | Centralising the email addresses etc. in CREDITS means we don't have > | patches that touch heaps of files like Angus committed recently when > | he changed his email address. Instead his script could just add a > | line like: > | > | Full author contact details available in file CREDITS > > I can live with that as well. > > but it is a lot easier to remember to add self to the top of the very > same file you are editing, instead of CREDITS or MAINTAIERS... Just so I'm perfectly clear: /* * \file PreviewLoader.C * Read the file COPYING * * \author Angus Leeming * * Full author contact details available in file CREDITS */ So you still add yourself to the top of the file but only once need to fill in an entry for CREDITS -- and then keep it updated as your contact details change. You only have to remember your name when you have a CREDITS entry ;-) Less typing too. Allan. (ARRae)
Re: On copyright
Allan Rae <[EMAIL PROTECTED]> writes: | On 4 Sep 2002, Lars Gullik Bjønnes wrote: | | > Angus Leeming <[EMAIL PROTECTED]> writes: | [...] | > | Fair point. So your preferred heading is | > | | > | /* | > | * \file PreviewLoader.C | > | * Read the file COPYING | > | * | > | * \author Angus Leeming <[EMAIL PROTECTED]> | > | */ | > | | > | I believe that we decided it'd be a good thing to move the email address to | > | the CREDITS file too? | > | > But I won't object to having email also in the author section. | | Centralising the email addresses etc. in CREDITS means we don't have | patches that touch heaps of files like Angus committed recently when | he changed his email address. Instead his script could just add a | line like: | | Full author contact details available in file CREDITS I can live with that as well. but it is a lot easier to remember to add self to the top of the very same file you are editing, instead of CREDITS or MAINTAIERS... -- Lgb
Re: On copyright
On 4 Sep 2002, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: [...] > | Fair point. So your preferred heading is > | > | /* > | * \file PreviewLoader.C > | * Read the file COPYING > | * > | * \author Angus Leeming <[EMAIL PROTECTED]> > | */ > | > | I believe that we decided it'd be a good thing to move the email address to > | the CREDITS file too? > > But I won't object to having email also in the author section. Centralising the email addresses etc. in CREDITS means we don't have patches that touch heaps of files like Angus committed recently when he changed his email address. Instead his script could just add a line like: Full author contact details available in file CREDITS Allan. (ARRae)
Re: On copyright
On Wed, Sep 04, 2002 at 06:05:23PM +0100, Angus Leeming wrote: > On Wednesday 04 September 2002 6:29 pm, Lars Gullik Bj?nnes wrote: > > I belive that we have done ourselves a bad favour by use the > > "Copyright The LyX Team." > > As there is no real entity with this name. > I believe we haven't adone ourselves any harm because saying "copyright" in a > file is not defined as necessary by law. All that is important is that the > authorship is apparent. So our lines > \author Lars Gullik Bj?nnes > \author Angus Leeming > are sufficient statements of copyright. > We do have legal gurus out there however. Perhaps they'll chime in. I'm hesitant. Last time I did that, I contributed a couple grand worth of legal work, only to see it blotted out by someone who didn't understand the legal issues (in short, the status of the claimed license at the moment is dubious at best). Anyway, I believe that all countries "of consequence" now abide by the Berne convention, which gives copyright protection by the act of creation. It's not necessary to name who or what, or to label the code as copyrighted. However, these make it easier if there is ever a dispute or litigation. Using "the lyx team" makes me nervous--it does suggest an entity, and can lead to ugly litigation. No, I don't seriously think that there's a problem in the works, but it's the kind of messy can of worms that you pay lawyers to avoid. What would make me most comfortable? Incorporate a non-profit, assigning the current team as the directors/trustees/whatevers. I don't think the U.S. would be the best bet for this in the current legal climate. The potential probelm is that a group running around with a common purpose and label becomes the target to sue--and thre can be an argument that they're a partnership (or whatever). I think "lyx" would win, as I see no evidence of plans to share profits or losses (of what???), but again, I prefer to steer clear of messes ahead of time. -- Richard E. Hawkins, Asst. Prof. of Economics/"\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Wednesday 04 September 2002 6:49 pm, Angus Leeming wrote:
|
| > Would you like me to run this little shell script over LyX's .[Ch] files?
| >
| > #! /bin/sh
| >
| > for FILE in $*
| > do
| > DIR=`dirname ${FILE}`
| > BASE=`basename $1`
| > TMP=${DIR}/${BASE}.tmp
| > sed -e '/the LyX Team/d' \
| > -e '/\\author/s/\(.*\), \(.*\)/\1/' \
| > -e '/\\author/s/\(.*\) <\(.*\)>/\1/' \
| > < ${FILE} > ${TMP}
| > cmp -s ${FILE} ${TMP}
| > if [ $? -eq 1 ]; then
| > diff -u ${FILE} ${TMP}
| > mv -i ${TMP} ${FILE}
| > fi
| > rm -f ${TMP}
| > done
|
| Doing so results in the following headers to the files in src/graphics
| (attached). Is this what you're looking for?
Yes, something like that.
--
Lgb
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | On Wednesday 04 September 2002 6:41 pm, Lars Gullik Bjønnes wrote: | > | All that is important is that the | > | authorship is apparent. So our lines | > | \author Lars Gullik Bjønnes | > | \author Angus Leeming | > | are sufficient statements of copyright. | > | > Yes, but that information is missing now, so WE do not really know. | | Not really. We have cvs. Could you not write a script to interrogate all | submissions to a file? If more than 10 lines, then you're an author. You really belive that we have CVS logs back to day one :-) and 10 lines won't cut it... just think of my "fix ws" frenzies. | > For the sake of copyright per se, you do not even have to add your | > name as author to have full legal support for your copyright. | > | > | We do have legal gurus out there however. Perhaps they'll chime in. | > | > I guess that from a Copyright pow, the problem with "The LyX Team" | > kindo implies that we have transfered the copyright to that entity. | > (which is non-existing) | | Fair point. So your preferred heading is | | /* | * \file PreviewLoader.C | * Read the file COPYING | * | * \author Angus Leeming <[EMAIL PROTECTED]> | */ | | I believe that we decided it'd be a good thing to move the email address to | the CREDITS file too? But I won't object to having email also in the author section. -- Lgb
Re: On copyright
On Wednesday 04 September 2002 6:49 pm, Angus Leeming wrote:
> Would you like me to run this little shell script over LyX's .[Ch] files?
>
> #! /bin/sh
>
> for FILE in $*
> do
> DIR=`dirname ${FILE}`
> BASE=`basename $1`
> TMP=${DIR}/${BASE}.tmp
> sed -e '/the LyX Team/d' \
> -e '/\\author/s/\(.*\), \(.*\)/\1/' \
> -e '/\\author/s/\(.*\) <\(.*\)>/\1/' \
> < ${FILE} > ${TMP}
> cmp -s ${FILE} ${TMP}
> if [ $? -eq 1 ]; then
> diff -u ${FILE} ${TMP}
> mv -i ${TMP} ${FILE}
> fi
> rm -f ${TMP}
> done
Doing so results in the following headers to the files in src/graphics
(attached). Is this what you're looking for?
Angus
==> src/graphics/GraphicsCache.C <==
/*
* \file GraphicsCache.C
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
*/
#include
==> src/graphics/GraphicsCache.h <==
// -*- C++ -*-
/**
* \file GraphicsCache.h
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
*
* grfx::Cache is the manager of the image cache.
* It is responsible for creating the grfx::CacheItem's and maintaining them.
==> src/graphics/GraphicsCacheItem.C <==
/*
* \file GraphicsCacheItem.C
* Read the file COPYING
*
* \author Baruch Even
* \author Herbert Voss
* \author Angus Leeming
*/
#include
==> src/graphics/GraphicsCacheItem.h <==
// -*- C++ -*-
/*
* \file GraphicsCacheItem.h
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
*
* The graphics cache is a container of grfx::CacheItems.
* Each grfx::CacheItem, defined here represents a separate image file.
==> src/graphics/GraphicsConverter.C <==
/**
* \file GraphicsConverter.C
* Read the file COPYING
*
* \author Angus Leeming
*/
#include
#ifdef __GNUG__
==> src/graphics/GraphicsConverter.h <==
// -*- C++ -*-
/**
* \file GraphicsConverter.h
* Read the file COPYING
*
* \author Angus Leeming
*
* The controller of a conversion process from file AA of format A to
* file BB of format B.
* Once finished, a signal is emitted to inform any listeners (connected
==> src/graphics/GraphicsImage.C <==
/*
* \file GraphicsImage.C
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
* \author Herbert Voss
*/
#include
==> src/graphics/GraphicsImage.h <==
// -*- C++ -*-
/**
* \file GraphicsImage.h
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
*
* An abstract base class for the images themselves.
* Allows the user to retrieve the pixmap, once loaded and to issue commands
==> src/graphics/GraphicsImageXPM.C <==
/*
* \file GraphicsImageXPM.C
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
*/
#include
==> src/graphics/GraphicsImageXPM.h <==
// -*- C++ -*-
/**
* \file GraphicsImageXPM.h
* Read the file COPYING
*
* \author Baruch Even
* \author Angus Leeming
*
* An instantiation of Image that makes use of libXPM to load and store
* the image in memory.
==> src/graphics/GraphicsLoader.C <==
/*
* \file GraphicsLoader.C
* Read the file COPYING
*
* \author Angus Leeming
*/
#include
#ifdef __GNUG__
==> src/graphics/GraphicsLoader.h <==
// -*- C++ -*-
/**
* \file GraphicsLoader.h
* Read the file COPYING
*
* \author Angus Leeming
*
* The public face of the graphics cache.
*
* * The user supplies an image file and the display parameters.
==> src/graphics/GraphicsParams.C <==
/*
* \file GraphicsParams.C
* Read the file COPYING
*
* \author Angus Leeming
*/
#include
#ifdef __GNUG__
==> src/graphics/GraphicsParams.h <==
// -*- C++ -*-
/**
* \file GraphicsParams.h
* Read the file COPYING
*
* \author Angus Leeming
*
* Used internally by the grfx::Image.
*/
==> src/graphics/GraphicsSupport.C <==
/**
* \file GraphicsSupport.C
* Read the file COPYING
*
* \author Angus Leeming
*/
#include
#ifdef __GNUG__
==> src/graphics/GraphicsSupport.h <==
// -*- C++ -*-
/**
* \file GraphicsSupport.h
* Read the file COPYING
*
* \author Angus Leeming
*/
#ifndef GRAPHICSSUPPORT_H
#define GRAPHICSSUPPORT_H
==> src/graphics/GraphicsTypes.C <==
// -*- C++ -*-
/**
* \file GraphicsTypes.C
* Read the file COPYING
*
* \author Rob Lahaye
*/
#include "graphics/GraphicsTypes.h"
==> src/graphics/GraphicsTypes.h <==
// -*- C++ -*-
/**
* \file GraphicsTypes.h
* Read the file COPYING
*
* \author Angus Leeming
*
* All that header files outside the graphics subdirectory should need to
* access.
*/
==> src/graphics/PreviewImage.C <==
/**
* \file PreviewImage.C
* Read the file COPYING
*
* \author Angus Leeming
*/
#include
#ifdef __GNUG__
==> src/graphics/PreviewImage.h <==
// -*- C++ -*-
/**
* \file PreviewImage.h
* Read the file COPYING
*
* \author Angus Leeming
*/
#ifndef PREVIEWIMAGE_H
#define PREVIEWIMAGE_H
==> src/graphics/PreviewLoader.C <==
/*
* \file Previe
Re: On copyright
On Wednesday 04 September 2002 6:27 pm, Angus Leeming wrote:
> On Wednesday 04 September 2002 6:41 pm, Lars Gullik Bjønnes wrote:
> > | All that is important is that the
> > | authorship is apparent. So our lines
> > | \author Lars Gullik Bjønnes
> > | \author Angus Leeming
> > | are sufficient statements of copyright.
> >
> > Yes, but that information is missing now, so WE do not really know.
>
> Not really. We have cvs. Could you not write a script to interrogate all
> submissions to a file? If more than 10 lines, then you're an author.
>
> > For the sake of copyright per se, you do not even have to add your
> > name as author to have full legal support for your copyright.
> >
> > | We do have legal gurus out there however. Perhaps they'll chime in.
> >
> > I guess that from a Copyright pow, the problem with "The LyX Team"
> > kindo implies that we have transfered the copyright to that entity.
> > (which is non-existing)
>
> Fair point. So your preferred heading is
>
> /*
> * \file PreviewLoader.C
> * Read the file COPYING
> *
> * \author Angus Leeming <[EMAIL PROTECTED]>
> */
>
> I believe that we decided it'd be a good thing to move the email address to
> the CREDITS file too?
Would you like me to run this little shell script over LyX's .[Ch] files?
#! /bin/sh
for FILE in $*
do
DIR=`dirname ${FILE}`
BASE=`basename $1`
TMP=${DIR}/${BASE}.tmp
sed -e '/the LyX Team/d' \
-e '/\\author/s/\(.*\), \(.*\)/\1/' \
-e '/\\author/s/\(.*\) <\(.*\)>/\1/' \
< ${FILE} > ${TMP}
cmp -s ${FILE} ${TMP}
if [ $? -eq 1 ]; then
diff -u ${FILE} ${TMP}
mv -i ${TMP} ${FILE}
fi
rm -f ${TMP}
done
Results like:
aleem@pneumon:devel-> sh rmcopyright.sh src/graphics/*.[Ch]
--- src/graphics/GraphicsCache.CWed Jul 17 17:13:20 2002
+++ src/graphics/GraphicsCache.C.tmpWed Sep 4 19:20:05 2002
@@ -1,10 +1,9 @@
/*
* \file GraphicsCache.C
- * Copyright 2002 the LyX Team
* Read the file COPYING
*
- * \author Baruch Even <[EMAIL PROTECTED]>
- * \author Angus Leeming <[EMAIL PROTECTED]>
+ * \author Baruch Even
+ * \author Angus Leeming
*/
#include
overwrite src/graphics/GraphicsCache.C?
Re: On copyright
On Wednesday 04 September 2002 6:41 pm, Lars Gullik Bjønnes wrote: > | All that is important is that the > | authorship is apparent. So our lines > | \author Lars Gullik Bjønnes > | \author Angus Leeming > | are sufficient statements of copyright. > > Yes, but that information is missing now, so WE do not really know. Not really. We have cvs. Could you not write a script to interrogate all submissions to a file? If more than 10 lines, then you're an author. > For the sake of copyright per se, you do not even have to add your > name as author to have full legal support for your copyright. > > | We do have legal gurus out there however. Perhaps they'll chime in. > > I guess that from a Copyright pow, the problem with "The LyX Team" > kindo implies that we have transfered the copyright to that entity. > (which is non-existing) Fair point. So your preferred heading is /* * \file PreviewLoader.C * Read the file COPYING * * \author Angus Leeming <[EMAIL PROTECTED]> */ I believe that we decided it'd be a good thing to move the email address to the CREDITS file too? Angus
Re: On copyright
Angus Leeming <[EMAIL PROTECTED]> writes: | On Wednesday 04 September 2002 6:29 pm, Lars Gullik Bjønnes wrote: | > I belive that we have done ourselves a bad favour by use the | > | > "Copyright The LyX Team." | > | > As there is no real entity with this name. | > | > I would suggest that from now on, that everybody that does some | > substantial¹ work on a file, also add themselves to the copyright | > clause in the same file. (and we should move all files to "new style" | > headings.) | > | > ¹ a tiny bit more than obvious and trivial stuff | | I believe we haven't adone ourselves any harm because saying "copyright" in a | file is not defined as necessary by law. Yes, this is true in most (or perhaps just several) countries. | All that is important is that the | authorship is apparent. So our lines | \author Lars Gullik Bjønnes | \author Angus Leeming | are sufficient statements of copyright. Yes, but that information is missing now, so WE do not really know. For the sake of copyright per se, you do not even have to add your name as author to have full legal support for your copyright. | We do have legal gurus out there however. Perhaps they'll chime in. I guess that from a Copyright pow, the problem with "The LyX Team" kindo impllies that we have transfered the copyright to that entity. (which is non-existing) -- Lgb
Re: On copyright
On Wednesday 04 September 2002 6:29 pm, Lars Gullik Bjønnes wrote: > I belive that we have done ourselves a bad favour by use the > > "Copyright The LyX Team." > > As there is no real entity with this name. > > I would suggest that from now on, that everybody that does some > substantial¹ work on a file, also add themselves to the copyright > clause in the same file. (and we should move all files to "new style" > headings.) > > ¹ a tiny bit more than obvious and trivial stuff I believe we haven't adone ourselves any harm because saying "copyright" in a file is not defined as necessary by law. All that is important is that the authorship is apparent. So our lines \author Lars Gullik Bjønnes \author Angus Leeming are sufficient statements of copyright. We do have legal gurus out there however. Perhaps they'll chime in.
On copyright
I belive that we have done ourselves a bad favour by use the "Copyright The LyX Team." As there is no real entity with this name. I would suggest that from now on, that everybody that does some substantial¹ work on a file, also add themselves to the copyright clause in the same file. (and we should move all files to "new style" headings.) ¹ a tiny bit more than obvious and trivial stuff -- Lgb
Re: [PATCH] KDE copyright
>>>>> "John" == John Levon <[EMAIL PROTECTED]> writes: John> This patch just moves John> copyright over to qtarch to fit with the others. Applied. JMarc
[PATCH] KDE copyright
This patch just moves copyright over to qtarch to fit with the others. If some applies it, please do cvs delete src/frontends/kde/dlg/formcopyrightdialog.kdevdlg as well thanks john -- "The HP-UX CC compiler cannot handle two consecutive semicolons. It is a silly compiler." - kdeveloper.org copyright.tar.gz
Re: copyright of files
Juergen Vigna <[EMAIL PROTECTED]> writes: | > @author Lars Gullik Bjønnes | | So should we use this tag in the File-Header? ?? E.. now (I tink...) You put that in the class documentation just as I showed in my example. Lgb
Re: copyright of files
> @author Lars Gullik Bjønnes So should we use this tag in the File-Header? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ The entire CHINESE WOMEN'S VOLLEYBALL TEAM all share ONE personality -- and have since BIRTH!!
Re: copyright of files
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 16-Aug-2000 Lars Gullik Bjønnes wrote:
|
| > I agree.
| > But we really sshould add author tags to all global functions and
| > classes.
|
| Agreed! How would you add them (I don't know if there is a doc++ way to
| do this)?
/** Short description.
Long description that can go over several lines.
@author Lars Gullik Bjønnes
@version 1.0 Aug 16. 2000
*/
class FooBar {};
http://www.linuxsupportline.com/~doc++/
To download + documentation.
Lgb
Re: copyright of files
On Wed, 16 Aug 2000, Juergen Vigna wrote: > Is it normal behaviour to copyright files created by someone to him? I > just saw that we have files copyright to Lars and Allan (and may be > some more). > > If so should I copyright all files created by me? I have studied the matter a little bit and my conclusios are that: 1. You own the copyright of something even if you don't add an explicit copyright statement. A software doesn't have an explicit statement is NOT free by default. 2. If you don't want that something have a copyright then you must explicitly release it under public domain. 3. You are allowed to assign the copyright of your creation to anyone else. In your particular case, the LyX team. 4. Authorship should not be confused with copyright: you may be the author of a software and don't own it's copyright. 5. The above cases may be restricted by some local law or by agreements between you and your employer. Of course, these are my personal opinions and I'm not a member of the LyX development group. -- Carlos A. M. dos Santos Federal University of Pelotas Meteorological Research Center Av. Ildefonso Simoes Lopes 2791 Pelotas, RS, Brasil, CEP 96060-290 WWW: http://www.cpmet.ufpel.tche.br RENPAC (X.25): 153231641 Phone: +55 53 277-6767FAX: +55 53 277-6722
Re: copyright of files
On 16-Aug-2000 Lars Gullik Bjønnes wrote: > I agree. > But we really sshould add author tags to all global functions and > classes. Agreed! How would you add them (I don't know if there is a doc++ way to do this)? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ union, n.: A dues-paying club workers wield to strike management.
Re: copyright of files
Juergen Vigna <[EMAIL PROTECTED]> writes: | P.S.: I really think the Copyright to the LyX-Team IS enough! I agree. But we really sshould add author tags to all global functions and classes. Lgb
copyright of files
Hi! Is it normal behaviour to copyright files created by someone to him? I just saw that we have files copyright to Lars and Allan (and may be some more). If so should I copyright all files created by me? Jürgen P.S.: I really think the Copyright to the LyX-Team IS enough! -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ I don't kill flies, but I like to mess with their minds. I hold them above globes. They freak out and yell "Whooa, I'm *way* too high." -- Bruce Baum
[PATCH] KDE Copyright actual patch
May pine be cursed ! Patch attached. sorry john -- "Love your country, but never trust its government." - Robert A. Heinlein formcopyright.diff.gz
copyright
Whatever you do with the license, LyX should probably output "(C) 1995-1999". It's currently writing 1998. What if someone takes the code and says we lost the copyright?! OK, it won't happen, but still. I would do the patch myself, but I'm too scared to touch anything with a .C suffix (and now that I can sleep, I might get nightmares). -Amir
