[RTEMS Project] #3962: Licensing Requirements for Submissions Poorly Documented

[RTEMS trac]

#3962: Licensing Requirements for Submissions Poorly Documented
----------------------------+--------------------
  Reporter:  Joel Sherrill  |      Owner:  (none)
      Type:  defect         |     Status:  new
  Priority:  high           |  Milestone:  5.1
 Component:  doc            |    Version:  5
  Severity:  major          |   Keywords:
Blocked By:                 |   Blocking:
----------------------------+--------------------
 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.

--
Ticket URL: <http://devel.rtems.org/ticket/3962>
RTEMS Project <http://www.rtems.org/>
RTEMS Project