On Wed, 21 Jan 2009 18:21:50 -0600, Jon wrote in message
<003501c97c27$6d008850$470198...@net>:
> > We may go on to keep our model and our code protected under GPL
> > license.
> >
> > Only an information regarding the copyright for such private Name:
> > Boeing..Lockheed.. and so on could be necessary.
> >
> > These addons won't be a restriction only an information.
> >
> > Cheers
>
>
> To be absolutely clear, here is the correspondence I had earlier this
> year:
>
> --- start my email ---
>
> Greetings,
>
> I am the project lead of the open source (free) software library
> called, JSBSim. We use this software to simulate the flight of
> aircraft. We also create data files that contain presumed
> characteristics of the vehicle (weight and balance, engines,
> controls, aerodynamics, etc.). All data comes from publicly
> available, traceable, sources. None of our aircraft models are sold.
> They are all freely available.
>
> We have recently been discussing whether or not we are allowed to
> call our aircraft models a "Boeing 737", or even simply a "737"
> model. What limitations are there on the use of the name "Boeing" in
> this situation, or the use of the aircraft type name, "737"? Would we
> be allowed to use the aircraft type name and/or company name if we
> had a disclaimer in the data file, such as:
>
> "This simulation model of a Boeing 737 aircraft was created using
> publicly available data, publicly available technical reports,
> textbooks, standard textbook aeronautical relationships, and
> "guesstimates", and possibly even results from the DATCOM tool. It
> contains no proprietary or restricted data. It has been validated
> only to the extent that it seems to "fly right", and possibly to
> conform to published, publicly known, performance data (maximum
> speed, endurance, etc.). Thus, this model is meant for educational
> and entertainment purposes only. This simulation model is not
> endorsed by the manufacturer."
>
> Best regards,
>
> Jon Berndt
> Chief Architect and Development Coordinator
> JSBSim Project
> www.jsbsim.org
> League City, TX
>
> --- end my email ---
>
> And the reply is as follows:
>
> --- start reply ---
>
> Hello Jon,
>
> Thank you for your inquiry regarding use of Boeing trademarks.
>
> Since it appears as though JSBSim will use the product identifiers
> (e.g..Boeing 737) in a descriptive manner, and no profit will be
> derived from said usage, then we have no objection to inclusion of
> the product identifiers on the software.
..all fine all the way down here. :o)
..now, ...
> However, if a situation
> arises in which the aircraft models are to be sold for a profit,
> please contact us to discuss implementation of a Trademark License
> Agreement for the sale of consumer products.
..no F-g way, they add a restriction beyond the GPL,
toss out all Boeing models and replace them all with
similar Airbus, Tupolev, Antonov, Shin-Meiwa, Harbin,
Dornier, Short etc models. And do it LOUDLY. ;o)
..if we need any similar things for historical reasons,
call them by their proper names historical names, e.g.
"the Gimli Glider." ;o)
..let Boeing sell their own JSBSim, FG etc models under
their own GPL-compliant license. ;o)
> Please be advised that inclusion of the Boeing logo on any JSBSim is
> not compliant with our Corporate Brand Strategy, and is not approved.
..all fine with that rejection.
> We have no objection to the proposed disclaimer provided, and prefer
> that it is used.
..all fine with that disclaimer.
> Sincerely,
>
> {name removed}
> Intellectual Property Licensing
> Boeing Intellectual Property Management
> (xxx) xxx-xxxx
> (xxx) xxx-xxxx
--
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
