2024-12-22 - 02:36

Dates and Events:

OSADL Articles:

2024-10-02 12:00

Linux is now an RTOS!

PREEMPT_RT is mainline - What's next?


2023-11-12 12:00

Open Source License Obligations Checklists even better now

Import the checklists to other tools, create context diffs and merged lists


2023-03-01 12:00

Embedded Linux distributions

Results of the online "wish list"


2022-01-13 12:00

Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completed

Another important milestone on the way to interoperable Open Source real-time Ethernet has been reached


2021-02-09 12:00

Open Source OPC UA PubSub over TSN project phase #3 launched

Letter of Intent with call for participation is now available



Open Source License Checklists - Editiorial notes

Implicit obligations

Explanation (Raw data)

A license may contain implicit obligations, if a more general obligation mentions a prerequisite that must not necessarily be available. For example, the obligation

YOU MUST Provide License text In Documentation OR Distribution material

gives no instruction how to act, if the software came without documentation or distribution material. Thus, an explicit version of this obligation may read either

  • You must provide the license text in the documentation or in distribution material, if such material came with the software. If it did not, this obligation is void.

or

  • You must provide the license text in a documentation or in distribution material. If such material did not come with the software or it did, but does not contain the license, appropriate documentation or distribution material must be created and at least the license text must be included in it.

In the checklist "language", the first interpretation would be encoded as

IF Documentation OR Distribution material Is Available

YOU MUST Provide License text In Documentation OR Distribution material

while the second interpretation simply would become

YOU MUST Provide License text In Documentation OR Distribution material

and imply that such material must be created if not available.

The second interpretation is assumed in all checklists, unless the license specifies otherwise.

Last modified: January 8, 2024 22:43

Checklists project disclaimer

Request for approval of checklists project participants

Please assist us to validate the above text. When clicking on the below button, you confirm that you approve the text in its current version taking into account the disclaimer below the text.

Request for feedback from checklists project participants

Please assist us to improve the above text taking into account the disclaimer below the text. Your feedback will be integrated into the text as soon as possible, and you will be notified. We gratefully acknowledge any comments, amendments and additions.

Links