Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Mailing lists

From FlightGear wiki
Revision as of 16:38, 10 May 2015 by Johan G (Talk | contribs) (Report bugs to the issue tracker: Grammar; link for to report form page)

Jump to: navigation, search

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. You do not strictly have to be a core developer to subscribe and/or post to the mailing lists.

The mailing lists

Some of the lists are for discussions while some only contain announcements.

List Status Archive Subscribe Email address Remarks
FlightGear-Devel Active archive subscribe flightgear-devel@lists.sourceforge.net The most active list. Where you can contact mostly core developers.
FlightGear-commitlogs archive subscribe flightgear-commitlogs@lists.sourceforge.net Announces all commits to some of the repositories.
FlightGear-Scenery Quiet archive subscribe flightgear-scenery@lists.sourceforge.net Scenery developments.
FlightGear-Users archive subscribe flightgear-users@lists.sourceforge.net Mostly replaced by the forum these days.
FlightGear-Announce Inactive archive subscribe flightgear-announce@lists.sourceforge.net
FlightGear-FlightModel archive subscribe flightgear-flightmodel@lists.sourceforge.net
FlightGear-Newsletter archive subscribe Receive an email when a new edition is published.

Posting to the mailing lists without subscribing

Subscribing is not strictly necessary to send emails.

Your post may be significantly delayed if you are not subscribed though. E-mails from addresses which are not subscribed to the list are held for moderator approval before they are posted.

Report bugs to the issue tracker

Bugs should preferably be reported to the issue tracker instead of posting to a mailing list.

You may have to register a SourceForge account first.

External links