Open source: the licence is the beginning, not the maintenance plan

The spotlight is from August; the decision belongs to the organization

The Open Source Observatory’s monthly selection features GIMP in August 2026. It does not prove that it replaces every current tool, reduces costs by a particular percentage or meets your accessibility requirements. None of those comparisons was performed for this article.

OSOR’s updated handbook announcement, published on 27 January 2026, covers evaluation, community participation, funding, licensing and supporting structures. Its guidance page also collects 2021 work on sustainability and member transitions. These are management references, not a new legal obligation or product certification.

Velqory perspective: approve the work, not just the installation

For a small communications team, the decision can start with a bounded task: preparing the usual materials for a campaign. Its operator defines the expected result; the technical team defines distribution and updates; the area owner reserves learning time. A heavy structure is unnecessary, but each task needs a named person and a substitute.

The adoption record should distinguish internal work, contracted support and community participation. Do not promise response times nobody has agreed to provide. If continuity depends on a plugin or script, document who maintains it and what happens when it stops working. We do not assume that any particular GIMP extension exists or is required.

• Functional owner: accepts task outcomes and identifies limitations that block adoption.
• Technical owner: maintains inventory, the update channel and a recovery procedure.
• Manager: funds support and training time, including cover for the most experienced person.

The continuity test often missing from the decision

We propose that a second person who did not prepare the pilot receive its files and procedure and attempt the task in a clean environment. They should be able to locate the approved version, understand the inputs and produce an outcome the functional owner accepts. Record requests for help and undocumented dependencies. Use synthetic or authorized materials; do not expose client documents to the community.

This is a proposed exercise, not an internal experiment this article claims to have completed. The outcome may be adoption, limitation to certain tasks or deferral. A positive decision should include owners and a review after the first usage cycle. Technological autonomy grows when an organization can keep working, not merely when it changes the name of its installed software.