Clemens Brunner

Removing is even better. I don't think every file needs to have the license when there is a license in the root.

Good points @larsoner. Then I'm also +0 on removing the license line. I'm also OK with removing authors only in `mne/`. If we keep them in `examples/` and `tutorials/`, we...

I still think names in the source code only make sense if they are kept up to date. I rarely bother to put my name there, but now this makes...

> i would say add your name to the files you feel a clear ownership for. I don't want your name in the files then don't. It's not about me....

Regarding the comment by @jasmainak, you show up in the blame of the file you linked to, so `git blame` does not stop working when files are re-organized. GitHub shows...

Here's a shell command that prints out all contributors of a file: ``` git --no-pager log --follow --pretty=format:"%aN " mne/report/report.py | sort | uniq ``` The important bit is the...

> I'm okay with having the names of the original authors of a module / function listed on top. I don't care if I'm listed even if I contributed a...

> I'd argue that then the name list become meaningless, no? For all points mentioned here: ownership, visibility, pride, ... But everyone who contributed has the same right to get...

I agree with @sappelhoff 100%!

Examples and tutorials are typically touched by far fewer individuals, so it should not be a problem to include all names. Even when someone "just" fixes typos (BTW I think...