Choosing a Software Licence

Recommending a licence means matching the needs in the scenario to a licence type, then justifying your choice. Describing both types without deciding is not a recommendation, and saying it is up to the developer is not a choice either.

Start with the developer

Ask what the person or company releasing the software wants. If they want to earn money by selling copies and keep the source code secret so nobody can copy or change it, a proprietary licence fits: it restricts copying, modifying and redistributing, which protects the owner's work and income. If they want others to view, improve and share the code, an open source licence fits, because the source code is available for anyone to change and pass on. Open source does not stop a developer earning: they can charge for support and services rather than for the software itself.

Then think about the user

• If the user needs to change the software to suit their own work, open source gives them the source code to edit.
• If the user needs professional support and regular updates, proprietary software usually has a company behind it.
• If the user has little money and can install software themselves, open source is usually free of charge.

Decide, then justify

For example, a mobile pet-grooming business has a booking and reminder system built for it. The owner wants to charge other grooming salons to use the same system and hide how it works, so a proprietary licence suits them: charging other salons earns money, and the restrictions stop them copying or passing the system on. Now picture a beekeeper who wants a hive-record app but has no budget, while her nephew, who is studying computing, can edit the code to record extra details about each hive. Open source suits her: it costs nothing and the code can be adapted to her hives.

A strong recommendation covers both types, weighs the advantages and disadvantages for the people involved, and is organised clearly in paragraphs or a table.