News for hackers. Stuff that matters.

A comment on We're switching to a DCO for source code contributions. Parent comment

Re:We're switching to a DCO for source code contributions by drdaeman on Wednesday November 01, 2017 @11:58PM (#15607732)
Sorry, I must be not getting something, but I'm reading MIT (Expat) license's text and I don't see this.

On the contrary, it says that the copyright notice (= the license) shall be included in all copies (I assume, it's about derivative works as well).

From my understanding, one can throw in some non-MIT files or code pieces, but MIT code shall remain MIT-licensed until rewritten or removed.

Can you please point on where I'm wrong?

[ Parent | on HN ]
Re:We're switching to a DCO for source code contributions by mehrdada on Thursday November 02, 2017 @01:37AM (#15608091)
You are both right. You can relicense MIT, assuming you follow certain requirements, including replicating the copyright notice, but you are not required to give away the source code (even just to the original artifact) at all. The user has to find its own way to the source code.

Replicating the copyright notice for attribution does not imply you are licensing it under MIT. You are following the original license requirements that permit your distribution.

[ Parent | on HN ]