-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Relicense all shootout benchmarks to use their preferred license #14248
Comments
Here's the specific license: http://benchmarksgame.alioth.debian.org/license.php It actually looks like a three-clause BSD license with the advertising/promotion clause included. |
Ah, yeah, not two-clause BSD. |
Updated OP to reflect that this is not "two-clause" BSD. |
I've touched some of that code a long time ago, not sure if I changed enough to qualify as 'author', but if I have, I hereby grant permission to relicense my stuff to whatever is the required version of the BSD-license. |
I rewrited or modified almost every benchmark. I grant permission to relicense my contributions to the shootout license. (Even under the WTFPLv2 if anyone want) |
I've updated the op with the list of people from whom I have statements on file. |
For those interested in helping with this, this is the statement I've asked the stragglers in #14420 to email me:
|
part of rust-lang#14248, fix rust-lang#14420 Removed @richo's contribution (outdated comment) Quoting @brson: let's move forward with this one. The only statement I'm missing is @richo's and it sounds like his was a minor patch.
I agree to re-license my contributions under the license above. I sent mail to @brson a couple days ago. My name (Andrew Gallant) appears in the first comment. :) |
Part of rust-lang#14248 The authors are @pcwalton and @BurntSushi, and we have their agreement.
…rson Part of #14248 The authors are @pcwalton and @BurntSushi, and we have their agreement. @brson OK?
Part of rust-lang#14248 Main contributors are @pcwalton, @alexcrichton and me. Only @dguenther appear in git blame as a minor contribution, but it is only adding the rust license, so removed by this relicensing.
…, r=brson Part of #14248 Main contributors are @pcwalton, @alexcrichton and me. Only @dguenther appear in git blame as a minor contribution, but it is only adding the rust license, so removed by this relicensing. @brson OK?
part of rust-lang#14248, fix rust-lang#14420 Removed @richo's contribution (outdated comment) Quoting @brson: let's move forward with this one. The only statement I'm missing is @richo's and it sounds like his was a minor patch.
Part of rust-lang#14248 The authors are @pcwalton and @BurntSushi, and we have their agreement.
Part of rust-lang#14248 Main contributors are @pcwalton, @alexcrichton and me. Only @dguenther appear in git blame as a minor contribution, but it is only adding the rust license, so removed by this relicensing.
Everyone agreed. Related to rust-lang#14248, close rust-lang#14718
http://benchmarksgame.alioth.debian.org/u64q/rust.php seem to have switched to Rust 0.11 but do not show results yet. Do they need to be pinged about the license changes or does it just take time? |
@kud1ing I think I've seen somewhere that they want we propose our programs using the official procedure. |
I've opened #15408 for this. |
I agree to relicense any previous contributions to http://github.com/mozilla/rust according to the term of the Computer Language Benchmarks Game license (http://benchmarksgame.alioth.debian.org/license.php) |
Everyone agreed. Related to rust-lang#14248, close rust-lang#15328
Everyone agreed except @thestinger. As @thestinger contribution on this file is trivial, we can relicense it. Related to rust-lang#14248, close rust-lang#15330
I'm not on your list above, but since I wrote the first versions of a couple of these benchmarks, I, too, agree to relicense my contributions to the benchmarks under src/test/bench/ according to the term of the Computer Language Benchmarks Game license (http://benchmarksgame.alioth.debian.org/license.php). |
…r=brson Everyone agreed except @thestinger. As @thestinger contribution on this file is trivial, we can relicense it. Related to #14248, close #15330 @brson OK?
…=brson Everyone agreed. Fix #17078 #14248 seems completed, as every src/test/bench/shootout-*.rs are relicensed after acceptation of this PR except: - shootout-ackermann.rs: obsolete shootout bench - shootout-fibo.rs: obsolete shootout bench - shootout-k-nucleotide-pipes.rs: slower that shootout-k-nucleotide-pipes.rs (and not so interesting as a benchmark) - shootout-pfib.rs: does not seems related to the shootout @brson OK?
This issue seems completed, as every src/test/bench/shootout-*.rs are relicensed except:
OK to close? |
Is one of these meant to be |
oups, typo, corrected in the comment. shootout-k-nucleotide-pipe.rs is supposed to do the same thing as shootout-k-nucleotide.rs, with a task for each k, copying strings readed on stdin. Thus, it is extremelly inefficient. |
Awesome work, thanks for taking the charge on this @TeXitoi! |
@TeXitoi I wrote |
…Veykril fix: show diagnostic for } token followed by else in let else statement fix rust-lang#14221 My thinking is to check if the `expr` after `=` is block like when parse `let ... lese` , and if so, emit error.
The shootout will only accept code that is under a particular variation of the BSD license. We are the authoritative source for this code at the moment, but it's under the Rust license. We can't participate in the shootout on an equal footing without using the proper license.
For each benchmark, either contact all the authors and get written permission to relicense, or just rewrite it; put the correct license on the files and add them as exceptions to licenseck.py.
Have statements from
The text was updated successfully, but these errors were encountered: