Thanks file

This article may require cleanup to meet the quality standards of the wiki. Please improve this article if you can.

Crediting won't be a problem, this is usually done as part of the "Thanks" file, which is by default part of every release, as you can see in $FG_ROOT/Thanks. However, if you want your work to be part of the official repository, it will inevitably need to be licensed under the GNU GPL.

I had previously been informed that fgdata has a Thanks file exactly for the purpose of licenses that require authors being mentioned, but I am not sure about this.

There was a time when we tried to credit any contributors, but I'm afraid this is a bit lacking. (See the Thanks file in fgdata and the flightgear source.) At this time it might be a good idea to properly document where the texture originates from to be able to fight possible future copyright infringement notifications.

Supporters will be mentioned on the FlightGear webpage and in the Thanks file.

Seriously though, the company that provided this beast of a machine should really be be added to the FlightGear Hall of Fame, the "Thanks" file wouldn't be doing justice. Maybe we should add a "Hall of Fame" wiki page, with only the admins having write privileges?

There used to be a time when such donations/sponsors were added to the $FG_ROOT/Thanks file, but apparently that is no longer the case.

The Thanks file used to be maintained by CVS committers over a decade ago - since then, I think it's only been core developers adding themselves. Ideally, patches should come with changes to the Thanks file, so that contributors can credit themselves, without the committer having to do any manual work.

Now the Thanks file exists only to politely indicate the authors and not as a licensing requirement; there won't be ever a licensing problem with them

If you want your contributions to be mentioned in the Thanks file, you should also send a corresponding patch. Discussions usually take place as part of the merge request.

As mentioned by Curt on previous occasions, one of the more labor intensive parts of managing a release consists of the compilation of a comprehensible revision log that lists the major changes / improvements to FlightGear. I would appreciate it if somebody would give a hand in compiling such a list. Last year, we used the WIKI to host this log. Eventually this page ended up in the Developer portal, under the section Done. There is still a "Changes since 0.9.10 page, and I guess we could add a new "Changes since 1.0.0". Each revision log typically consists of the sections: "New Features", "Bugfixes", "Regressions", "New Aircraft", and "Improved Aircraft"

Also, with the global target set for the release, I'm trying to get an impression of which projects are still under development, and which would be nice to have included in the release. Note that this overview implies by no means a deadline, or anything like it. I'd just like to know what is currently going on, so I can get an impression of which projects need some more time, and when we should set a feature freeze period.

I've just gone through the "Thanks" file and added many names of people who have contributed to FlightGear.

We should really have had this from the beginning. It's hard to remember all the details afterwards. I couldn't even remember my contributions without looking at my git log.

This file really needs to be updated, there has been a tremendous amount of work gone into FlightGear that had not been listed yet. I wouldn't even know where to begin if I was to update it myself.

I'm sure I've forgotten some people, so if you know other people you think should be listed, feel free to step up and mention them. Self nominations are welcome, and feel free to mail your nominations to me directly.

If you feel you deserve to be listed: Don't be shy and please provide a list of the areas you've worked in so it can be brought up to par. This may be done privately if you wish (by sending me an email).

FlightGear would have been nowhere without the help of all these people, and we should give credit, where credit is due.

Criteria for inclusion are, more or less: If you have made a successful contribution to FlightGear, or have done significant activities toward keeping the infrastructure of FlightGear together, have done promotional work, or have a successful track record of helping new users find their way, you should be listed.