20,741
edits
Implementing new features for FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Implementing new features for FlightGear (view source)
Revision as of 18:36, 17 May 2014
, 17 May 2014→Test the waters
| Line 37: | Line 37: | ||
== Test the waters == | == Test the waters == | ||
If you want your idea to be part of Flightgear in the end and not a fork or an addon, test the waters early on. Working for a year on some project which won't be committed in the end is frustrating for both sides. Use the forum or the mailing list to talk to people, get a feeling for how the response is, just don't leave it there. | If you want your idea to be part of Flightgear in the end and not a fork or an addon, test the waters early on. Working for a year on some project which won't be committed in the end is frustrating for both sides. Use the forum or the mailing list to talk to people, get a feeling for how the response is, just don't leave it there. It is always a good idea to announce your project on the forum, you can also use the [[Newsletter]] to make announcements. If your project is in any way about software or the base package, another good idea is becoming familiar with using git and gitorious and using it to conduct development in the open, so that others can track your work and provide feedback. | ||
Some events that have occurred in the past, and what to learn from them: | Some events that have occurred in the past, and what to learn from them: | ||