Excellent. That is exactly what is needed - good clear advice direct from the
source. It does appear they're not willing to allow anyone to use elements of
copyrighted works in any 'visible' aspects of the models, so that would present
some difficulty when it comes to re-creating liveries - at least it is better
to
know this than to not know...
Regards,
Chris Wilkinson, YBBN/BNE.
________________________________
From: Jon S. Berndt <jonsber...@comcast.net>
To: FlightGear developers discussions <flightgear-devel@lists.sourceforge.net>
Sent: Fri, 18 February, 2011 11:43:52 AM
Subject: [Flightgear-devel] Logos and licensing
Chris’ point is well-taken.
If in doubt – in fact, even if not in doubt – it’s good to ask.
Here’s an actual data point.
There was an “event’ a few years ago that lead me to inquire with Boeing about
the use of their company name in identifying certain aircraft that had been
modeled in JSBSim and distributed with the source code. This was the response I
got:
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. 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.
Please be advised that inclusion of the Boeing logo on any JSBSim is not
compliant with our Corporate Brand Strategy, and is not approved.
We have no objection to the proposed disclaimer provided, and prefer that it is
used.
Sincerely,
Now, we (JSBSim) don’t have a problem with this since we don’t use the Boeing
logo anywhere. I understand that this does open a huge can of worms.
We’ve taken the step of putting a disclaimer in each aircraft model.
Jon
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
