Re-licensing under the Mozilla Public License version 2

[robertodr]

The project comes under the LGPL3.0+ with a Static Linking Exception (SLE) It could be worthwhile to re-license under MPLv2, since it has the SLE baked in and is a standard license.

This is the list of contributors according to git shortlog --summary --numbered

• [x] @ajborgoo
• [x] @aspgomes
• [x] @chjacob-tubs
• [x] @erebolini
• [x] @juselius
• [x] @miroi
• [x] @bast
• [x] @robertodr
• [x] @sarahr
• [x] @simensr
• [x] @uekstrom

Could you:

1. kindly reply "I hereby agree to publish my contributions to XCFun under the MPLv2 license"?
2. Open a pull request to add a file in the RELICENSE subdirectory of the repository following this template This action is needed in order to leave a "paper trail" of the relicensing (much like the relicensing process in DALTON/LSDALTON)

If you have any objection to relicensing your contributions, explain your reasons

[bast]

I support it. MPLv2.0 is two-way remixable but probably simpler with regards to re-linking requirement. We will however need support from all past contributors.

[robertodr]

Ça va sans dire :wink: I think we need two steps:

1. Open an issue asking for relicensing under MPLv2, like here
2. Create a paper trail in the repository like here

[uekstrom]

I'm fine with the mplv2.

Ulf On Thu, 27 Apr 2017 at 12:03, Roberto Di Remigio notifications@github.com wrote:

Ça va sans dire 😉 I think we need two steps:

1. Open an issue asking for relicensing under MPLv2, like here https://github.com/zeromq/zyre/issues/327
2. Create a paper trail in the repository like here https://github.com/zeromq/libzmq/tree/master/RELICENSE

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17#issuecomment-297670866, or mute the thread https://github.com/notifications/unsubscribe-auth/AMeumfgtwEejIQc62yjVyYDJc-oL9HBHks5r0GfsgaJpZM4NJ70- .

[aspgomes]

i'm fine with it too.

On Thu, Apr 27, 2017 at 12:36 PM, Ulf Ekström notifications@github.com wrote:

I'm fine with the mplv2.

Ulf On Thu, 27 Apr 2017 at 12:03, Roberto Di Remigio <notifications@github.com

wrote:

Ça va sans dire 😉 I think we need two steps:

1. Open an issue asking for relicensing under MPLv2, like here https://github.com/zeromq/zyre/issues/327
2. Create a paper trail in the repository like here https://github.com/zeromq/libzmq/tree/master/RELICENSE

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17#issuecomment-297670866, or mute the thread https://github.com/notifications/unsubscribe-auth/ AMeumfgtwEejIQc62yjVyYDJc-oL9HBHks5r0GfsgaJpZM4NJ70-

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17#issuecomment-297677680, or mute the thread https://github.com/notifications/unsubscribe-auth/AGyI9PV6b_yItG6rXoWz1cXCjBJchoo1ks5r0G_LgaJpZM4NJ70- .

[robertodr]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[chjacob-tubs]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[ajborgoo]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

On 27 Apr 2017, at 14:11, Roberto Di Remigio notifications@github.com wrote:

The project comes under the LGPL3.0+ https://www.gnu.org/licenses/lgpl-3.0.en.html with a Static Linking Exception (SLE) http://zeromq.org/area:licensing It could be worthwhile to re-license under MPLv2 https://www.mozilla.org/en-US/MPL/2.0/, since it has the SLE baked in and is a standard license.

This is the list of contributors according to git shortlog --summary --numbered

@ajborgoo https://github.com/ajborgoo @aspgomes https://github.com/aspgomes @chjacob-tubs https://github.com/chjacob-tubs Elisa Rebolini @juselius https://github.com/juselius @miroilias https://github.com/miroilias @bast https://github.com/bast @robertodr https://github.com/robertodr @sarahr https://github.com/sarahr @simensr https://github.com/simensr @uekstrom https://github.com/uekstrom Could you:

kindly reply "I hereby agree to publish my contributions to XCFun under the MPLv2 license"? Open a pull request to add a file in the RELICENSE subdirectory of the repository following this template https://github.com/robertodr/xcfun/blob/relicense/RELICENSE/relicense-template-mplv2.txt This action is needed in order to leave a "paper trail" of the relicensing (much like the relicensing process in DALTON/LSDALTON) If you have any objection to relicensing your contributions, explain your reasons

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17, or mute the thread https://github.com/notifications/unsubscribe-auth/ANas8bWvgTtzkRbJfJDEhKjbzLDzPaA8ks5r0IXngaJpZM4NJ70-.

[simensr]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[erebolini]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[sarahr]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[robertodr]

@ajborgoo @chjacob-tubs @erebolini @juselius @miroi @sarahr @simensr @uekstrom You should now file a pull request to add a file like this to the repository. You can click on "Create new file", copy-paste the template and then submit. Please close the commit message with [ci skip], so that unnecessary CI builds are avoided. Thank you in advance!

[miroi]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[simensr]

Reminder for @ajborgoo @erebolini @juselius @sarahr @uekstrom

[uekstrom]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[robertodr]

This issue has been open for a while and I would like to close it. If you haven't done so yet, I reiterate my request to @ajborgoo @erebolini @juselius @sarahr @uekstrom to reply to this issue and to generate a new file in the RELICENSE folder following the template

1. Go to https://github.com/dftlibs/xcfun
2. Click on the RELICENSE folder.
3. Click on Create new file
4. Copy-paste the template into the editor window and edit the placeholders ({{ name of company / name of individual }}, {{github username}}, {{github commit author}}, {{name}}, {{ Full Name }} and {{ creation date of document (format: yyyy/mm/dd) }}) with the correct content.
5. The new file should be saved as NameSurname.md.
6. The commit message should state that the new file was created and should have the [ci skip] tag, so that CI jobs on Travis are not triggered.
7. You can save the new file. This should automatically submit a pull request with your changes.

[uekstrom]

Thank you Robert for your excellent instructions! I have committed my file.

Regards, Ulf

2017-11-15 16:01 GMT+01:00 Roberto Di Remigio notifications@github.com:

This issue has been open for a while and I would like to close it. If you haven't done so yet, I reiterate my request to @ajborgoo https://github.com/ajborgoo @erebolini https://github.com/erebolini @juselius https://github.com/juselius @sarahr https://github.com/sarahr @uekstrom https://github.com/uekstrom to reply to this issue and to generate a new file in the RELICENSE folder following the template https://github.com/dftlibs/xcfun/blob/master/RELICENSE/relicense-template-mplv2.txt

1. Go to https://github.com/dftlibs/xcfun
2. Click on the RELICENSE folder.
3. Click on Create new file [image: untitled] https://user-images.githubusercontent.com/3708689/32841793-9a5e0dc6-ca1b-11e7-8dd1-70e26dd3c41a.png
4. Copy-paste the template into the editor window and edit the placeholders ({{ name of company / name of individual }}, {{github username}}, {{github commit author}}, {{name}}, {{ Full Name }} and {{ creation date of document (format: yyyy/mm/dd) }}) with the correct content.
5. The new file should be saved as NameSurname.md. [image: selection_001] https://user-images.githubusercontent.com/3708689/32842617-d2f9c1be-ca1d-11e7-839f-65c5316faa14.png
6. The commit message should state that the new file was created and should have the [ci skip] tag, so that CI jobs on Travis are not triggered.
7. You can save the new file. This should automatically submit a pull request with your changes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17#issuecomment-344618630, or mute the thread https://github.com/notifications/unsubscribe-auth/AMeumRugixUN59N1NN6QFHkRr-yqB-UIks5s2vyFgaJpZM4NJ70- .

[juselius]

I hereby agree to publish my contributions to XCFun under the MPLv2 license

[robertodr]

REMINDER This issue has been open for a while and I would like to close it. If you haven't done so yet, I reiterate my request to @ajborgoo @erebolini to reply to this issue and to generate a new file in the RELICENSE folder following the template

1. Go to https://github.com/dftlibs/xcfun
2. Click on the RELICENSE folder.
3. Click on Create new file
4. Copy-paste the template into the editor window and edit the placeholders ({{ name of company / name of individual }}, {{github username}}, {{github commit author}}, {{name}}, {{ Full Name }} and {{ creation date of document (format: yyyy/mm/dd) }}) with the correct content.
5. The new file should be saved as NameSurname.md.
6. The commit message should state that the new file was created and should have the [ci skip] tag, so that CI jobs on Travis are not triggered.
7. You can save the new file. This should automatically submit a pull request with your changes.

[bast]

@robertodr everybody is checked on top but I guess @ajborgoo is missing?

[ajborgoo]

I did it just now. (I’ve tried to do this before.)

I didn’t get to choose between “Commit directly to master” or “Crete branch and start pull request” as described in step 5 of one of the previous e-mails. I managed to click the green button and I hope it’s done right this time.

Sorry for being so slow on this. A

On 4 Apr 2018, at 11:40, Radovan Bast notifications@github.com wrote:

@robertodr https://github.com/robertodr everybody is checked on top but I guess @ajborgoo https://github.com/ajborgoo is missing?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17#issuecomment-378541938, or mute the thread https://github.com/notifications/unsubscribe-auth/ANas8VhdCHw5sEaVuMTfxaHvXliWoBYwks5tlJUXgaJpZM4NJ70-.

[ajborgoo]

Now GitHub proposes to do a pull request. Should I do this, or has it been done automatically (as it said in the previous window?) A

On 4 Apr 2018, at 13:23, Alex Borgoo ajborgoo@gmail.com wrote:

I did it just now. (I’ve tried to do this before.)

I didn’t get to choose between “Commit directly to master” or “Crete branch and start pull request” as described in step 5 of one of the previous e-mails. I managed to click the green button and I hope it’s done right this time.

Sorry for being so slow on this. A

On 4 Apr 2018, at 11:40, Radovan Bast <notifications@github.com mailto:notifications@github.com> wrote:

@robertodr https://github.com/robertodr everybody is checked on top but I guess @ajborgoo https://github.com/ajborgoo is missing?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dftlibs/xcfun/issues/17#issuecomment-378541938, or mute the thread https://github.com/notifications/unsubscribe-auth/ANas8VhdCHw5sEaVuMTfxaHvXliWoBYwks5tlJUXgaJpZM4NJ70-.

[robertodr]

Thanks @ajborgoo and yes, go ahead with the PR.