The File Library at AusFlightSim is a popular feature of the site. This document explains what you need to know and the steps you should follow in order to upload your files and have them approved by an Administrator. It also explains some of the common problems that can occur when uploading files to the library.

Before going ahead and uploading your file to the library there are several things to consider and also some simple steps to take to ensure that your file passes approval smoothly and without question.

Considerations

· Licensing: You should first decide what licensing structure your file should be released under. There are several to consider. Public Domain, Freeware, Shareware and Copyleft are a few of the licensing structures available with each enabling developers a number of options with regards to the use and distribution of the software.

Public Domain: For anything to be public domain the creator must specifically declare that it is public domain and give up all rights to its use and distribution. Software designated public domain can be modified and re-distributed and any way shape or form by anyone else. Note that anything you create is automatically given copyright protection and only becomes public domain by specifically saying so.

Freeware: Something designated as freeware is given away at no charge by the creator, however the creator retains the copyright and other rights. A creator, as copyright holder, can include additional terms and conditions beyond those implied by the term "freeware" but should not assume that "freeware" means more than it actually does.

Shareware: Something distributed by the shareware method is a commercial product for which the developer expects to get paid. The developer holds the copyright and all other rights to the product, but allows some form of it (possibly limited in some way) to be freely distributed so that potential customers can evaluate it.

Copyleft: A distribution concept developed by The GNU Project. Applying a "copyleft" to a release puts it somewhere between freeware and public domain. The legal terms allow the file to be improved on, but the source code must always be available for free. The standard legal notice that must be included provides strong protection for your release, much better than the legal mumbo jumbo that many hobbyists use. For the full details of copyleft visit the General Public License page at www.gnu.org/copyleft/gpl.html.

· Credit for the Work: As is often the case with flight sim development much of the material offered for download by developers is a derivative of another developers work. The prime example is aircraft re-paints where many of the files in the distribution are common among derivative works. When choosing to distribute files that are not entirely your creation you must ensure that you have the express written permission of the author of those files before submitting to the file library.

Programmatically renaming files or variables in code or even using portions of program code or image files without the permission of the original autor is in breach of international copyright law and may lead to serious legal action against you. Please keep this in mind!

· Documentation: Any good developer realises the importance of comprehensive documentation. Among other things the important features of well written documentation will include:
- a detailed description of what the package is/does and any specific features that will be provided as a result of its use. For instance a scenery package may include a list of included airfields and any naviads and their associated frequencies.
- step by step installation instructions. Never assume a user will know what is required of them to get the download working. If the files simply need to be extracted into a specific directory explain each step required to extract the files to that directory.
- valid contact information. The user should always have a way to contact the developer/publisher in the event that they encounter problems with the software. If the user knows that they are able to contact someone when something goes wrong you will earn their trust as a developer and you may find that your work gains a following in the flightsim community.

Preparation for Upload

· File Format: The AusFlightSim File Library will only accept ZIP files for upload. Attempting to upload files of any other type will fail automatically. The latest versions of Windows have a Compressed Folder feature that can be utilised to package your files into a ZIP file. There are also several applications freely available specifically for this purpose. The most popular for Windows operating systems is WinZip. If you cannot package your software into a ZIP file you must host the file elsewhere and use the linking facility to include it in the library.

· Descriptive Text: The ZIP file must also contain a text document that describes what the software is. This text document must also contain the Full Name of the author (no aliases) and a working contact email address. You should also include information about any dependancies your software requires in order function correctly and any specific installation instructions.

When you are satisfied with your packaged file and are ready to submit it to the file library simply go to the Add Download section and complete the details requested on the form.

Large Uploads And File Size Restrictions

The Add Download form is capable of uploading files NOT greater than 50Mb in size. If your file is larger than this or you are having trouble attempting to submit your files via the web form, special access to upload via the AusFlightSim FTP server can be requested. Logon details for the FTP server are provided on a case by case basis and should be requested by completing the contact form. When using the FTP server the details of the file should still be submitted using the Add Download form entering the file name of the file on the FTP server.

After Submission

Once we have received your file it will first be checked to ensure that it is virus free, it unzips properly, contains proper documentation, and does not create legal issues. This process is for the protection of AusFlightSim and it users. This also means that not all files will make it into the public library on the same day. You should allow at least 72 hours to allow AusFlightSim to complete its checks before contacting us. If a problem is found with a submitted file you will be contacted at the address provided as the Author's Email at the time of submission.