On Tue, Jan 31, 2012 at 8:05 PM, Tito <[email protected]> wrote:
> Hi,
> just to post a link to this article about a non-GPL busybox replacement
> http://lwn.net/Articles/478249/
>
> Ciao,
> Tito
I think there are two main points about this:
The first is that I agree with Tim that suspending the license is a
big issue for any company wishing to ship busybox,
much more so if all of their other unrelated products are held
hostage. Any litigation regarding busybox should remain
confined to the offending product and the enforcement of busybox
itself only. Also, the companies by themselves taking
the steps to amend and make the product compliant should be sufficient
to have the license reinstated and the legal
matter dropped.
Second point is that any decision regarding whether to sue or not
should take into consideration what we want in return,
and also the overall costs involved.
A small list of things we (?) may want in return, in order of importance:
1) Code
Does the product in question ship a patched busybox at all? Is
there any reason to believe that?
If not, then no reason to ask them to release it anyway just
for self-gratification.
Is the modification big enough to warrant all the costs and
manpower wasted in the process?
If Denys or anyone else could reimplement it in a few hours,
then it's hardly worth all the fuss.
Do we even care about the modifications at all?
The changes could be one big ugly hack, out of the scope, and
all other reasons
why patches get rejected here in this mailing list.
2) Recognition
This is a more reasonable demand, as it's much much easier to
comply, easier to understand and
appreciate the motive behind it. The companies would probably not
put themselves at any disadvantage by doing this.
I suspect requesting to comply with this would hardly go as far as
into court.
Now, to see in which position this would put busybox, my question is,
what has been gained so far from suing?
Any code? Which code?
Authorship recognition? Has this even been an issue?
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
