Bureaucrats, checkuser, Administrators
304
edits
Feature Requests / Proposals / Ideas: Difference between revisions
add general ideas
Hellosimon (talk | contribs) (add general ideas) |
|||
| Line 145: | Line 145: | ||
'''Full document''': [http://www.cs.yorku.ca/~cs233144/Flightgear/new_FG_architecture.pdf A New Architecture for FlightGear Flight Simulator] | '''Full document''': [http://www.cs.yorku.ca/~cs233144/Flightgear/new_FG_architecture.pdf A New Architecture for FlightGear Flight Simulator] | ||
== General Ideas == | |||
* Set up a wiki at FlightGear.org, so that regular backups can be easily done. Also, the wiki could possibly write/export its pages directly into the CVS directory of $FG_ROOT/Docs | |||
* set up a full set of automatically created DoxyGen documentation at FlightGear.org, possibly using a monthly/weekly update cycle for the CVS version, this would require approx. 500MB of webspace, could be done using a cron job | |||
* consider distributing the FlightGear CD/DVD as a linux boot cd/dvd (i.e. knoppix), so that users can optionally try to easily boot easily into linux in order to start FG | |||
* consider setting up a non-profit organization for FlightGear, so that donations may become tax-deductible | |||
* consider setting up a subversion server, so that we can stop using CVS-subversion can easily import an entire repository, preserving all revision history etc. | |||
* http://scan.coverity.com/ - offers free code checks to open source projects | |||
* At http://freshmeat.net/projects/installbase/ or more specifically at http://installbase.sourceforge.net/main.shtml there's an open source cross platform GUI installer available that may be an interesting option for creating binary FlightGear installers. The whole thing is based on TK and works with statically precompiled interpreters that serve as stub for an ASCII config file that contains all relevant information for cross platform setups,including a tarball of installation specific files for each platform. The installbase installer is very convenient and works entirely with a very powerful GUI frontend that allows you to set up, test and export installer packages. Given that the final config file is ASCII, it would probably be quite possible to simply put all this into some sort of Makefile, so that the whole package creation could be handled automatically, i.e. by doing something like "make win32-package" or "make macos-package". The screenshots look very convincing. That way, all FlightGear binaries could easily use an identical installer and configuration wizard. | |||
* Set up a cross compiler version of gcc at flightgear.org to automatically create binary packages (releases) of FlightGear for platforms such as Win32 or MacOS. | |||