Add a license?

[manodeep]

I didn't see any obvious license associated with the repo - might be good to add one.

[anton-seaice]

We've definately talked about this, I am not sure where it got to. Each of the component models has licenses, maybe that complicates it.

@micaeljtoliveira ?

[micaeljtoliveira]

Yes, this one here is more complicated (I can sense @aidanheerdegen's head aching just from us talking about it 😆 )

Indeed, each component has its own license. We could add a license here, but basically it would only apply to the files that are not included via the git submodules. That's mostly the CMake stuff, but might still be a good idea. The problem is that it could be misleading. Indeed, the conditions that apply to this piece of software are the combination of all the conditions of the licenses of all the software that is being redistributed.

An alternative would be to have a file listing all the licenses of the components with a short explanation of what I just wrote above.

Anyway, with the planned split of OM3, this is probably a moot point.