Licensing Requirements for Submissions Poorly Documented

[Joel Sherrill]

The discussion of licensing for code/docs in RTEMS is a bit of a mess right now. After posting this issue to the mailing list (​https://lists.rtems.org/pipermail/devel/2020-April/059489.html), Sebastian pointed out where the actual recommended text for code/docs was located.

SW Engineering Guide sections 6.3.1.2 (Licenses) and 11 (Licensing Requirements) are somewhat overlapping and duplicative. In addition, Gedare's old blog
​http://gedare-csphd.blogspot.com/2013/05/software-licenses-with-rtems.html is still a decent discussion of the underlying issues and goals even though we have moved to BSD-2 and Creative Commons for documentation since he wrote that in 2013.

The above references just describe the rationale and cite the licenses. For an example of what to put in the code, you have to visit ​https://docs.rtems.org/branches/master/eng/coding-file-hdr.html#copyright-and-license-block

I THINK a good solution would be to reference the Chapter 11 Licensing
Requirements from the Coding Conventions chapter. And incorporate an
updated version of Gedare's blog text.

[Chris Johns]

Is this being worked on for the RTEMS 5 release?

[Sebastian Huber]

Yes, this needs to be fixed, however, it is not release critical from my point of view. This stuff is important for new contributors and they should focus on the master. I would move the milestone to 6.1.

[Joel Sherrill <joel@…>]

In [changeset:"2d22d7453d56e9558a11a8f80a3f139018df2da8/rtems-docs" 2d22d74/rtems-docs]:

Error: Processor CommitTicketReference failed

/data/trac/repo/rtems-docs.git does not appear to be a Git repository.