20,741
edits
FlightGear Newsletter June 2014: Difference between revisions
Jump to navigation
Jump to search
m
I seem to have removed the wrong section previously ?
m (I seem to have removed the wrong section previously ?) |
|||
| Line 235: | Line 235: | ||
Continue reading at [[Implementing new features for FlightGear]]... | Continue reading at [[Implementing new features for FlightGear]]... | ||
<!-- | |||
=== Getting involved as a programmer === | === Getting involved as a programmer === | ||
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs. | Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs. | ||
| Line 245: | Line 246: | ||
Of course, you're also free to work on whatever you want -- FlightGear as a community-driven doesn't tell people what to do, but welcomes any contributions from anybody, as long as they have acceptable quality and are free to be licensed under the GNU GPL. So if you have something you would like to contribute back to FlightGear, please get in touch! (Preferably using Gitorious for larger merge requests, and the forums or (core-) developer's mailing list to inform the developers of what you want to contribute back.) Changes contributed 6-8 weeks before a release will usually appear in the next release, so your changes can be spread across the world. | Of course, you're also free to work on whatever you want -- FlightGear as a community-driven doesn't tell people what to do, but welcomes any contributions from anybody, as long as they have acceptable quality and are free to be licensed under the GNU GPL. So if you have something you would like to contribute back to FlightGear, please get in touch! (Preferably using Gitorious for larger merge requests, and the forums or (core-) developer's mailing list to inform the developers of what you want to contribute back.) Changes contributed 6-8 weeks before a release will usually appear in the next release, so your changes can be spread across the world. | ||
--> | |||
== Release ChangeLog == | == Release ChangeLog == | ||