-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add MIT License #57
Conversation
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? |
I approve of this. |
I approve this. |
Yep, works for me. |
This is fine by me. |
Sure, approved. |
I approve. |
I approved myself :D |
StatusHere'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.)
[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.)
|
Hi there, I just noticed this ping 🙂 I approve 👍 |
I'll send out some mails. |
@adamiwaniuk's email account does not exist any more. |
I approve. |
1 similar comment
I approve. |
I approve and I'd like to add that all my contributions to any of the kaitai-io organization repositories are licensed as CC0. |
I approve. |
I approve of the change |
Hurray! Looks like we only miss consent of @markbook2. I'll try to reach out to them. |
Looking at @markbook2's commit there are two types of changes:
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 So, if the decision was made to revert that commit the reimplementation could be:
|
@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? |
See kaitai-io/kaitai_struct#474