Delete ChangeLog files Was :Re: ChangeLog change to .ChangeLog

Joel Sherrill joel.sherrill at OARcorp.com
Wed Mar 6 17:56:26 UTC 2013


On 3/6/2013 11:44 AM, Thomas Doerfler wrote:
> Ralf,
>
> Am 06.03.2013 18:34, schrieb Ralf Corsepius:
>> On 03/06/2013 04:20 PM, Gedare Bloom wrote:
>>> If the ChangeLog entry text is by and large replicated already in the
>>> git log, then I see no reason to keep the files hanging around
>>> bit-rotting.
>> Again, ... the git-logs are a temporary internal implementation detail,
>> the ChangeLog files are legal documents.
> Can you elaborate this more clearly? I can't see any legal character in
> the changelogs or any RTEMS project files (except the copyright headers
> and License statements). Nobody sells RTEMS, nobody assures the features
> of RTEMS based on the Changelogs or the git logs. So what exactly do you
> mean the "legal"?
This is an utter and complete BS statement on Ralf's part. If the 
ChangeLog had
any legal standing, then the FSF would NOT require submitters to file
assignment paperwork.

There are also many projects without ChangeLog's including the Linux kernel
which do not have legal problem.

I want to make it emphatically clear that

(1) you are not a lawyer
(2) I am not a lawyer
(3) If you personally feel at legal risk, then you should evaluate what you
personally consider your exposure. If you feel at risk, you should leave at
the project.

We will be doing something to eliminate or rename ChangeLog's.
A majority of core developers have spoken.

We will no longer be bullied by single person on this project.

As the French say "fin"
>> Git is like your employer carrying your working contract's data in their
>> internal database - The only document that counts is the version you
>> have printed.
> Right. But there is no RTEMS contract. At least I did not sign any
> (except the copyright stuff which has no special relationship the the
> Changelogs).
Long ago before either of you were involved, OAR evaluated how to handle 
this.
We had the exposure before anyone else (except Chris) had touched RTEMS. 
This
was a major issue when RTEMS was Army hosted and when it transitioned to
OAR's stewardship.

We decided that submission of code to a public mailing list constituted 
permission
to use that code in RTEMS. Then it was just a matter of verifying the 
license was
appropriate.

This decision was made about 20 years ago and this discussion is just a 
carnival
side-show to protect the ChangeLog's.

Give it up.
> wkr,
>
> Thomas.
>


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985




More information about the devel mailing list