[PATCH v5] Add new COPYING file

[Chris Johns]

On 19/2/20 5:04 pm, Sebastian Huber wrote:
> On 06/12/2019 07:16, Sebastian Huber wrote:
>> Ping.
>>
>> On 19/12/2018 13:37, Sebastian Huber wrote:
>>> Update #3053.
>>> ---
>>> v2:
>>>
>>> Add Hesham Almatary:
>>>
>>> https://devel.rtems.org/ticket/3053#comment:6
>>>
>>> v3:
>>>
>>> Add Jiri Gaisler:
>>>
>>> https://devel.rtems.org/ticket/3053#comment:7
>>>
>>> I am not sure about the first contribution year.
>>>
>>> v4:
>>>
>>> Add GCI contributors:
>>>
>>> Abhimanyu Raghuvanshi
>>> Himanshu Sekhar Nayak
>>> Jacob Shin
>>> Marçal Comajoan Cara
>>> Pritish Jain
>>> Shashvat Jain
>>>
>>> v5:
>>>
>>> Add GCI contributor:
>>>
>>> Zenon Hans Taneka
>>>
>>> I need names for:
>>>
>>> kaidoho kho237115 at gmail.com
>>> kuaLeYi kualeyidxa at gmail.com
>>>
>>>   COPYING | 47 +++++++++++++++++++++++++++++++++++++++++++++++
>>>   1 file changed, 47 insertions(+)
>>>   create mode 100644 COPYING
>>>
>>> diff --git a/COPYING b/COPYING
>>> new file mode 100644
>>> index 0000000000..2e1339c90e
>>> --- /dev/null
>>> +++ b/COPYING
>>> @@ -0,0 +1,47 @@
>>> +RTEMS is a collection of software from several sources.
>>> +
>>> +Each file may have its own copyright/license that is embedded in the source
>>> +file.  Unless otherwise noted in the body of the source file(s), the following
>>> +copyright notices will apply to the contents of RTEMS.  Copyright lines should
>>> +be sorted by the first year followed by the copyright holder.
>>> +
>>> +(1) BSD-2-Clause
>>> +
>>> +Copyright (C) 2018 Abhimanyu Raghuvanshi
>>> +Copyright (C) 2018 Himanshu Sekhar Nayak
>>> +Copyright (C) 2018 Jacob Shin
>>> +Copyright (C) 2018 Marçal Comajoan Cara
>>> +Copyright (C) 2018 Pritish Jain
>>> +Copyright (C) 2018 Shashvat Jain
>>> +Copyright (C) 2015, 2016 Alexander Krutwig
>>> +Copyright (C) 2013, 2018 Hesham Almatary
>>> +Copyright (C) 2012, 2014 Ralf Kirchner
>>> +Copyright (C) 2012, 2018 Christian Mauderer
>>> +Copyright (C) 2010, 2018 Gedare Bloom
>>> +Copyright (C) 2008, 2018 Sebastian Huber
>>> +Copyright (C) 2005, 2018 Thomas Dörfler
>>> +Copyright (C) 2005, 2018 embedded brains GmbH
>>> +Copyright (C) 1996, 2018 Chris Johns
>>> +Copyright (C) 1996, 2016 Jiri Gaisler
>>> +Copyright (C) 1989, 2018 On-Line Applications Research Corporation (OAR)
>>> +
>>> +Redistribution and use in source and binary forms, with or without
>>> +modification, are permitted provided that the following conditions
>>> +are met:
>>> +1. Redistributions of source code must retain the above copyright
>>> +   notice, this list of conditions and the following disclaimer.
>>> +2. Redistributions in binary form must reproduce the above copyright
>>> +   notice, this list of conditions and the following disclaimer in the
>>> +   documentation and/or other materials provided with the distribution.
>>> +
>>> +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
>>> +AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
>>> +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
>>> +ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
>>> +LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>>> +CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>>> +SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
>>> +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
>>> +CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
>>> +ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
>>> +POSSIBILITY OF SUCH DAMAGE.
> 
> What about this COPYING file?
> 

Does it need to deal with new files being added to the repo?

Should it also discuss what we want in files, ie SPDX?

Chris