20,741
edits
Volunteer: Difference between revisions
Jump to navigation
Jump to search
m
adding more things that can be easily done by everybody
m (→HowTo Writers) |
m (adding more things that can be easily done by everybody) |
||
| Line 4: | Line 4: | ||
If you are contributing to the core simulator, or an aircraft in CVS, you should be part of the FlightGear-devel mailing list, which is the primary point of contact for all discussions regarding the development of the simulator. | If you are contributing to the core simulator, or an aircraft in CVS, you should be part of the FlightGear-devel mailing list, which is the primary point of contact for all discussions regarding the development of the simulator. | ||
==== Participate in the FlightGear Forums ==== | |||
If you haven't done so already, please consider registering at the [http://www.flightgear.org/forums FlightGear forums], this is a very simple thing to do, but it makes it very easy to obtain and provide help within the FlightGear community. | |||
==== Check out the FlightGear Chat channel ==== | |||
To talk to fellow FlightGear users in realtime, you may want to check out the IRC chat channel, please see: http://wiki.flightgear.org/index.php/IRC | |||
This is also an excellent way for getting and providing community help, or for getting the latest news about FlightGear. | |||
==== Tell us about your own ideas and feature requests for improving FlightGear ==== | |||
If you have a good idea or feature request for improving FlightGear, the FlightGear forums and the IRC channel are an excellent way for getting feedback. | |||
==== Help us write the FlightGear Newsletter ==== | |||
The FlightGear newsletter is a community driven Newsletter that is created and edited using the wiki. | |||
All community members are invited to contribute to the newsletter. The only thing that is required is a wiki account, which is free and easy to register. | |||
You can find next month's newsletter at: http://wiki.flightgear.org/index.php?title=Next_newsletter | |||
==== Help improve the Wiki ==== | |||
You can easily register a new account and help improve the wiki, for example by editing existing articles or creating new ones. | |||
Also, many articles could be greatly improved just by adding a handful of relevant screenshots for illustration purposes. | |||
==== Help review Wiki articles ==== | |||
Many wiki articles are outdated, or may simply need to be reviewed and improved for other reasons - your help in reviewing existing articles would be highly appreciated! | |||
==== Help translate the Wiki ==== | |||
You can also help localize the Wiki by translating important articles into different languages. | |||
==== Submitting Bugs to the Bug Tracker ==== | |||
Bugs are currently being reported at [http://code.google.com/p/flightgear-bugs/ this tracker]. Feel free to contact one of the project owners to be added to the member list, if you would like to add a bug (or two). Reporting bugs accurately helps make bug fixing significantly easier for the developers. | |||
Another thing that is very helpful, is reviewing posted bug reports and see if you can reproduce/confirm them. | |||
==== Screenshot Managers ==== | |||
In order to illustrate FlightGear's impressive and advancing capabilities it was recently suggested (and agreed) to conduct monthly screenshot competitions where users are encouraged to submit their best FlightGear screenshots, so that the very best screenshots will be posted on the webpage for one month. Participants are expected to make their submissions at the end of each month, submissions should not be directly sent to the user mailing list as attachments, rather participants are expected to upload their screenshots to some free webspace and send mails containing links to their screenshots to the FlightGear User mailing list. It will be the decision of the screenshot managers to determine which screenshots shall win the monthly competition and are thus uploaded to www.flightgear.org | |||
==== FAQ-Maintainers ==== | ==== FAQ-Maintainers ==== | ||
The FlightGear project is currently looking for people who are willing to maintain the FAQ (which is quite out of date). If you you would like to get involved, please subscribe to the FlightGear Developers [[Mailing list]] in order to discuss the details. | The FlightGear project is currently looking for people who are willing to maintain the FAQ (which is quite out of date). If you you would like to get involved, please subscribe to the FlightGear Developers [[Mailing list]] in order to discuss the details. | ||
==== | ==== Scenery Model Creators ==== | ||
The FlightGear project maintains a steadily growing repository of [http://scenemodels.flightgear.org/models.php 3D models] for adding some eye-candy to the Scenery. The World has always enough room left for your [http://scenemodels.flightgear.org/contribute.php contribution]. Please take the time to investigate what's already there and enjoy populating your favourite area. | |||
Note that you don't have to create any models yourself. You can simply place existing models using the UFO. | |||
==== Artwork Creators/Contributors ==== | ==== Artwork Creators/Contributors ==== | ||
| Line 17: | Line 52: | ||
* Sound recordings of aircraft are also valuable - particularly engine sounds for unusual aircraft. | * Sound recordings of aircraft are also valuable - particularly engine sounds for unusual aircraft. | ||
==== HowTo Writers ==== | ==== HowTo Writers ==== | ||
| Line 66: | Line 97: | ||
Currently, some of the other documentation that comes with FlightGear is lacking, terse or simply inaccurate (outdated) in various places due to the advances in FlightGear's code since the time when the original documentation was written. This state is not improved by people's tendency to create new documents instead of maintaining what already exists. As a documentation editor/reviewer, it would be your task to check the current documentation and identify areas for improvement. Preferably you should also be able to directly make corresponding suggestions for augmentations, or even write new help documents altogether (possibly based on evaluating recent mailing list discussions). You would be expected to thoroughly check the documentation folder ($FG_ROOT/Docs) and review all relevant documentation for obvious shortcomings or mistakes, smaller corrections shall be sent by email to the developer mailing list, preferably in unified diff format (for patch to work). Alternatively, small text files can also be sent directly to the mailing list, more complex modifications should be only made available by uploading them to a webpage and linking to the corresponding files from your emails. If you are not now familiar with the process of creating unified diff patches, but would like to make it easier for the developers to work with your changes, please consider trying [http://kdiff3.sourceforge.net/ KDiff3], a GUI frontend to the diff and patch utilities that works on several platforms (also Windows). | Currently, some of the other documentation that comes with FlightGear is lacking, terse or simply inaccurate (outdated) in various places due to the advances in FlightGear's code since the time when the original documentation was written. This state is not improved by people's tendency to create new documents instead of maintaining what already exists. As a documentation editor/reviewer, it would be your task to check the current documentation and identify areas for improvement. Preferably you should also be able to directly make corresponding suggestions for augmentations, or even write new help documents altogether (possibly based on evaluating recent mailing list discussions). You would be expected to thoroughly check the documentation folder ($FG_ROOT/Docs) and review all relevant documentation for obvious shortcomings or mistakes, smaller corrections shall be sent by email to the developer mailing list, preferably in unified diff format (for patch to work). Alternatively, small text files can also be sent directly to the mailing list, more complex modifications should be only made available by uploading them to a webpage and linking to the corresponding files from your emails. If you are not now familiar with the process of creating unified diff patches, but would like to make it easier for the developers to work with your changes, please consider trying [http://kdiff3.sourceforge.net/ KDiff3], a GUI frontend to the diff and patch utilities that works on several platforms (also Windows). | ||
If you intend to redo a major part of the current documentation, it is recommended that you first discuss this with the developers, to ensure that you do not end up documenting code that may also be subject to major changes or even removal altogether. Please contact the developers before launching into a major documentation effort. | If you intend to redo a major part of the current documentation, it is recommended that you first discuss this with the developers, to ensure that you do not end up documenting code that may also be subject to major changes or even removal altogether. Please contact the developers before launching into a major documentation effort. | ||