On Wed, Jul 26, 2023 at 4:28 AM Karel Gardas <karel@functional.vision> wrote: > > --- > eng/license-requirements.rst | 18 +++++++++++++++++- > 1 file changed, 17 insertions(+), 1 deletion(-) > > diff --git a/eng/license-requirements.rst b/eng/license-requirements.rst > index b2720f2..b9eea9a 100644 > --- a/eng/license-requirements.rst > +++ b/eng/license-requirements.rst > @@ -98,9 +98,25 @@ these guidelines: > * Advertising obligations are not acceptable. > > * Some license restrictions may be permissible. These will be considered > - on a case-by-case basis. > + on a case-by-case basis. See below for a list of such restrictions. > > In practice, these guidelines are not hard to follow. Critically, > they protect the freedom of the RTEMS source code and that of end users > to select the license and distribution terms they prefer for their > RTEMS-based application. > + > +License restrictions > +-------------------- > + > +* Apache License 2.0 in section 4 (b) requires modified files to carry > + prominent notice about performed modification. In case you modify such > + file and the notice is not there yet you are required to put notice > + below at the top of the modified file. If the notice is already > + there you don't need to add it second time. > + The notice should look: > + > + .. code-block:: c > + > + /* > + * The file was modified by RTEMS contributors. > + */
Add a note about NOTICES (and that we currently don't have one.) > -- > 2.25.1 > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel