Working with programmes: Software licensing & quality
Software outputs will normally be licensed as open-source, unless a case has been made to the contrary and accepted by the bid evaluation panel.
You should make the licence mechanisms and the sustainability plan for the software clear throughout the project You should make clear, throughout the project, the:
- licence mechanisms (under which software outputs will be released) that will be put in place for community contribution (users and developers)
- sustainability plan for the software beyond the period of project funding
For open source software development, you should consult with:
You should read and be compliant with:
To be able to re-use the software it must be of a certain quality and maturity. For example, it must have supporting information (FAQ, installation guides, test data etc.) to help others use it. In addition to the advice from the OSS Watch and OMII-UK, elements that contribute to software quality and project maturity are outlined in the Software Quality Assurance (QA) and Open Source Maturity Model (OSMM) development guidelines. You will be expected to follow the recommendations from these sources of guidance.