| | 48 | = OSS Developers = |
| | 49 | |
| | 50 | If you are a developer on the !SourceForge.net site, this section is for you. If you are new to OSS development, we strongly recommend reading [http://producingoss.com/en/index.html Producing Open Source Software] by [http://www.red-bean.com/kfogel/ Karl Fogel]. |
| | 51 | |
| | 52 | == Downloads == |
| | 53 | |
| | 54 | While it might seem like an odd place to start, experience indicates that by thinking about and applying effort to the software being developed being easily down-loadable, pays off in the end. Particularly in the early stages of a development effort, making sure that folks can easily compile the source without a number of odd requirements, will greatly enhance adoption. |
| | 55 | |
| | 56 | == Selecting a license == |
| | 57 | |
| | 58 | !SourceForge.net prefers open source licenses that are [http://www.opensource.org/ OSI compliant] as per the [http://www.opensource.org/docs/osd OSD]. All OSI compliant licenses are available for selection in the [wiki:"Register a project for hosting" project registration] process. What is chosen at this phase will dictate the future of the developed software may be used. Choose with care and with the advice of a lawyer if that makes sense. |
| | 59 | |
| | 60 | == Support your software == |
| | 61 | |
| | 62 | Users will be installing the software developed in a project. A project team will benefit greatly by offering some form of support for the software. Be sure to make clear to users in a readme file or by other means how they will be able to contact the project to get the support they need. Projects that are particularly successful in this area offer a support link or tab on their [wiki:"Project web" project web] page so that when users go there, they know what to do. |
| | 63 | |
