Hi Michael,
I would like to elaborate a bit about your comments:
ownership versus credit. I think there are some legal
issues here.
If you work for the company and you patented something,
the company owns the patent, but you still own your name
on the patent. Company cannot change it, otherwise the
patent will be invalidated.
Sun owns the code, but I think they don't own the name of
the person who produced that code. They cannot change it.
I am not sure that Sun's community license and even GPL pay
enough attention to the name ownership. Otherwise, we would
not have "GNU/Linux" discussion, because both use GPL. Code
released under the developer's name promotes the developer
and makes him/her more responsible for it.
Michael Young gave his IPO shares to some Linux developers years
after they did their work. It created good precedent for Blackdown
team. Who knows, may be McNealy is going to do something like that
in the future?
Jacob Nikom
Michael Thome wrote:
>
> Just wanted to say that I'm *really* pleased with 1.2.2RC2, and I'm
> sure that the rest will be even better. I've been running RC2 with
> native threads on an SMP machine (2xPIII-500) with 2.3-series kernel
> without a hitch - *very* nice. Worth the wait, guys!
>
> It appears that the whole blackdown/sun/inprise debacle really was a
> case of multiple miscommunication - it is unfortunate, but such
> problems often occur when organizations with such different goals and
> restrictions interface. I sure hope that everyone calms down and does
> the right thing by the others... while there is plenty of blame to go
> around, it just isn't productive.
>
> Re: author credit vs the SCSL... There are two issues here: ownership
> and credit. While it is true that under the SCSL, Sun may *own*
> derivative works, failure to cite the authors of such work is simple
> plagiarism. It is intellectual dishonesty to claim authorship of
> someone else's works, even if you own rights of distribution. That
> said, it appears that Sun has done a pretty reasonable job at
> assigning due credit in their recent PRs.
>
> -mik
> --
> Michael Thome ([EMAIL PROTECTED])
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
