Re: [Flightgear-devel] Fair practice & autorisations
Clément ,Not trying to start a flame war , but you modified someone else's work , so this sounds a bit odd , but i do understand your point .Ive seen a lot of things Ive modelled end up in other's 'original' work , but i've also borrowed nasal scripts and ideas from others so I can't complain .I agree ,though, cooperation is usually a better way to go :) Just my thoughts... Cheers -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fair practice & autorisations
Hi Martin, The original author of the model is Emmanuel Baranger The original author of basic XML animation for model is Emmanuel Baranger The original author of instruments panel is Alexis Laille The original author of the Dual Control (copilot & passenger) adapted for DC-3 is Clément de l'Hamaide The original author of nasal hydraulic system is Clément de l'Hamaide The original author of hydraulic system model is Ernest Teutcher The original author of tutorials is Alexis Laille The original author of engine system is Clément de l'Hamaide The original author of overhead model is Clément de l'Hamaide The original author of wipers is Ernest Teutcher The original author of nasal electric system adapted fo DC-3 is Clément de l'Hamaide The original author of decoration model is Emmanuel Baranger The original author of sound system is Christian Thiriot The original author of new panel is Alexis Laille The original author of new chair in cabine is Christian Thiriot The original author of liveries in cabine and cockpit is Christian Thiriot The original author of GUI dialog is Clément de l'Hamaide The original author of lights and light system adapted for DC-3 is Clément de l'Hamaide The original author of paratroopers adapted for DC-3 is Emmanuel Baranger (but need my intervention for it works) ... ... ... The list can be very long :) But here it's not the problem of "who is the author model". The problem is => the minimum politeness is to ask to the PAF team if we accept to see our contributions committed. I know the GPL give the possibility to commit without asking anything but here we speak about "fair practice". When you decide to download a package from a website and upload it on your website and GIT the minimum politeness is to ask to the author of the improvement if he's agreed with this isn't it ? Thanks you for your attention Cheers, Clément de l'Hamaide (F-JJTH) -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fair practice & autorisations
Salut Clement, Clement de l'Hamaide wrote: > The PAF team just seeing our integral > contributions have been uploaded on GIT by E.Baranger aka helijah. (Commit : > https://gitorious.org/fg/fgdata/commit/4fb29b9010ae69e01b46a7ea074259b04b12064e > ) > > > > > This member haven't asked any > autorisation before upload our contributions. Yet it is customary to > ask autorisation from authors of contributions before modify/diffuse > the work created by them. Just to get a better understanding of the context: Who's the 'original' author of this DC-3 aircraft model ? Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fair practice & autorisations
Hi all, The PAF team just seeing our integral contributions have been uploaded on GIT by E.Baranger aka helijah. (Commit : https://gitorious.org/fg/fgdata/commit/4fb29b9010ae69e01b46a7ea074259b04b12064e ) This member haven't asked any autorisation before upload our contributions. Yet it is customary to ask autorisation from authors of contributions before modify/diffuse the work created by them. Moreover, the uploaded version on GIT by E.Baranger isn't the stable version by PAF team. The only one stable version from PAF team is available in the Hangar of the PAF team : http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf We haven't any control about our contributions available on GIT and we can't be responsible if there are malfunctions. You can consider that the contributions committed by E.Baranger aren't the official and stable version of the contributions developped by the PAF team. Also, it seems that helijah makes many faults about licence respect and fair practice in recent months. We remember many problems of licence non-respected by helijah (i.e http://sourceforge.net/mailarchive/message.php?msg_id=28676706 ). Today this member have yet makes a fault of fair practice (without asking autorisation from contribution authors). Seeing these multiple faults it would be more careful to remove the commit rights to E.Baranger. Cheers, Clément -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Final 2.6.0 Release Preparations
Am 11.02.2012 16:32, schrieb Ron Jensen: > I found and fixed a potential NaN and Segfault in the JSBSim propeller code > yesterday. It could be considered a blocking bug for 2.6 to me. Thanks, looks like a small and safe enough patch which we should push to the 2.6.0 branch. cheers, Thorsten -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Final 2.6.0 Release Preparations
On Friday 10 February 2012 04:08:32 Torsten Dreyer wrote: > Hi all, > > for our release of version 2.6.0 next week, we have a few open items on > our checklist and I am kindly asking for support to get them done: > > 1. How are our release candidates performing? Are there any release > blocking bugs that should be taken care of? I found and fixed a potential NaN and Segfault in the JSBSim propeller code yesterday. It could be considered a blocking bug for 2.6 to me. The property /fdm/jsbsim/propulsion/engine/prop-induced-velocity_fps gives wrong answers, and can become NaN under certain conditions. When thrust is negative and forward velocity is small we can take the square root of a negative number. This could occur, for example, when using reverse thrusters on landing. The value comes out much too high when alpha is near 180, such as taxing with a tail wind. Thanks, Ron http://jsbsim.cvs.sourceforge.net/viewvc/jsbsim/JSBSim/src/models/propulsion/FGPropeller.cpp?r1=1.42&r2=1.43&view=patch --- FGPropeller.cpp 2011/12/22 22:13:59 1.42 +++ FGPropeller.cpp 2012/02/11 15:14:27 1.43 @@ -228,8 +228,16 @@ // Induced velocity in the propeller disk area. This formula is obtained // from momentum theory - see B. W. McCormick, "Aerodynamics, Aeronautics, // and Flight Mechanics" 1st edition, eqn. 6.15 (propeller analysis chapter). - Vinduced = 0.5 * (-Vel + sqrt(Vel*Vel + 2.0*Thrust/(rho*Area))); - + // Vinduced = 0.5 * (-Vel + sqrt(Vel*Vel + 2.0*Thrust/(rho*Area))) + // Since Thrust and Vel can both be negative we need to adjust this formula + // To handle sign (direction) separately from magnitude. + double Vel2sum = Vel*abs(Vel) + 2.0*Thrust/(rho*Area); + + if( Vel2sum > 0.0) +Vinduced = 0.5 * (-Vel + sqrt(Vel2sum)); + else +Vinduced = 0.5 * (-Vel - sqrt(-Vel2sum)); + // P-factor is simulated by a shift of the acting location of the thrust. // The shift is a multiple of the angle between the propeller shaft axis // and the relative wind that goes through the propeller disk. -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] linking errors with origin/next?
On Saturday, February 11, 2012 14:01:55 Scott wrote: > thanks Thorsten, > > Now to find out why, must be a static link library somewhere that > isn't getting updated... > > > cheers > S. > Hi, I had the same problem recently, and it took me quite a long while to figure it out. It may be the same for you or not, but I think it's worth mentioning this just in case: if you build simgear and flightgear with CMAKE_BUILD_TYPE="Debug", libraries have a "d" suffix. If afterwards you switch flightgear to "Release" and forget to do the same for simgear, flightgear tries to link to old "Release" simgear libraries which don't have a "d" suffix. Of course, the right way to do this is to have separate build trees for build types, like it's described in the cmake readme, but of course I did not follow this procedure and was bitten by this issue. Worst part was flooding the tracker with fake bug reports and pestering Thorsten because of my local issue :) I still have a common build tree, but now I check the flags beforehand. Cheers, Adrian -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] linking errors with origin/next?
thanks Thorsten, Now to find out why, must be a static link library somewhere that isn't getting updated... cheers S. On Sat, 2012-02-11 at 11:24 +0100, ThorstenB wrote: > Am 11.02.2012 10:16, schrieb Scott Hamilton: > > I updated my git working directory to "origin/next" and am getting the > > following link errors, I'm not 100% sure that git is properly updating > > everything, I have done a "make clean" and "make rebuild_cache" on both > > simgear and flightgear. > > Is anyone else seeing these errors, or is my working directory really > > messed up? > > Looks like a local problem on your machine. > > You can always check with the build server: > http://flightgear.simpits.org:8080/ > > If you're having a compile or link problem, but the lights for your > platform are all green there (i.e. Windows/Linux/Mac, Release or Next), > then you're very likely to have local issue. > > cheers, > Thorsten > > -- > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] linking errors with origin/next?
Am 11.02.2012 10:16, schrieb Scott Hamilton: > I updated my git working directory to "origin/next" and am getting the > following link errors, I'm not 100% sure that git is properly updating > everything, I have done a "make clean" and "make rebuild_cache" on both > simgear and flightgear. > Is anyone else seeing these errors, or is my working directory really > messed up? Looks like a local problem on your machine. You can always check with the build server: http://flightgear.simpits.org:8080/ If you're having a compile or link problem, but the lights for your platform are all green there (i.e. Windows/Linux/Mac, Release or Next), then you're very likely to have local issue. cheers, Thorsten -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Final 2.6.0 Release Preparations
Am 11.02.2012 10:40, schrieb thorsten.i.r...@jyu.fi: >> Best of all, the new features are based on user community requests, and >> > not driven by economic incentives. Some of these features are already in >> > the works for the next FG release [give continuity message about the >> > development] > That'd be suspiciously close to dishonest advertizing. I spend a fair > share of my forum time explaining to angry/disappointed/overeager users > that feature requests are suggestions which often end up being discussed, > but more rarely end up being implemented, and rather that an army of eager > developers waiting for features to be proposed, features usually get > implemented if a developer is interested in implementing them (so the best > strategy to get something done is to get a developer interested, not by > just complaining...). > > As far as I am aware, the development is mostly driven by what developers > are interested in, not by user community requests (which sort of makes > sense in an all-volunteer community), and unless there is a formal > commitment of core developers on the horizon to devote part of their time > to work through feature requests, I would not advertize such a line - it's > going to backfire on the project. +1 Every free, open source project is really driven by active community _participation_, not so much by (passive) user's _requests_. In general, it's not even a matter of economic incentives, though this may be the case with FG. But you can see it with Linux kernel development: loads of companies and individuals involved, all pushing the project forward - each with their own private fun or economic interests. What really matters to an OS project is the community effort and the option for everyone to get involved. Even if this results in the mentioned "group hug" :) - I think that'd be the really important point to stress, when hinting a comparison with MS Plight (oops, typo ;-) ). cheers, Thorsten -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Local Weather menu structure
Am 22.01.2012 21:27, schrieb Stuart Buchanan: > On Sun, Jan 22, 2012 at 5:34 PM, Torsten Dreyer wrote: >> And I just pushed that to FGDATA. "Global Weather" and "Local Weather" >> is dead. Long live "Basic Weather" and "Advanced Weather" :-) > > Thanks Torsten. That looks great. > > BTW, if this change is merged into the 2.6.0 branch, we should also include > commit a38820828c5343dbcb77d97a65597d736c845ff4, which removes > a now-redundant reference to the local_weather_tiles menu item. > > I've also made the co-requisite change to The Manual > (773db8825336521c42fd4d0edb22ca2d1bcc06ea) that should also > be merged. I have just cherry-picked the Basic/Advanced Weather patches into release/2.6.0 - including Stuarts change to local_weather.nas. We don't have release branches for the getstart repository (The Manual), so there is nothing to merge/pick there. Torsten -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Final 2.6.0 Release Preparations
> Best of all, the new features are based on user community requests, and > not driven by economic incentives. Some of these features are already in > the works for the next FG release [give continuity message about the > development] That'd be suspiciously close to dishonest advertizing. I spend a fair share of my forum time explaining to angry/disappointed/overeager users that feature requests are suggestions which often end up being discussed, but more rarely end up being implemented, and rather that an army of eager developers waiting for features to be proposed, features usually get implemented if a developer is interested in implementing them (so the best strategy to get something done is to get a developer interested, not by just complaining...). As far as I am aware, the development is mostly driven by what developers are interested in, not by user community requests (which sort of makes sense in an all-volunteer community), and unless there is a formal commitment of core developers on the horizon to devote part of their time to work through feature requests, I would not advertize such a line - it's going to backfire on the project. * Thorsten -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] linking errors with origin/next?
I updated my git working directory to "origin/next" and am getting the following link errors, I'm not 100% sure that git is properly updating everything, I have done a "make clean" and "make rebuild_cache" on both simgear and flightgear. Is anyone else seeing these errors, or is my working directory really messed up? Linking CXX executable fgfs CMakeFiles/fgfs.dir/globals.cxx.o: In function `FGGlobals::set_fg_root(std::basic_string const&)': /src/Flightgear/git-repo/flightgear/src/Main/globals.cxx:220: undefined reference to `SGPath::realpath() const' CMakeFiles/fgfs.dir/globals.cxx.o: In function `FGGlobals::append_aircraft_path(std::basic_string const&)': /src/Flightgear/git-repo/flightgear/src/Main/globals.cxx:306: undefined reference to `SGPath::realpath() const' CMakeFiles/fgfs.dir/globals.cxx.o: In function `FGGlobals::append_fg_scenery(std::basic_string const&)': /src/Flightgear/git-repo/flightgear/src/Main/globals.cxx:256: undefined reference to `SGPath::realpath() const' ../Airports/libfgAirports.a(groundnetwork.cxx.o): In function `FGGroundNetwork::render(bool)': /src/Flightgear/git-repo/flightgear/src/Airports/groundnetwork.cxx:1439: undefined reference to `SGMaterial::get_effect()' /src/Flightgear/git-repo/flightgear/src/Airports/groundnetwork.cxx:1513: undefined reference to `SGMaterial::get_effect()' ../ATC/libfgATC.a(trafficcontrol.cxx.o): In function `FGStartupController::render(bool)': /src/Flightgear/git-repo/flightgear/src/ATC/trafficcontrol.cxx:1412: undefined reference to `SGMaterial::get_effect()' /src/Flightgear/git-repo/flightgear/src/ATC/trafficcontrol.cxx:1489: undefined reference to `SGMaterial::get_effect()' collect2: ld returned 1 exit status make[2]: *** [src/Main/fgfs] Error 1 make[1]: *** [src/Main/CMakeFiles/fgfs.dir/all] Error 2 make: *** [all] Error 2 -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
