[pacman-dev] Time for changes

[VMiklos]

On Wed, Oct 04, 2006 at 10:22:34AM -0700, Judd Vinet <jvinet at zeroflux.org> wrote:
> Here are my thoughts -- all in all, I would like to retain the
> copyright to pacman.  I worked hard on it for a number of years and I
> think I deserve it.  With that said, people like you, Aaron, Christian,
> and Aurelien certainly deserve credit for large portions of the code
> and what it can do today.  This is what I want the AUTHORS file to say,
> and prominently.  We can also reference it on the pacman website and in
> the README file.  It is not my intention to hide the fact that I had
> help with the project, because I did have a lot of help.

okay, so you would like to have the same header for each file and your
copyright from 2002 to 2006. what about the follwong:

/* foo.c - This file is part of Pacman, see the COPYRIGHT file for more
 * information */

then all the names could be listed there

> But if the day comes where a big decisions needs to be made that only
> the copyright holder can make, I wouldn't want to be bogged down by a
> game of who-wrote-what -- I think that could tear the project apart.

if there are several authors, then the license can be changed to an
other one in case all the copyright holders agree about the change,
which is almost impossible. currently (yes, of course i really hope this
will never happen :) ) if you go crazy and change the license, then you
can do it, so the license of my own code is not guarantated. i hope you
can see the problem

> Again, I think the lack of Linus' name on some files is due to the
> crazy modularity of the kernel.

hopefully we will have backends other than 'files' and then we'll have
crazy modules, too :)

> Let me take this opportunity to thank you, Christian, and the other
> developers at Frugalware for your hard work on pacman.

i'm happy to contribute :)

so, i don't plan to revert the copyright updates in our tree, but in
case something is changed in the cvs (somehow we're listed as copyright
holders) then of course i'll pull that change and drop our copyright
fixes. and again, this whole "copyright thingy" from my part is about to
be able to control under what license is my code distributed, not about
hurting you in any way

udv / greetings,
VMiklos

-- 
Developer of Frugalware Linux, to make things frugal - http://frugalware.org