Hi Jon, I apologize for being persnickety here, but I am searching for clarity and consistency on this issue.
Has the JSBSim project asked permission from all the aircraft manufacturers that you create and distribute models for? If not, have you only dealt with Boeing in terms of asking for and receiving permission? If you've only received permission from one company, then why? I assume it's because they contacted you and forced this issue. In any case, why is it ok to proceed with explicit permission from Boeing, and at the same time ok to proceed *without* explicit permission from every other aircraft manufacturer on the planet? If it's ok for JSBSim to proceed without permission from most companies, then why suggest that FlightGear should get permission before we model aircraft from various manufacturers with logos representing various owners of specific aircraft? I don't understand. By my reading of your messages, I feel like you are making ethical comments (or perhaps suggestions would be a better word) related to the actions of the FlightGear project without applying that same standard consistently to the JSBSim project? I don't see how (from a logical perspective) that getting permission from one aircraft manufacturer exempts you from asking for permission (and not proceeding without it) for any other aircraft manufacturer. And this is my difficulty with everyone who is arguing that FlightGear should get permission before modeling any aircraft or liveries ... I don't see any consistent application of these suggestions or any way to consistently apply anything close to them without either (a) gutting our project, or (b) acting in ways that would be completely inconsistent with these hypothetical policies. I'm not trying to be a PITA here, just trying to understand ... Thanks, Curt. On Sat, Feb 26, 2011 at 3:06 PM, Jon S. Berndt wrote: > As you may recall, a few years ago myself and at least one other JSBSim > developer did have an event that caused us to look over our "operating > procedures" - and I won't go into the details, but suffice it to say that > it > was not a pleasant experience, although it turned out OK and in my case I > was apologized to for the inconvenience. I never did figure out the exact > reason why I was contacted and "questioned." > > As you may also recall I did post the correspondence I received from Boeing > IP personnel here in this thread a couple of weeks ago. It was that > response > that lead us to reevaluate our process and to withdraw some aircraft models > from distribution for a while. We then added some disclaimers and > statements > in most of them and made sure that our data was traceable to public > sources. > > We have it much easier than FlightGear does, since the reference to an > aircraft "type" using the company name (such as "Boeing 737") is far > different than the use of a trademark or logo - particularly for a logo. > > I can't tell you guys what to do, but if it was me I would take maybe one > of > two approaches: > > 1) Make a README file that contains an appropriate disclaimer and > distribute that with each model. I don't know what that disclaimer would > state. > 2) Continue as if nothing had changed, but contact the various > trademark/logo owners and very carefully inform them of the project and ask > them for permission. > > In any case, I strongly suspect that the worst that can happen is that if a > company takes issue with the unauthorized use of its IP it will simply ask > that further use be discontinued and that will be the end of it. > > Jon > > > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT > data > generated by your applications, servers and devices whether physical, > virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/<http://www.flightgear.org/blogs/category/personal/curt/>
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
