Volunteer: Difference between revisions

Jump to navigation Jump to search
1,452 bytes removed ,  14 July 2006
No edit summary
Line 62: Line 62:
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
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


==== Pre-Release Managers ====
 
It was recently discussed, and it is currently considered, to offer regular binary pre-releases to the FlightGear user community, these should be based on the latest CVS code and are currently planned to be released every 8-12 weeks (this may be subject to change however). This is mainly meant to allow the user community to keep up to date with the latest developments and is supposed to enable developers to recognize potential issues with development code by widening the audience for pre-release (test) code.
However, primarily this is a reaction to address issues that became apparent with the official release of the 0.9.9 version, where apparently only a very small number of users actually knew of the possibility to test the pre-release binaries and even fewer people actually did use this opportunity, so that practically nobody provided any feedback to the developers, ultimately resulting in a number of critical issues going unnoticed until after the official release.
As pre-release manager you should have access to a working build environment for one or several of the platforms that are supported by FlightGear, and be able to build FlightGear binaries from (CVS) source code without further assistance from the developers. If you would like to contribute in this way to the project, please make sure to volunteer by subscribing to the FlightGear Developer mailing list and offering your services there.


==== Pre-Release Testers ====
==== Pre-Release Testers ====
Anonymous user

Navigation menu