Understanding the project

From FlightGear wiki
Revision as of 17:08, 22 February 2015 by Johan G (talk | contribs) (Johan G moved page Understanding the Project to Understanding the project: Non-camel case title)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
This article is a stub. You can help the wiki by expanding it.

This page is intended to list ideas for articles that are intended to help address long-standing issues and debates, such as for example:

  • "entry point" articles:
    • troubleshooting/end-user support
    • volunteering
    • contributing
    • core development
  • a more modular base package [1]
  • backward compatibility
  • JSBSim vs. YASim
  • Having too many unfinished/incomplete aircraft
  • Why we have fictional aircraft
  • GPL requirements
  • Placeholder mentality WRT to contributions
  • Aircraft ratings contributed by end-users
  • why we don't have custom GUI tools for things like developing aircraft/scenery, but use Blender, GRASS/QGIS, GIMP etc
  • why we tend to focus on infrastructure and building blocks instead of developing end-user features
  • why contributions should be granted directly to the project, to prevent people from "pulling" their contributions once they disagree with other contributors (c.f. grtux, vitos, i4dnf)
  • HLA/RTI repercussions WRT circumventing the GPL unless we adopt the AGPL