Re: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
Hi Emmanuel, may I remind you that the release deadline is little more than a week away and that this license violation (see below) is still in Git? Could you please cooperate with George to get the license sorted out? Else we'll have to remove it from Git before the freeze. (actually we should already, but I guess the rest of us was kind enough to give you some time to fix the issue; please use that time). Cheers, Gijs From: emili...@gmail.com Date: Wed, 19 Dec 2012 22:51:50 +0200 Subject: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4 The DR400 Guide (Aircraft/DR400/DR400 Guide.pdf) commited in this has a non-GPL compatible license (All rights reserved). I think this situation needs to be fixed (either the guide removed, or a proper GPL version of the guide is pushed) I think it would be a good idea if contributors would check more thoroughly the licenses of third party material commited. Relevant links: https://gitorious.org/fg/fgdata/blobs/master/Aircraft/DR400/DR400 Guide.pdf http://flightgear.org/forums/viewtopic.php?f=4p=172822#p172818 -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
Hangars are discussed in the wiki article actually ( http://wiki.flightgear.org/FlightGear_Git:_splitting_fgdata#Per-aircraft_project ) . That's why I pointed to it. Lots of ideas that show up on the mailinglist have been discussed in the past and the outcome of those discussions is mentioned at the wiki. First reading the wiki before sharing your own (good) ideas or opinions saves everyone's time, not at the least yours ;-) Your question about James' system is a good one. I'm interested in that too! Gijs -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
On 22 Dec 2012, at 08:34, Gijs de Rooy gijsr...@hotmail.com wrote: Hangars are discussed in the wiki article actually ( http://wiki.flightgear.org/FlightGear_Git:_splitting_fgdata#Per-aircraft_project ) . That's why I pointed to it. Lots of ideas that show up on the mailinglist have been discussed in the past and the outcome of those discussions is mentioned at the wiki. First reading the wiki before sharing your own (good) ideas or opinions saves everyone's time, not at the least yours ;-) Your question about James' system is a good one. I'm interested in that too! It's been on the back burner but now the NavCache is mostly stable, and Thomas is taking care of the replacement GUI work, I can return to it. Actually I made some odd progress - libSvn has become a problem to support on the Mac, so I extended the HTTP code to become a read-only WebDAV client. It already works (can download from terra sync repository) and it's faster to update, and uses less diskspace (since it can assume the local files are Unmodified). But the initial checkout is currently much slower than libSvn, which I need to fix. But, it will also work for aircraft! So any WebDav or SVN server can be an aircraft hangar, and update automatically. And we already support multiple aircraft dirs, so there is not much work, to combine everything, I hope. The metadata will then simply be the -set.xml files and thumbnail images, extracted into a single file at the root of each 'hangar' repository. BTW I will also upstate my wiki page with my post 2.10 plans since I agree it's useful to share. Personally I think the wiki is better for such data, especially if we can add a category for 'developer plans'. James Gijs -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
Hi Yves, Maybe the PAF team has to take into account that Helijah spent half of his life contributing to flightgear models and this needs some personal respect and not only respecting gpl terms. [...] but to be honest, it has not the same history like the contribution of Emanuel Does it mean that in your opinion PAF team has no personal respect for helijah ? Does it mean that helijah can legitimately insult and denigrate other contributors/contributions ? PAF team has never insulted helijah (unlike him) and has asked the authorization to use his work : Before forking the DR400 one of PAF team member took a phone communication with helijah during more than 1 hour in order to explain him ( http://equipe-flightgear.forumactif.com/t899p45-pour-une-meilleur-integration-des-travaux-de-la-paf-dans-flightgear#16025 ) Isn't it an acceptable proof of respect ? Fork process is well know in Open Source world, for example OpenOffice is forked in LibreOffice, here PAF team does the same, forking the DR400 in DR400-jsbsim. LibreOffice hasn't personal respect for OpenOffice because of fork ? I don't think, for DR400-jsbsim it's exactly the same. Now imagine that OpenOffice uses the modified/created source code of LibreOffice but removes every copyright header who noticed that LibreOffice has modifified/created files, it should be incredible isn't it ? It's exactly what does helijah. This is a fact not a judgement. But to be honest the DR400 is not the important here, and I'm sure that everybody here know what is important, your reply explains it well. Anyway, I'm totally agree with the rest of your message. Thanks you having spent some of your time replying to this discussion. Cheers, Clément -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
Hi Clement Am 21.12.2012 um 09:40 schrieb Clement de l'Hamaide clem...@hotmail.fr: Hi Yves, Maybe the PAF team has to take into account that Helijah spent half of his life contributing to flightgear models and this needs some personal respect and not only respecting gpl terms. [...] but to be honest, it has not the same history like the contribution of Emanuel Does it mean that in your opinion PAF team has no personal respect for helijah ? Does it mean that helijah can legitimately insult and denigrate other contributors/contributions ? No, absolutely not. Never, that would be a misinterpretation of my sentences. In my opinion the only possibility to prevent the project from such things for future ongoings is to split parts of fgdata, i.e. the aircraft directory into hangers, adding a proper history file to each aircraft which needs to be kept in directory when you fork (what's normal anyway I think?). Maybe this needs a period of hanger subscription where people can show their interests in binding/adding a hanger to the project and where current developers are asked to found a own hanger. I would also like to see a wreckyard where new developers can pick up some projects probably ;-) And maybe this needs an active fg hanger project site (or hanger section on current sites) where you get overview and can follow this change. I would help to write down history of lets say 10-15 aircraft, contact former and recent contributors, make a proposal for a readme and ask them where to put their work and document this ongoings on a official site. It's a collaborative effort, it needs a plan, it needs a standard copyright and license notice which needs to be kept. My assumption is that it will take 6 months or more, but it is doable. I know 10 aircraft is not that much, but I would take responsability for this, that it goes to the right hanger for a new start of aircraft directories for fg, without loosing history, that this work is documented and former contributors know where their work has gone in case they do not found a own hanger. But at the end it is a decision of the core team if they give support for such a change or not, or if this remains a discussion of who presents the most clever git commands ;-) -Yves-- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
Please see http://wiki.flightgear.org/FlightGear_Git:_splitting_fgdata and feel free to add thoughts/ideas there. A mailing list is not a good place for documenting things. Cheers, Gijs -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
[..] Not only do they believe to be the authors of this aircraft but they also break existing things for the pleasure of breaking. It's sad to see this kind of commit description in a public place of the FlightGear project. For information, the commit is about the improvement made by PAF team on the DR400. (Of course nobody from PAF team asked him to push their work in the repo. It's his own choice to download the work done by PAF team and use it for it's own DR400) As the GNU GPL licence says : it's highly recommended to add a copyright header for each file created/modified. It's exactly what PAF team done adding Modified by PAF team (in case of file modification) or Created by PAF team (in case of file creation) as copyright header. Unfortunately helijah has removed all these copyright header before pushing the work made by PAF team on the repo. I can't imagine what would be the reaction of Curt if a commiter remove the header copyright of the file flightgear/src/Main/main.cxx . The fault made by helijah is the same here : he removed the copyright header (recommended by GNU GPL licence) of files for the second time (the first one was : https://gitorious.org/fg/fgdata/commit/7bc193ad0af206f166f2ab768880cec07891faa6 ) I will skip all the insults publicly written by helijah for just focusing your attention about the past and current licence / copyright violation brought by this contributor (red bull livery (z-lin50), sound file(reported by Pierre), texture file (JAS39-gripen). I think that a real solution has to be discussed here in order to avoid any new problem with this contributor. Cheers, Clément -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
Hi Clement Yes it is really sad to see such commit messages. But maybe the PAF team also thinks too concurrently in headers, gpl and copyright notice and file descriptions here. Maybe the PAF team has to take into account that Helijah spent half of his life contributing to flightgear models and this needs some personal respect and not only respecting gpl terms. For me personally the contribution of the PAF is very welcome, but to be honest, it has not the same history like the contribution of Emanuel. Even when it sounds strange to you, try to talk to him directly. I guess no one here wants to judge about small coyright thinking and who was first, who violates gpl by gpl and other childish games (which points mainly to Emanuel, who is responsible for many reallly bad commit messages, forum messages, in a really bad manner). But at the end here we are all volunteers, and the best you can do, the best the PAF team can do for the project is ... keep your work up, get commit rights and commit and try to communicate in a good way, a long time. Never blame others for doing this or that to make us judge about who is right. Helijah does it the hidden way in his commit messages, everyone knows and ignores, but you do it here officially in the list. Don't think people here are so stupid that they do not realise what's going on. The Flightgear Project made the bad mistake to miss to split the code into core and plug-ins with fg/sg vs. parts of fgdata, making it possible to have hangers for example. Maybe the core devs will make a better decision about this once, or when the current core team realise what fgdata has become actually, or another core team. Lets say thanks to all fgdata contributors who makes not that much noise and are patient all the days, really. -Yves Am 20.12.2012 um 23:44 schrieb Clement de l'Hamaide clem...@hotmail.fr: [..] Not only do they believe to be the authors of this aircraft but they also break existing things for the pleasure of breaking. It's sad to see this kind of commit description in a public place of the FlightGear project. For information, the commit is about the improvement made by PAF team on the DR400. (Of course nobody from PAF team asked him to push their work in the repo. It's his own choice to download the work done by PAF team and use it for it's own DR400) As the GNU GPL licence says : it's highly recommended to add a copyright header for each file created/modified. It's exactly what PAF team done adding Modified by PAF team (in case of file modification) or Created by PAF team (in case of file creation) as copyright header. Unfortunately helijah has removed all these copyright header before pushing the work made by PAF team on the repo. I can't imagine what would be the reaction of Curt if a commiter remove the header copyright of the file flightgear/src/Main/main.cxx . The fault made by helijah is the same here : he removed the copyright header (recommended by GNU GPL licence) of files for the second time (the first one was : https://gitorious.org/fg/fgdata/commit/7bc193ad0af206f166f2ab768880cec07891faa6 ) I will skip all the insults publicly written by helijah for just focusing your attention about the past and current licence / copyright violation brought by this contributor (red bull livery (z-lin50), sound file(reported by Pierre), texture file (JAS39-gripen). I think that a real solution has to be discussed here in order to avoid any new problem with this contributor. Cheers, Clément -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
The DR400 Guide (Aircraft/DR400/DR400 Guide.pdf) commited in this has a non-GPL compatible license (All rights reserved). I think this situation needs to be fixed (either the guide removed, or a proper GPL version of the guide is pushed) I think it would be a good idea if contributors would check more thoroughly the licenses of third party material commited. Relevant links: https://gitorious.org/fg/fgdata/blobs/master/Aircraft/DR400/DR400 Guide.pdf http://flightgear.org/forums/viewtopic.php?f=4p=172822#p172818 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgdata Commit c8a69dffd49a298e01c0e0e1320f4a1d49a0bca4
The DR400 Guide (Aircraft/DR400/DR400 Guide.pdf) commited in this has a non-GPL compatible license (All rights reserved). A nice example of some small words can do. I would have never noticed as I would all rights misinterprete as simple copyright at first glance. *blush* It isn't just a simple copyright I'm a bit more concerned about the commit description. First it doesn't make sense to me (there was only two contributor ever who committed changes to the DR400 in FGData - who the hell then broke anything?! E. BARANGER or Thorsten Brehm? *confused*). Then the description doesn't list was had been changed. So it seems to be just a quite meaningless description attacking someone... :-( That's something that I have seen quite often by some contributors, that they aren't able to tell what they have exactly changed. But that's the meaning of the commit log- Keywords and short exact description would help to see quick what had changed and would invite more to test and try. No need to write a book! So bugs and mistakes could be more followed easily. Juts two cents from the users perspective -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
