Contribute Software
Other ways to Contribute

Contribute Software

A 1999 survey by the Tennessee DOT indicates there is an abundance of in-house bridge engineering software developed by DOTs. 95% of the survey respondents indicate they use in-house software in their daily production work. Contributing this software to the Alternate Route Project will not diminish the value or quality of this software. In fact, just the opposite is likely to occur. It costs virtually nothing to make the contribution and the potential benefits are tremendous. You never know, someone may take your favorite old DOS program and turn it into your favorite new Windows program.

Contributing new or existing software

Contributing new or existing software to the Alternate Route Project is unbelievably simple. All you have to do is follow the three easy steps outlined below.

1. Adding License Notice to Source Code

For each source code file add the following text at the top of the file:

<one line to give the program’s name and a brief idea to what it does.>

Copyright yyyy <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the Alternate Route Open Source License as published by the Washington State Department of Transportation, Bridge and Structures Office.

This program is distributed in the hope that it will be useful, but distribution is AS IS, WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Alternate Route Open Source License for more details.

You should have received a copy of the Alternate Route Open Source License along with this program; if not, write to the Washington State Department of Transportation, Bridge and Structures Office, 4500 3rd AVE SE – P.O. Box 47340, Olympia, WA 98503, USA or e-mail Bridge_Support@wsdot.wa.gov

If your program is interactive, and it uses a splash screen, make it display the following notice on the splash screen.

Copyright yyyy, <name of author>, This software is licensed under the terms and conditions of the Alternate Route Open Source License.

WSDOT has gone the extra step and presents the full text of the license agreement every time the program is started. The license becomes binding by ensuring that the licensee has read or should have read the license agreement and agrees with its terms and conditions. You might want to make this extra effort as well. The WBFL provides a ready to use component for just this purpose.

2. Add License Agreement to your Distribution

For each program you distribute, you must also distribute a copy of the Alternate Route Open Source License. The easiest way to do this is to put a copy of the license agreement into the program folder during installation.

WSDOT recommends the practice of "click-wrapping" software distributions. During the installation process, the user is presented with the full text of the license agreement. By clicking on an "Accept" button, the user indicates acceptance of the terms and conditions of the license. By clicking on a "Decline" button, the user  declines and the installation is aborted. Presenting the license agreement up front, and requiring the user to take an action, will make enforcement of the license much easier in the unlikely event of a dispute.

3. Distribute the Software

You can distribute your program using any method you like. You could mail out CD ROMs or setup a web site for download. You can distribute your software for free or for a fee, it doesn't matter.

Do you have to distribute the source code with the executable program? No, but you could if you like. However, you must provide either a separate download for the software or accompany your distribution with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the source code.


Copyright 1999-2000, Washington State Department of Transportation