Mailing lists are used for some of the FlightGear community's communications, in particular among the core developers who are working on the flight simulator itself.
Some questions are better asked on the mailing list instead of the forum, especially those related to core development or project infrastructure, but you do not strictly have to be a core developer to subscribe and/or post to the mailing lists.
The mailing lists
|flightgear-announce||FlightGear announcements||Archive||Subscribefirstname.lastname@example.org||Last post 2015|
|flightgear-bugs||Bug tracker messages||Archive||Subscribeemail@example.com||Apparently dismissed|
|flightgear-builds||Chatter from the FlightGear build servers||Archive||Subscribefirstname.lastname@example.org|
|flightgear-commitlogs||Source code change commit logs||Archive||Subscribeemail@example.com||As of May 2016, commit logs over 160 KB need to be approved manually by the list moderator; therefore, their delivery might be delayed. In the future, bigger logs might not be sent anymore to the list in their entirety, to keep messages short and readable.|
|flightgear-cvslogs||CVS commit logs||Archive||Subscribefirstname.lastname@example.org||Apparently dismissed. Last post 2010.|
|flightgear-devel||FlightGear developer discussions||Archive||Subscribeemail@example.com||Most active list (primary)|
|flightgear-fgaddon-commitlogs||Commit logs for the FGAddon repository (content developers)||Archive||Subscribefirstname.lastname@example.org|
|flightgear-flightmodel||Flight model discussions||Archive||Subscribeemail@example.com||Last post 2017.|
|flightgear-newsletter||Newsletter announcements and discussions||Archive||Subscribefirstname.lastname@example.org||Last post 2012|
|flightgear-scenery||Discussion of scenery development: code, tools, GIS data, models, etc.||Archive||Subscribeemail@example.com|
|flightgear-users||FlightGear user discussions||Archive||Subscribefirstname.lastname@example.org||Mostly replaced by the forum|
How to subscribe to a mailing list
To sign up for one of the above mailing lists, follow these steps:
- Click a Subscribe link in the list above to get to the mailing list subscription form.
- Enter your e-mail address in the Your email address: box. You can optionally also:
- give your name;
- choose to receive e-mails batched in a daily digest (merged in a single message) or not;
- choose a password you can use to edit your subscription options in the future. If you do not enter a password, one will be automatically generated for you.
|Warning Do not use a valuable password as it will be occasionally sent to you via e-mail (this means that someone snooping on your messages might be able to get it).|
- Click the button.
- You will be sent a confirmation e-mail (usually it is delivered within ten seconds, but it can take up to a few minutes; if you do not see it, check your Spam folder). Click on the confirmation link in the message.
- SourceForge will display you a confirmation page where you can change some settings chosen in step 2. Click on to complete the process.
Posting to mailing lists
To protect list subscribers from spam, you are allowed to post there only after you have subscribed, and to send e-mails from the address you are subscribed with. For the same reason, first posts are subject to moderator approval to catch the cases where people sign up for the sole purpose of posting spam.
When posting to the lists, discuss your problem laying it out in as much detail you can and show that you are interested in the problem. If you are willing to work on it will also help, even if it is not related to coding itself. If your discussion is more than just asking for features to be added you have a better chance of getting help and you may find people there who can give you pointers on how to approach your problem. Also, be civil - avoid bringing conflicts or noise.
Keep in mind that getting a response from the lists is usually slower than the forum and that responses may take several days. Should it take more than a week, you might want to probe the interest by responding to your own message; sometimes, there might be no reply as there is none.
Report bugs to the issue tracker
Bugs should preferably be reported to the issue tracker instead of posting them to a mailing list.
You may have to register a SourceForge account first.