Develop and manage openly licensed software

Before making a project public, make sure that at least these essentials are in place:

• the code contains no sensitive data, credentials or confidential information;
• a clear and consistent open license is indicated;
• the repository includes a README with project scope and minimum instructions;
• major dependencies are declared;
• it is clear who maintains the software and how to contact them;
• a channel is available for reports or requests (issues);
• contribution methods are stated, also in a simple way;
• the project is understandable even to those who have not developed it.

Publication is not just a technical act. It serves to make the project findable and reusable. Follow these directions:

• publish the code on a code hosting platform;
• add the files and metadata necessary for understanding the project;
• make the software visible through the channels provided for PA.

Once published, the software enters its life cycle. Simple but consistent management also makes a difference. Follow these guidelines:

• set realistic expectations on maintenance and support;
• organize issue and request management;
• adopt a clear versioning strategy;
• automate testing and monitoring when possible.