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

The license is non-free #17

Closed
bowlofeggs opened this issue Feb 10, 2019 · 27 comments
Closed

The license is non-free #17

bowlofeggs opened this issue Feb 10, 2019 · 27 comments

Comments

@bowlofeggs
Copy link

bowlofeggs commented Feb 10, 2019

Greetings!

I see that you are using a custom license that includes the restriction "The Software may not be used in
any system whose intent is harm any person's privacy, body or mind." I am not a laywer, but this seems similar to the JSON license's clause that the software must be used for good and not evil. You can use a web search to find analysis on why that license is considered non-free.

Though the goal does seem good, one of the problems with the text is that it does not define what "harm" is (similar to how "evil" and "good" are not easy to define in the JSON license).

I recommend relicensing under an OSI approved license.

@oli-obk
Copy link
Owner

oli-obk commented Feb 10, 2019

This is kinda on purpose. If someone worries about whether the term "intent to harm" applies to them, it does.

I don't really have an issue with going to a free license. If someone makes a relicense PR with checkboxes for all past, present and future contributors, I'll merge it without complaint.

@bowlofeggs
Copy link
Author

Do you really mean to include future contributors as a criteria for relicensing?

@oli-obk
Copy link
Owner

oli-obk commented Feb 25, 2019

lol, no, sorry. But the license change should include wording so that any contributions (past and future) are under e.g. Apache2 + MIT licenses.

@bowlofeggs
Copy link
Author

Cool. For past contributors, we can try to see if we can contact them to ask if they are willing to switch to a free license. For future contributors, I recommend using the DCO - it's just a way for contributors to certify that their patch is FOSS and more explicitly, that they grant it to the project under the same license as the project.

@bowlofeggs
Copy link
Author

Greetings contributors! I propose relicensing this project under an OSI approved license. Could each of you reply with a set of OSI licenses that you would agree with relicensing your past contributions under? If there are some common licenses that you can all agree to, then we can pick that one. @oli-obk suggested Apache 2.0 or MIT above, for example.

CC @oli-obk @nakeep @chrisxue815 @quadfault @Ryman

@oli-obk The early commits in the repo were from Oliver Schneider - is that you? That's the only name I saw that I didn't CC above.

@chrisxue815
Copy link
Contributor

I don't mind. Any OSI license works for me.

@bowlofeggs
Copy link
Author

bowlofeggs commented Mar 7, 2019

I'll keep a record here for contributors we have heard from:

@quadfault
Copy link
Contributor

Any is fine with me.

@oli-obk
Copy link
Owner

oli-obk commented Mar 8, 2019

@oli-obk The early commits in the repo were from Oliver Schneider - is that you?

yes

@Ryman
Copy link
Contributor

Ryman commented Mar 12, 2019

Any OSI license works for me

Same!

@bowlofeggs
Copy link
Author

Hello @nakeep - are you OK with the proposed license changes?

@bowlofeggs
Copy link
Author

I have written @nakeep an e-mail to see if they are OK with switching the license here.

For reference, they have written two commits:

https://github.com/oli-obk/rust-si/commits?author=nakeep

@oli-obk
Copy link
Owner

oli-obk commented May 13, 2019

worst case we'll revert their commits and open an issue with the general idea of compile-time checking the correctness

@qryxip
Copy link
Contributor

qryxip commented Nov 8, 2019

I've just contributed to this repository. I am OK with the license change.

joseluis added a commit to joseluis/rust-si that referenced this issue Nov 8, 2019
Hi @nakeep, if you read this, please visit the following thread, yours is the last one of the contributors permissions they need to change the license of the project, thank you: oli-obk#17 (comment)
@Endle
Copy link
Contributor

Endle commented Jul 16, 2021

Do we have any updates about this progress?

@oli-obk
Copy link
Owner

oli-obk commented Jul 16, 2021

we could revert @nakeep's commits, their github accounts seems to be dead.

@Endle
Copy link
Contributor

Endle commented Jul 28, 2021

I executed such command

$ git shortlog --summary --numbered --email
    20  Oliver Schneider <[email protected]>
    19  Oliver Schneider <[email protected]>
     9  Oliver Schneider <[email protected]>
     8  Oliver Scherer <[email protected]>
     5  Kevin Butler <[email protected]>
     4  Ryo Yamashita <[email protected]>
     3  Breno Viana <[email protected]>
     2  Carl Scherer <[email protected]>
     2  MuhammadAnnaqeeb <[email protected]>
     2  Oli Scherer <[email protected]>
     2  Oliver Schneider <[email protected]>
     1  Chris Xue <[email protected]>
     1  Lorenz Gorse <[email protected]>
     1  Oliver Schneider <[email protected]>
     1  Oliver Schneider <[email protected]>
     1  Zhenbo Li <[email protected]>
     1  quadfault <[email protected]>

How can we find the two patches committe by nakeep in this list?

@oli-obk
Copy link
Owner

oli-obk commented Jul 28, 2021

git log --author="MuhammadAnnaqeeb <[email protected]>" should work

@Endle
Copy link
Contributor

Endle commented Jul 28, 2021

Thanks @oli-obk
I'm trying to revert these two patches and checking if anything would be broken.

commit fe2b3b6d436bf02127d2ff37857083a3f98acf15
Author: MuhammadAnnaqeeb <[email protected]>
Date:   Sat Nov 26 01:16:28 2016 +0200

    add failing examples, add a test for panic
    
    also switch line ending to LF in .gitattributes to avoid failed tests
    because of  line ending changing while cloning repo. Also avoid copying
    .lock file by listing it in .gitignore

commit fda477c20108470178266fcfaae2bde4cdb3ca75
Author: MuhammadAnnaqeeb <[email protected]>
Date:   Fri Nov 25 06:48:35 2016 +0200

    allow compilation time checks
    
    use format_args!() macro to allow compile time checks. Now code like:
    ```
    let a: i32;
    let b: &mut u8 = &mut 5;
    scan!("{}, {}{", a, *b);
    ```
    will not pass compilation, however code as
    ```
    let a: i32;
    let b: &mut u8 = &mut 5;
    scan!("{:o}, {:o}", a, *b);
    ```
     will pass compilation and fail at runtime

Besides, have we tried to connect him by email?

@oli-obk
Copy link
Owner

oli-obk commented Jul 28, 2021

Besides, have we tried to connect him by email?

I haven't

@Endle
Copy link
Contributor

Endle commented Jul 28, 2021

I'm trying to revert nakeep's first commit by #35

For the other commit fda477c it seems that his change has been overwritten (partially) by otherchanges

$ git blame src/lib.rs | grep -i Muhammad
fda477c2 (MuhammadAnnaqeeb 2016-11-25 06:48:35 +0200 224)     ($text:expr, $($arg:expr),*) => {
fda477c2 (MuhammadAnnaqeeb 2016-11-25 06:48:35 +0200 227)         format_args!($text, $($arg),*);
fda477c2 (MuhammadAnnaqeeb 2016-11-25 06:48:35 +0200 228)     };

@oli-obk
Copy link
Owner

oli-obk commented Jul 28, 2021

I guess just remove

format_args!($pattern, $($arg),*);

and

format_args!($pattern, $($arg),*);

@Endle
Copy link
Contributor

Endle commented Jul 28, 2021

Thanks @oli-obk
Are we good to go?

@oli-obk
Copy link
Owner

oli-obk commented Jul 28, 2021

yes

@Endle
Copy link
Contributor

Endle commented Jul 29, 2021

Hi @oli-obk , do you plan to change the LICENSE file soon?
Besides, I assume a new release (0.1.9?) is needed, so the metadata on crates.io would be refreshed.
https://crates.io/crates/text_io

oli-obk added a commit that referenced this issue Jul 29, 2021
see #17 for approval by all devs
@oli-obk
Copy link
Owner

oli-obk commented Jul 29, 2021

Done!

@MuhammadAnnaqeeb
Copy link
Contributor

I am sorry for very late reply. Please go ahead and change the license. Sadly, years went without me seeing the message. My old Github handle was @nakeep.

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

No branches or pull requests

8 participants