> Here are some questions: > 1. Should I work from a c172p model more recent than on the website? > If so, where can I find the Aircrafts in gitorious? > 2. How do I contribute? Do I learn to use git and create a branch? Do > I post the aircraft as a .zip file for someone to look at? > 3. Should I run a more recent flightgear version? (e.g. compile 2.4.0 > from source) > > Hi Stephan,
Stuart currently is our maintainer for the c172p and it might be a good idea to coordinate your efforts with him to avoid duplicate work. It is usually best to develop against the latest state of development which you can find at http://gitorious.org/fg Our aircraft are still in the fgdata sub project with it's direct link http://gitorious.org/fg/fgdata I'd strongly recommend learning git. Creating merge requests is by far the best way for commiters to apply patches. And for the binary, it is best to run not only the latest version (2.4.0) but build from source from the current HEAD of the next branches to make sure your changes are compatible with the next version of FlightGear. I hope this helps getting you started. The learnig curve is a little steep in the beginning but if you get stuck, there are many documents about compiling from source at the wiki and many helping hands at the forum or here on the list. Torsten ------------------------------------------------------------------------------ Cloud Computing - Latest Buzzword or a Glimpse of the Future? This paper surveys cloud computing today: What are the benefits? Why are businesses embracing it? What are its payoffs and pitfalls? http://www.accelacomm.com/jaw/sdnl/114/51425149/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
