[Bug 430307] Review Request: Falcon - The Falcon Programming Language

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: Falcon - The Falcon Programming Language


https://bugzilla.redhat.com/show_bug.cgi?id=430307





------- Additional Comments From gc at falconpl.org  2008-02-18 18:14 EST -------
About 5d it just states that it must be said somewhere in the docs, on the site,
in the program screens, in the readme files, in the troubleshooting guide or
wherever you like that the scripts were falcon. I think it's a very small
constraint, if relevant at all, and it's meant to protect the final user from  
                                                                          
concealing this information (that may be relevant to him) and the Falcon project
from unauthorized commercial (i.e. closed source) exploitation. If you are using
a C compiler you're compiling to object code, but if you're using a script
you're using a virtual machine, and it may be a good idea for your users not to
be spoiled from the right of knowing what they are running on their machines.

I didn't want to deprive Falcon script writers of the ability to distribute
commercial closed source applications, but in that case, I didn't want the fact
of using Falcon to be obfuscated so that the end user didn't possibly know.

I think this goes along OSI guidelines (certification process started), but it's
a bit forceful on radical free software concept of FSF.

In case they ask, I can give the grant to Fedora users to pick up FSF GPL3 or
any later or Falcon FPLL license, wichever they prefer. Falcon's is just less
restrictive, so it's their call.

(actually, if they ask I can provide double licensing directly for Falcon
itself. I don't mind if the users select a more restrictive license on their own
will).


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.