It really bothered me that every file I open up has (c) The Core developers written on it. We are modifying this code too -- so we should put our copyright notices on each file as well. Why not? I apologize for the hugeness of this diff. I promise it's just top-of-file commends for each file in question and nothing more. It's possible that also the linter picked up some stuff too from files that it has never seen. If so -- sorry!
Details
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- copyright_update
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 728 Build 728: arc lint + arc unit
Event Timeline
Oops.. a few files already had the (c) message so it was duplicated. Removed duplicates.
I think we should only apply "our" copyright notices to files where we have made actual changes, not introduce a blanket claim on files with minimal changes (e.g. formatting only etc).
As developers we shouldn't be so lazy to not add/update it when we make changes to files.
Once in a while one can scan for modified files for which the copyright hasn't been added or updated correctly, and fix them.
The bitcoin developers do not exclude core, it's good. Piling up junk in the header that need to be manually updated is a failure to leverage source control anyway.
@freetrader so you're decidedly against changing copyright notices to include us?
Well the thing is the MIT license allows people to create derivative works provided the original copyright notice appears alongside any new copyright notices. It's basically 'academic'-style credit. I wanted to add us so that if someone now creates a derivative work it's clear that their work is based off our sources which are based off core's which are based off Satoshi's, etc.
It was more out of respect for the license, and respect for all of our work going forward in the future that I decided to add these notices.
The notices already appear where it's important -- in the app gui, in the source repository, etc. But it would complete the cycle to also have them in all the source files, is all.
so you're decidedly against changing copyright notices to include us?
@CCulianu : please read what I wrote.
I'm against pasting "Bitcoin developers" copyright notices on files where we haven't made any meaningful changes so far.
I'm also firmly against removing "Bitcoin Core" and replacing it by just "Bitcoin developers" as deadalnix suggests. That would not be preserving correct attribution. It's not a "failure to leverage source control" either, it's just something that's not done. If the header at the top of the file bothers anyone, move them to the bottom, preserving attribution.