This shouldn't need to devolve into an argument, nor do we need to carry
over petty bickering from the forum. Let us put all that aside and just
focus on the facts. We must honor the GPL. That is central to the entire
existence of FlightGear.
If there is non-gpl compatible copyrighted content included in various
aircraft, we simply have to suck up our ego and fix the problems. Let's
not try to deflect the attention elsewhere. I'm sure if we dig we can find
other issues to distract ourselves with, but we must address the issues in
front of us that we do know about.
For me, this is what it boils down to:
Every one makes mistakes; that is part of life. We need to allow for that
in our dealings with each other and not come down too hard on each other.
I think what is important is how we deal with those mistakes; that is the
more important characteristic.
I see a couple options here now that potential issues have been discovered
and brought to the public attention.
1. We could discuss (reasonably!) if these are indeed GPL/Copyright
violations or not -- and this would need to be on a case-by-case basis I
suppose.
2. If it is clear to everyone that there are indeed real issues here, then
we need to focus on those and fix them -- not argue about other things.
In terms of fixing the problems I would propose giving the original author
a reasonable time frame to address the issue. Like I said, we all make
honest mistakes and we should be given a reasonable opportunity to address
them.
If there is a good faith intention to fix the problems, but we run out of
time before the v2.6.0 release, we could simply leave those identified
aircraft out of the release/distribution until the problems can be fully
resolved.
I thing we should assume the best of intentions and proceed in good faith
here. Emmanuel (and others if they would choose to contribute) should be
given some reasonable time address these specific issues, or defend the
usage of the material in question.
At the end of all this we have to put aside all the arguments and
distractions and focus on making sure any problems with the GPL are cleaned
up before the next release so we will be able to include these aircraft.
Best regards,
Curt.
On Sat, Jan 14, 2012 at 9:15 AM, Pierre Mueller <pierre.muel...@ymail.com>wrote:
> Dear Emmanuel BARANGER,
>
> >First point, when you want to criticize and criticize only, it is best
> >to write correctly. My name is Emmanuel BARANGER.
>
> O.k. I'm sorry for that mistake. And I'm surprised to see that your
> surname is captilized. I didn't know that it is possible in France, so I
> wasn't aware of it.
>
> >6, or 8 airplanes on 203..... It enough that you send free files for
> >replacement. Always wait for others to do is not the answer!
>
> >The interest of free, it is precisely that, normally, instead of be
> >scandalized, just to denigrate people, anyone can modify the data and
> >correct errors. If you are not able to do, so do not come drool on other.
>
> Sorry again, but I thought YOU are are the author and the maintainer. At
> least you created the mentioned aircraft, so I held YOU for being
> responsible for the mentioned aircraft.
>
> >I explained to you (on forum) that GIT was a place of development. The
> >files referred to are of course just for the present development. It
> >seems that you have cares of understanding and your favorite hobby is
> >the critical. This is not constructive.
>
> First: I'm a User. I have understanding of licences due to many reasons
> and some little understanding how OSS works, but not in creating an
> aircraft .
>
> So do I have to be a developer to critize?
> Aren't users allowed to critize and make aware of bugs, errors, mistakes
> done with and without intention?
> And how can users like me find out how to make remove things like the
> mentioned images, sounds etc.?
> Shoulden't be it enough to say: please Dear Mr. BARANGER- Please remove
> the mentioned files, as you violating copyrights with?
>
> Second: with pushing your things into GIT and on your homepage you made
> them publicly available. All licences do not care about things being in
> developement- if you take protected things without permission and
> redistribute them, you are infringing the copyrights.
>
> And as I understood the developement process of FlightGear, all things in
> FGdata (=GIT?) are freezed and and packaged without further modifications,
> and again made publicly available.
>
> So there is a not so small chance that FGFS-Project can be made
> responsible for violating copyrights by redistributing copyrighted images
> and sound snapshots used in the aircraft available on the
> FGFS-Official-Downloadpage. And as I don't see any Disclaimer on the
> Download page or anywhere else, that FGFS-Project is not responsible for
> the content they provide, it could be a nice invitation for some lawyers
> who wants to earn more money.
>
>
> >I am really tired of all these people who, instead of acting, prefer
> >disparage, criticize, drooling on the authors etc. ..... It's really
> >pathetic.
>
> No, the way critism handled here is pathetic.
>
> As I said, there was no offense meant, but it seems to me you feel
> yourself personaly attacked. Sorry, that's not what I wanted, but making
> you aware of having done mistakes with using the copyrighted things.
>
> With my Aircraft review on the forum I also gave you tips for improving
> your aircraft- a pity that you can't use it.
>
> Maybe someone others here on the mailing-list can explain the developement
> process of FGFS written in the FGFS-wiki to me again, so I can sure that I
> said above about the developement process is correct.
>
> Kind Regards
> Pierre Mueller
> Switzerland
>
>
> <http://helijah.free.fr>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> _______________________________________________
> 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://gallinazo.flightgear.org
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
