An idea about the license problem

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

An idea about the license problem

Chris Cunnington-5

How about "The Add A Comment Campaign"?

Finding people is hard, and dealing with them is worse. So forget the people
who wrote the code. They don't matter.

What we need is a list of the pieces of code that need to be accounted for.
With that list we can address the problem. All those pieces of code need to
be modified, and new initials left to cover over the older author.

The easiest modification (thank you Ron T. for your expressing your
trepidation about modifying the code) is to leave a comment. In the code.
With quotation marks.

Thus all the pieces of rouge-owned code get modified by people we can get to
sign the form. Voila.

Give me a list of all the pieces in Squeak, and I'll assign them to
volunteers willing to leave ten comments apiece. If their are five hundred
pieces that need to be changed that's fifty volunteers.

And if you think this is a facile solution, then I request you define the
word "rewrite" and ask who's going to adjudicate the level of
"rewritedness"?

At the very least create a list of code that needs to be re-owned and forget
the list of people who wrote it. They're long gone, man.


Chris  


Reply | Threaded
Open this post in threaded view
|

Re: An idea about the license problem

Hilaire Fernandes-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Cunnington a écrit :

> How about "The Add A Comment Campaign"?
>
> Finding people is hard, and dealing with them is worse. So forget the people
> who wrote the code. They don't matter.
>
> What we need is a list of the pieces of code that need to be accounted for.
> With that list we can address the problem. All those pieces of code need to
> be modified, and new initials left to cover over the older author.
>
> The easiest modification (thank you Ron T. for your expressing your
> trepidation about modifying the code) is to leave a comment. In the code.
> With quotation marks.
>
> Thus all the pieces of rouge-owned code get modified by people we can get to
> sign the form. Voila.
>
> Give me a list of all the pieces in Squeak, and I'll assign them to
> volunteers willing to leave ten comments apiece. If their are five hundred
> pieces that need to be changed that's fifty volunteers.
>
> And if you think this is a facile solution, then I request you define the
> word "rewrite" and ask who's going to adjudicate the level of
> "rewritedness"?

Right, without mentioning the last initial may not be from the one
bringing the "significant" code change.

>
> At the very least create a list of code that needs to be re-owned and forget
> the list of people who wrote it. They're long gone, man.

I also fell it is pretty "safe" to do it that way.
And frankly, I don't think the eventual individual copyright owner are a
 problem or will attempt any lawsuit. And if so, the code can be removed
at this moment.
If there are problem we could be afraid of, it could come from the post
Apple era when Squeak was "hosted" at Dysney and HP.


Hilaire

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHWSl6SAvrR6lz6PQRAlTzAJ9pe5OVy8G/oohUMxlLvotC1zlzdQCgq9tf
4Hs45QFQ7TUFwZFQ3bTFRB0=
=fc4w
-----END PGP SIGNATURE-----