[EMAIL PROTECTED] (Bruce Perens) wrote on 21.05.97 in <[EMAIL PROTECTED]>:
> Take the public domain part and put it in one package. Take the
> non-free part and put it in another package. You already knew this but
> I said it as context for the following:
>
> Contact the author and ask them to i
Take the public domain part and put it in one package. Take the
non-free part and put it in another package. You already knew this but
I said it as context for the following:
Contact the author and ask them to issue the following more-legaly-correct
license _only_ on the public domain part:
Joey Hess <[EMAIL PROTECTED]> writes:
> This all seems ok except for maybe the export restrictions section. We don't
> have a non-Cuba-Yugoslavia-Hati-Iran-Iraq-North-Korea-and-Syria section like
> we have a non-us section.. so does abuse belong in non-free or on some
> us-only ftp site, or what?
Jim Pick:
> > Restrictions :
> >Crack dot Com retains ownership of the Abuse Trademark and data sets.
>
> What does data sets mean?
I think it means the levels, sounds, artwork, etc that the abuse engine
uses.
> Sounds like the libs can go into the free section. Cool.
If by "libs" you mea
> Crack dot Com has decided to release abuse as public domain software. So no
> more a.out abuse, once I get the new one built. But I do have a couple of
> questions about their copyright:
>
> This release is to the public domain, meaning there are very few
> restrictions in on use. But here a
Crack dot Com has decided to release abuse as public domain software. So no
more a.out abuse, once I get the new one built. But I do have a couple of
questions about their copyright:
This release is to the public domain, meaning there are very few
restrictions in on use. But here are a few :
6 matches
Mail list logo
