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

feat: add module for control-flow analysis #2827

Merged
merged 7 commits into from
Dec 14, 2018

Conversation

monperrus
Copy link
Collaborator

original code by @marcelinorc

@pvojtechovsky
Copy link
Collaborator

Cool! 🥇

@pvojtechovsky
Copy link
Collaborator

Looks like a nice Christmas present :-)

@surli
Copy link
Collaborator

surli commented Dec 10, 2018

@monperrus thanks for adding this one! Still I have a question regarding the license: the files you added do not have the license header. Does it mean they are in another license? What about the packaging of this module? What does it mean for the releases of Spoon? I really think we should be consistent on that subject: we already have a not-well-known license so let's avoid more ambiguities :)

@nharrand
Copy link
Collaborator

@surli I think in their original repo they had no header, and no licenses at all. As far as I understand, that means that we can do anything we want with them.

So I agree we should put as header the license we want for spoon sub modules.

@surli
Copy link
Collaborator

surli commented Dec 10, 2018

As far as I understand, that means that we can do anything we want with them.

We should have at least the agreement from @marcelinorc here and to put the original repository in the header then.

@nharrand
Copy link
Collaborator

I meant legally speaking. But yes you are right it would be more elegant.

@tdurieux
Copy link
Collaborator

tdurieux commented Dec 12, 2018

@surli I think in their original repo they had no header, and no licenses at all. As far as I understand, that means that we can do anything we want with them.

NO, it is the opposite, we cannot use it. By default, the source code has the same copyright than books. Thus, merging this PR is an explicit violation of the copyright of the author (something like plagia).

@nharrand
Copy link
Collaborator

nharrand commented Dec 12, 2018

Ok. I will write him an email then.

@monperrus
Copy link
Collaborator Author

monperrus commented Dec 12, 2018 via email

@nharrand
Copy link
Collaborator

Not necessarily authoritative: https://choosealicense.com/no-permission/

@surli
Copy link
Collaborator

surli commented Dec 12, 2018

https://en.wikipedia.org/wiki/License-free_software

he software owner has not made explicit the terms of the license which makes the software fully copyright protected according to the Berne convention.

@monperrus
Copy link
Collaborator Author

monperrus commented Dec 12, 2018 via email

@nharrand
Copy link
Collaborator

Marcelino has kindly accepted to put a MIT license on his project as can be seen here so I think we can proceed with merging once we have updated the headers of these files.

@pvojtechovsky
Copy link
Collaborator

Thank you @marcelinorc !

@nharrand
Copy link
Collaborator

nharrand commented Dec 13, 2018

I think this should be ready for review. @pvojtechovsky or @surli WDYT?

<version>1.2.17</version>
</dependency>

<dependency>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

junit, only for test no? And I thought @monperrus did a PR for bringing junit in the parent pom?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR in question is not merge-able yet #2828 if I am not mistaken.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But as soon as it is possible, I agree that we should move junit in parent.

@surli
Copy link
Collaborator

surli commented Dec 13, 2018

Is it possible to add a Readme.md?

@nharrand
Copy link
Collaborator

Yes definitely!

@surli surli merged commit 8a8ef93 into INRIA:master Dec 14, 2018
@monperrus
Copy link
Collaborator Author

monperrus commented Dec 15, 2018 via email

@monperrus
Copy link
Collaborator Author

monperrus commented Dec 15, 2018 via email

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.

5 participants