OpenChain for projects

Jonas Oberg <jonas@...>

Hi everyone,

just a short note of thanks to everyone for your efforts on OpenChain. I
wanted to share with you a recent success story involving OpenChain.

A few months ago, I worked with an open source project from the transport
sector. The project was initially conceived by a municipal department but
later abandoned and taken up by a volunteer group. As they expanded the
scope of the project, they begun facing questions about the origin of the
software, it's license, and their own responsibilities towards other
contributors and users.

Working with this still largely volunteer driven open source project, I
took inspiration from the OpenChain specification and indeed, we discovered
most of the principal requirements apply equally to volunteer open source

- A documented policy for the project in relation to its software
- Awareness building of this policy (c.f. artifact 1.1.2 about training
for software staff)
- A consistent contact point
- Identfication of the FOSS compliance roles
- Release documentation to cover archiving of and preparation of the
compliance artifacts
- A contribution policy
- A process document for external contributions

As you may imagine, we went a bit lighter on the documentation side and
focused on putting reasonable practices in place. And while this is a project
which is not likely to claim OpenChain conformance, I thought it an
interesting practice to apply the OpenChain artifacts in this situation
and it did provide much needed clarity to the volunteers in the project.

At the Open Source Leadership Summit in mid February, I'll give a very short
overview of how we worked with this project to apply principal requirements
from OpenChain in a volunteer context to ensure a consistent and verifiable
management of their open source assets.


Jonas Öberg, Styrelseordförande
Morus konsult AB |
E-mail is the fastest way to my attention

Join to automatically receive all group messages.