To: Theodore Tso <tytso@...>, Can E. Acar <can.acar@...>, Claudio Jeker <cjeker@...>, Adrian Bunk <bunk@...>, <misc@...>, <linux-kernel@...>, Daniel Hazelton <dhazelton@...>, Eben Moglen <moglen@...>, Lawrence Lessig <lessig_from_web@...>, Bradley M. Kuhn <bkuhn@...>, Matt Norwood <norwood@...>
Yes, quite an improvement, considering how it all started, dont you think?
Pity it took so much pushing and dragging to get people to do the right
thing.
There is just one little step to go. It is can not be that hard, can it?
As a programmer, you sure would know what difference any "two lines"
would make on your program. When it comes to law, you seem to lose
that intuition.
Well, they can add their names *anywhere* in the whole file, *except*
these two lines. See, these lines have a whole different meaning
when it comes to laws. When they make sufficient contribution, they
sure can add their names. What is so difficult to understand here?
I have seen some academic papers, where the first author did all the work,
the second author is the professor who funded the work, and the remaining
five "authors" are just coming along for a ride. You know what the
difference is? The original author *allows* them to put their names as
authors.
Here, you are adding names, and say "why not". It is both unethical and
illegal.
As long as it is not a derived work, Reyk gets to decide who is in the
copyright. Even if it is a derived work, it is polite to ask.
If, at the beginning, Nick and Jiri, and others asked Reyk to be included
in the Copyright for the adaptation work they did on the HAL. I do not
believe he would have refused. I can not talk for him, but things would
be have been resolved in a much nicer and positive way.
Instead they chose to push Reyk for months to dual license his code,
then attempted to change the whole license. Even now, when there is
just a small issue left, people are still dragging and resisting.
I am really disappointed by all this. I would have expected that once
such a patch is suggested (let alone being committed to some public place)
some senior/respected/responsible Linux person would tell them what they
are doing is wrong. Right from the start. I now see this is not how
things work around here. Senior developers are either too busy or
reluctant to get their hands dirty. In OpenBSD, (which, I accept is a
much smaller community) when one developer does something wrong,
the clue stick is there to be used by one of the more experienced
developers.
Which means, issues are resolved quickly and with much less pain.
Can
--
In theory, there is no difference between theory and practice.
But, in practice, there is.
-
