Amaan,
If you only write the code in the file, then it is only your
individual copyright that goes on it.
For integrating 3rd party code, especially from BSD sources, you might
look at the rtems-libbsd method of handling this:
https://git.rtems.org/rtems-libbsd/tree/CONTRIBUTING.md
It is preferred in all new RTEMS development to use a 2-clause BSD
license, rather than the original RTEMS license.
Gedare
On Fri, Jun 15, 2018 at 6:16 AM, Amaan Cheval wrote:
> Hi!
>
> In some RTEMS source files I see a series of copyright notices,
> including those for individuals and corporations, for eg.:
> https://git.rtems.org/rtems/tree/cpukit/score/cpu/arm/include/rtems/score/cpu.h#n7
> https://git.rtems.org/rtems/commit/?id=660db8c86fa16dc67c40bdeebbf671e50a7f3087
> (again, in cpu.h)
>
> I was just wondering how this ought to be for new code. Is this meant
> to be handled on a file-by-file basis? I don't see anything about it
> on the wiki either.
>
> For now I'm using this, let me know if I need to add OAR to the comment too:
>
> https://github.com/AmaanC/rtems-gsoc18/blob/ac/daily-01-compile-stub/cpukit/score/cpu/x86_64/include/rtems/score/cpu.h#L10
>
> I haven't yet, but I'll likely also port FreeBSD sources soon - in
> that case I ought to just preserve the file as much as possible to
> make future updates easier, right? (That is, no changes made to the
> copyright or added to the code if we can avoid it (by adding new files
> for customizations on top, for eg.)).
>
> Cheers
> ___
> 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
