License under dual MIT/Apache-2.0 #139

carllerche · 2018-02-15T21:32:09Z

carllerche · 2018-02-15T21:32:33Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

jasondavies · 2018-02-15T21:33:14Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

hockeybuggy · 2018-02-15T21:33:31Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

khaledkbadr · 2018-02-15T21:33:35Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

phrohdoh · 2018-02-15T21:33:44Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

oconnor663 · 2018-02-15T21:33:54Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

schleumer · 2018-02-15T21:34:15Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

radupopescu · 2018-02-15T21:34:54Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

justinmayhew · 2018-02-15T21:35:08Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

SuperFluffy · 2018-02-15T21:36:23Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

nelsonjchen · 2018-02-15T21:42:12Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

srijs · 2018-02-15T21:42:59Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

…

On Fri, Feb 16, 2018, at 8:32 AM, Carl Lerche wrote: The repository currently does not have an associated license, [preventing] some from contributing. [preventing]: #124 In order to fully relicense this repository, all contributors must sign-off.> You are receiving this notification because you have contributed to this repo.> While smaller changes can't be copyrighted by law, its non-trivial to> find out with certainty whether a given change falls under copyright or> not, due to the nature of the matter. Therefore I'm asking you to agree> to the new terms even if you consider your contributions to be not copyrightable. # Checkoff To agree to the licensing terms, please comment with: > I license past and future contributions under the dual MIT/Apache- > 2.0 license, allowing licensees to chose either at their option.> Thank you! * [ ] @alexcrichton * [ ] @aturon * [ ] @carllerche * [ ] @nelsonjchen * [ ] @hockeybuggy * [ ] @rbalicki2 * [ ] @shepmaster * [ ] @RadicalZephyr * [ ] @munckymagik * [ ] @khaledkbadr * [ ] @funkill * [ ] @Rufflewind * [ ] @vi * [ ] @mbrubeck * [ ] @radupopescu * [ ] @irtefa * [ ] @SuperFluffy * [ ] @theduke * [ ] @phrohdoh * [ ] @tafia * [ ] @sheeldotme * [ ] @kanerogers * [ ] @braddunbar * [ ] @lazyval * [ ] @toddWannaCode * [ ] @oconnor663 * [ ] @mohammadsamir * [ ] @hngnaig * [ ] @DirkyJerky * [ ] @mayhewj * [ ] @jasondavies * [ ] @DmitryBochkarev * [ ] @zmanian * [ ] @baloo * [ ] @schleumer * [ ] @jbendig * [ ] @mre * [ ] @dfockler * [ ] @ineol * [ ] @daschl * [ ] @srijs * [ ] @Freyskeyd * [ ] @danobi * [ ] @kw217 * [ ] @AaronStGeorge * [ ] @jedisct1 * [ ] @CrockAgile * [ ] @tanimoto * [ ] @awelkie * [ ] @matematikaadit * [ ] @rofrol * [ ] @jefflembeck * [ ] @mquandalle * [ ] @iamcodemaker * [ ] @zklapow * [ ] @schuster * [ ] @acobster * [ ] @cgwalters * [ ] @P-E-Meunier * [ ] @mgattozzi * [ ] @steveklabnik * [ ] @dwrensha * [ ] @redaready -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #139

zmanian · 2018-02-15T21:45:16Z

I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to chose either at their option.

shepmaster · 2018-02-15T21:46:00Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

ineol · 2018-02-15T21:51:50Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

mre · 2018-02-15T21:52:58Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

aturon · 2018-02-15T21:54:16Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

kw217 · 2018-02-15T21:57:37Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

kanerogers · 2018-02-15T22:15:20Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

…

On Fri, 16 Feb 2018, 8:57 AM Keith Wansbrough ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB7b56fQAxwdXhGwSMm1XJKGoRO-afFTks5tVKhTgaJpZM4SHiWa> .

vi · 2018-02-15T22:53:33Z

I license past and future contributions to this repository under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

AaronStGeorge · 2018-02-15T23:23:47Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

CrockAgile · 2018-02-15T23:35:32Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

theduke · 2018-02-16T00:29:48Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

RadicalZephyr · 2018-02-16T00:42:10Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

mbrubeck · 2018-02-16T00:58:06Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

tanimoto · 2018-02-16T01:04:11Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Rufflewind · 2018-02-16T02:48:12Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

mohammadsamir · 2018-02-22T09:20:23Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

rbalicki2 · 2018-02-22T18:55:39Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

…

On Thu, Feb 22, 2018 at 4:20 AM, msamir ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEFDVZNyfMZ4La98AuPRmCHaV1qmoSCvks5tXTFZgaJpZM4SHiWa> .

alexcrichton · 2018-02-26T15:38:10Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

dwrensha · 2018-02-27T03:45:23Z

Word.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

jedisct1 · 2018-02-27T06:45:33Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

steveklabnik · 2018-02-27T14:37:37Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

carllerche · 2018-03-07T20:14:24Z

Ping!

@munckymagik @radupopescu @sheeldotme @braddunbar @lazyval @toddWannaCode @hngnaig @rofrol @jefflembeck @mquandalle @iamcodemaker @zklapow @schuster @acobster @cgwalters @P-E-Meunier @mgattozzi @redaready

cgwalters · 2018-03-07T20:24:02Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

jefflembeck · 2018-03-07T20:26:37Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

radupopescu · 2018-03-07T20:29:38Z

Hi,
I replied 20 days ago.
Cheers,

acobster · 2018-03-07T20:37:52Z

Sounds good to me! :)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

iamcodemaker · 2018-03-07T20:59:07Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

mgattozzi · 2018-03-07T21:23:49Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

schuster · 2018-03-07T22:15:15Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

redaready · 2018-03-07T23:42:28Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

P-E-Meunier · 2018-03-08T07:25:37Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

mquandalle · 2018-03-08T11:36:48Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

carllerche · 2018-03-08T17:23:59Z

@radupopescu Woops, sorry about that. Got you this time!

rofrol · 2018-03-08T23:00:39Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

radupopescu · 2018-03-09T08:12:54Z

@carllerche No worries! Cheers!

zklapow · 2018-05-25T16:45:08Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

carllerche · 2018-05-25T20:33:35Z

Ping: @munckymagik @sheeldotme @braddunbar @lazyval @toddWannaCode @hngnaig

tobz · 2018-08-02T00:53:20Z

Roll call! @munckymagik @sheeldotme @braddunbar @lazyval @toddWannaCode @hngnaig

sheeldotme · 2018-08-02T10:24:48Z

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Issue #139 tracks explicit licensing of existing newly created content under MIT / Apache2. However, the repository also contains substantial content from the bootstrap project. As such, it must be licensed under MIT exclusively.

carllerche · 2019-07-16T17:56:49Z

Authors for all existing content on master have been covered by this issue. As such, I will close. Thanks all.

Issue #139 tracks explicit licensing of existing newly created content under MIT / Apache2. However, the repository also contains substantial content from the bootstrap project. As such, it must be licensed under MIT exclusively.

…toring Update contributors list, reorganize about team content

carllerche mentioned this issue Feb 15, 2018

Add a license covering new contributions. #140

Merged

carllerche mentioned this issue Feb 15, 2018

No license for tokio-rs/website repository. #124

Closed

carllerche mentioned this issue Feb 15, 2018

futures.md: fix markup error #137

Merged

carllerche mentioned this issue Jul 16, 2019

Update to only MIT license. #326

Merged

carllerche closed this as completed Jul 16, 2019

jefflembeck pushed a commit to jefflembeck/website that referenced this issue Apr 3, 2020

Merge pull request tokio-rs#139 from COVID19Tracking/about-team-refac…

71d550b

…toring Update contributors list, reorganize about team content

License under dual MIT/Apache-2.0 #139

License under dual MIT/Apache-2.0 #139

Comments

carllerche commented Feb 15, 2018 • edited

Checkoff

carllerche commented Feb 15, 2018

jasondavies commented Feb 15, 2018

hockeybuggy commented Feb 15, 2018

khaledkbadr commented Feb 15, 2018

phrohdoh commented Feb 15, 2018

oconnor663 commented Feb 15, 2018

schleumer commented Feb 15, 2018

radupopescu commented Feb 15, 2018

justinmayhew commented Feb 15, 2018 via email • edited

SuperFluffy commented Feb 15, 2018

nelsonjchen commented Feb 15, 2018

srijs commented Feb 15, 2018 via email

zmanian commented Feb 15, 2018

shepmaster commented Feb 15, 2018

ineol commented Feb 15, 2018

mre commented Feb 15, 2018

aturon commented Feb 15, 2018

kw217 commented Feb 15, 2018

kanerogers commented Feb 15, 2018 via email

vi commented Feb 15, 2018

AaronStGeorge commented Feb 15, 2018

CrockAgile commented Feb 15, 2018

theduke commented Feb 16, 2018

RadicalZephyr commented Feb 16, 2018

mbrubeck commented Feb 16, 2018

tanimoto commented Feb 16, 2018

Rufflewind commented Feb 16, 2018

mohammadsamir commented Feb 22, 2018

rbalicki2 commented Feb 22, 2018 via email

alexcrichton commented Feb 26, 2018

dwrensha commented Feb 27, 2018

jedisct1 commented Feb 27, 2018

steveklabnik commented Feb 27, 2018

carllerche commented Mar 7, 2018

cgwalters commented Mar 7, 2018

jefflembeck commented Mar 7, 2018

radupopescu commented Mar 7, 2018

acobster commented Mar 7, 2018

iamcodemaker commented Mar 7, 2018

mgattozzi commented Mar 7, 2018

schuster commented Mar 7, 2018

redaready commented Mar 7, 2018

P-E-Meunier commented Mar 8, 2018

mquandalle commented Mar 8, 2018

carllerche commented Mar 8, 2018

rofrol commented Mar 8, 2018

radupopescu commented Mar 9, 2018

zklapow commented May 25, 2018

carllerche commented May 25, 2018

tobz commented Aug 2, 2018

sheeldotme commented Aug 2, 2018

carllerche commented Jul 16, 2019

carllerche commented Feb 15, 2018 •

edited

justinmayhew commented Feb 15, 2018 via email •

edited