Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dropping copyright lines from frequent contributors #9320

Closed
keszybz opened this issue Jun 18, 2018 · 39 comments
Closed

Dropping copyright lines from frequent contributors #9320

keszybz opened this issue Jun 18, 2018 · 39 comments

Comments

@keszybz
Copy link
Member

keszybz commented Jun 18, 2018

Information about who contributed to which file is already covered by git log and git blame much better. The "copyright by" lines that added manually are often out of date and just unnecessary boilerplate. In particular, all works are covered by copyright without any explicit notice since the 1971 Berne Convention.

Following #9274 and #9302, I'd like to drop the remaining "Copyright" lines. Explicit permission from all "owners" of such a line is requested. There is a long tail of names with just one or a few entries, and getting an answer from all those people would be hard, so I'm targeting just the more frequent contributors for now. If you are OK with dropping your copyright line, please say so in this ticket.
(And If you're not OK, also please say so, so we can keep track.) I'll prepare a patch once there's enough answers.

/cc @teg, @kaysievers, @ssahani, @phomes, @dvdhrm, @ronnychevalier, @zonque, @bluetech, @michich, @haraldh, @titanous, @rojkov, @yuwata, @shawnl, @intelfx

[I used

git grep -h 'Copyright' | sed -r -n 's/.*Copyright.*[0-9,-]+\s*(.+)\s*($|<).*/\1/p'|sort|uniq -c|sort -g

but it's counting is terribly broken.]

@intelfx
Copy link
Contributor

intelfx commented Jun 18, 2018

If you are OK with dropping your copyright line, please say so in this ticket

Yes, I'm of course fine with that.

@ronnychevalier
Copy link
Member

ronnychevalier commented Jun 18, 2018 via email

@rojkov
Copy link
Contributor

rojkov commented Jun 18, 2018

I'm OK.

@teg
Copy link
Contributor

teg commented Jun 18, 2018

I'm ok

@kaysievers
Copy link
Contributor

OK

@zonque
Copy link
Member

zonque commented Jun 18, 2018

Sure, go ahead!

@dvdhrm
Copy link
Contributor

dvdhrm commented Jun 18, 2018

Sure.

@michich
Copy link
Contributor

michich commented Jun 18, 2018

I am OK with this.

@titanous
Copy link
Contributor

Sure.

@ssahani
Copy link
Contributor

ssahani commented Jun 18, 2018

ok

@shawnl
Copy link
Contributor

shawnl commented Jun 18, 2018 via email

@phomes
Copy link
Contributor

phomes commented Jun 18, 2018

Ok. No problem.

@yuwata
Copy link
Member

yuwata commented Jun 18, 2018

Ok.

@keszybz
Copy link
Member Author

keszybz commented Jun 20, 2018

@poettering
Copy link
Member

Hmm, reopening, because afaics we are still lacking some responses.

@poettering poettering reopened this Jun 20, 2018
@falconindy
Copy link
Contributor

Ack.

@flokli
Copy link
Contributor

flokli commented Jun 20, 2018 via email

@pabigot
Copy link
Contributor

pabigot commented Jun 20, 2018

OK.

@martinpitt
Copy link
Contributor

ACK (I don't care about these lines really)

@rhatdan
Copy link
Contributor

rhatdan commented Jun 20, 2018

ACK

@victorenator
Copy link
Contributor

OK

@filbranden
Copy link
Member

OK with me.

@Mic92
Copy link
Contributor

Mic92 commented Jun 20, 2018

ok.

@davidstrauss
Copy link
Member

Okay by me.

@dbuch
Copy link
Contributor

dbuch commented Jun 20, 2018

Ok

@haraldh
Copy link
Member

haraldh commented Jun 21, 2018

ok

keszybz added a commit to keszybz/systemd that referenced this issue Jun 22, 2018
@sebth
Copy link
Contributor

sebth commented Jun 23, 2018

OK.

keszybz added a commit to keszybz/systemd that referenced this issue Jul 2, 2018
@keszybz
Copy link
Member Author

keszybz commented Jul 23, 2018

@keszybz
Copy link
Member Author

keszybz commented Jul 23, 2018

@philips ?

@mbiebl
Copy link
Contributor

mbiebl commented Jul 23, 2018

sure

@andir
Copy link
Contributor

andir commented Jul 23, 2018

OK for me.

keszybz added a commit to keszybz/systemd that referenced this issue Jul 24, 2018
keszybz added a commit to keszybz/systemd that referenced this issue Jul 24, 2018
@michaelolbrich
Copy link
Contributor

ok

@philips
Copy link
Contributor

philips commented Jul 24, 2018

Fine by me @philips

@maximlevitsky
Copy link
Contributor

maximlevitsky commented Jul 24, 2018 via email

@keybuk
Copy link
Contributor

keybuk commented Jul 24, 2018

No.

@piotrdrag
Copy link
Contributor

Sure, OK.

@mvollmer
Copy link
Contributor

Ok.

keszybz added a commit to keszybz/systemd that referenced this issue Oct 31, 2018
keszybz added a commit to keszybz/systemd that referenced this issue Oct 31, 2018
keszybz added a commit to keszybz/systemd that referenced this issue Oct 31, 2018
Ack in systemd#9320.

Also drop some lines with my name.
keszybz added a commit to keszybz/systemd that referenced this issue Oct 31, 2018
lambdadroid pushed a commit to me176c-dev/systemd-boot-me176c that referenced this issue Feb 8, 2019
Yamakuzure pushed a commit to elogind/elogind that referenced this issue Feb 13, 2019
@keszybz
Copy link
Member Author

keszybz commented Jun 7, 2019

Most copyright lines were dropped. A few remain, either for authors who refused or didn't reply. Let's close this.

@Conan-Kudo
Copy link
Contributor

I'm okay with this for everything but macros.systemd.in and triggers.systemd.in files, since these files have to be copied out for people to use it in packaging, and so it's decoupled from the source tree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests