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

Add MIT License #57

Merged
merged 1 commit into from
Mar 8, 2020
Merged

Add MIT License #57

merged 1 commit into from
Mar 8, 2020

Conversation

cugu
Copy link
Contributor

@cugu cugu commented Sep 16, 2019

@GreyCat
Copy link
Member

GreyCat commented Sep 25, 2019

Technically and legally, we should reach out to contributors of tests repo and get their approvals to license their work in tests repo using MIT license:

An ask for everyone mentioned on this list: please provide your approval / disapproval to license your work as per MIT license in this issue?

@jchv
Copy link
Contributor

jchv commented Sep 25, 2019

I approve of this.

@ams-tschoening
Copy link
Contributor

I approve this.

@LogicAndTrick
Copy link
Collaborator

Yep, works for me.

@adrianherrera
Copy link
Member

This is fine by me.

@nolta
Copy link
Contributor

nolta commented Sep 26, 2019

Sure, approved.

@13rac1
Copy link
Contributor

13rac1 commented Sep 26, 2019

I approve.

@koczkatamas
Copy link
Member

I approved myself :D

@jchv
Copy link
Contributor

jchv commented Oct 6, 2019

Status

Here's where we're at.

Here is a table of the currently missing approvals. The word 'significant' here is meant to refer to contributions that are large enough to be considered expressions. (notably, I am not trying to suggest such contributions are not meaningful to the project, just looking at this from a point of view strictly focused on copyright/relicensing.) The bar for originality and non-triviality in terms of copyright differ by jurisdiction, so only the absolute smallest and most trivial contributions will be considered not significant in this case. (Just to be sure, I am not a lawyer, and this does not constitute legal advice.)

Developer Commits Added Removed Significant? Have Email
@markbook2 1 8 0 Maybe?[1]

[1] The sole contribution adds a few declarations to tests. Although relatively small, I believe these changes may clear the bar for copyrightability in some jurisdictions.

What to do

(I have no decision making power, this is just my personal suggestion.)

  • Now:

    • Attempt to reach developers via e-mail? This should be coordinated in order to avoid having multiple people do it. I am not posting e-mail addresses here out of respect for privacy.
  • In the event not everyone can be reached:

    • Undo commits from developers that we are unable to get consent from.
    • Apply license change.
    • Possibly rewrite changes from scratch based on their intended effects, or simply continue to try to get consent from original authors to reapply later.

@mickdekkers
Copy link
Contributor

Hi there, I just noticed this ping 🙂

I approve 👍

@cugu
Copy link
Contributor Author

cugu commented Oct 27, 2019

I'll send out some mails.

@cugu
Copy link
Contributor Author

cugu commented Oct 27, 2019

@adamiwaniuk's email account does not exist any more.

@sealmove
Copy link
Member

I approve.

1 similar comment
@modernikarus
Copy link
Contributor

I approve.

@cherue
Copy link
Contributor

cherue commented Feb 5, 2020

I approve and I'd like to add that all my contributions to any of the kaitai-io organization repositories are licensed as CC0.

@adamiwaniuk
Copy link

I approve.

@CWood1
Copy link
Contributor

CWood1 commented Feb 7, 2020

I approve of the change

@GreyCat
Copy link
Member

GreyCat commented Feb 7, 2020

Hurray! Looks like we only miss consent of @markbook2. I'll try to reach out to them.

@cherue
Copy link
Contributor

cherue commented Feb 22, 2020

Looking at @markbook2's commit there are two types of changes:

  1. Two tests are marked as skipped, this can only be done one way so it can be copied
  2. Two tests are marked as "not risky"

The two tests are "risky" because they do not have any assertions, see PHPUnit docs. PHPUnit calls tests like these "useless" but they are not in this case. What is being tested is that the generated PHP is syntactically correct and that it parses some data file without throwing errors. Instead of marking individual tests as "not risky" it is possible to tell PHPUnit that this type of test is ok by passing the --dont-report-useless-tests command line option in run-php.

So, if the decision was made to revert that commit the reimplementation could be:

  • Add $this->markTestSkipped(); to kaitai_struct_tests/spec/php/Debug0Test.php and kaitai_struct_tests/spec/php/DebugEnumNameTest.php
  • Add --dont-report-useless-tests to kaitai_struct_tests/run-php

@GreyCat
Copy link
Member

GreyCat commented Feb 27, 2020

@markbook2: you seem to be busy these days, but any chance you can sign this off, so we can move forward with adding the license?

@GreyCat
Copy link
Member

GreyCat commented Mar 8, 2020

@cherue @cugu Phew, looks like we're now in full agreement and ready to apply the license. Thanks for this tremendous job, everyone!

@GreyCat GreyCat merged commit 86ff516 into master Mar 8, 2020
@GreyCat GreyCat deleted the add-license branch March 8, 2020 22:18
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

Successfully merging this pull request may close these issues.