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

License #48

Closed
wendtke opened this issue Jul 1, 2019 · 7 comments
Closed

License #48

wendtke opened this issue Jul 1, 2019 · 7 comments
Assignees
Labels
high priority Meta-work Description, README, CI, documentation, test question Further information is requested

Comments

@wendtke
Copy link
Owner

wendtke commented Jul 1, 2019

Update #11 and #45 with final decision

  • End-user license (MIT vs. GPL)
    "Worst" case scenario: company takes psyphr, puts GUI on it, and sells it (could be with or without attribution). Let's talk through the scenario with each license and consider if we are comfortable with which/either outcome.

  • Can we change license after making repo public or submitting/publishing?
    GBA 20190714 suggested not to do so:

Yes, I think you should be able to change licenses down the line, with all coauthors’ agreement. I’d try not to too often, though—if people ever use it within other things they make, I think a change from MIT to GPL might affect what they can do (if they’re creating under a license that isn’t open source). The general consideration, when you are maintaining a package, is to try to limit the changes you make that could break a lot of things “downstream” for people who might be building off your package. This, of course, is only a big issue when the package has a lot of users, which isn’t the case for plenty of packages (although I think yours could get a lot of downstream development, where people are using your package as a dependency in their own package). But it’s not the end of the world if you change your license later, I think.

Resources from GBA
R Packages
Understanding Open Source and Free Software Licensing

@wendtke
Copy link
Owner Author

wendtke commented Jul 9, 2019

@geanders also recommended we discuss this licensing concern with CSU folks (maybe these people)

@iqis
Copy link
Contributor

iqis commented Jul 11, 2019

Would the university care? It may be worth it to ask. Like, hey we're doing this psyphr thing and it benefited from such and such university resources, we're planning to release it under XXX license, is it OK?

@wendtke
Copy link
Owner Author

wendtke commented Jul 11, 2019

Yes, I will check with CSU -- once @geanders and I find the right person to contact!

@geanders
Copy link

I've talked with Steve Foster (https://csuventures.org/about/people/steve-foster/) at CSU Ventures before, and I think he might be helpful to talk with. If he doesn't know answers, he might be able to point to someone who does.

@wendtke
Copy link
Owner Author

wendtke commented Jul 12, 2019

Just emailed him.

@wendtke wendtke self-assigned this Jul 15, 2019
@wendtke wendtke added Meta-work Description, README, CI, documentation, test question Further information is requested high priority labels Jul 15, 2019
@wendtke
Copy link
Owner Author

wendtke commented Jul 17, 2019

We are going to stick with MIT.

@wendtke wendtke closed this as completed Jul 17, 2019
@iqis iqis reopened this Jul 18, 2019
@iqis
Copy link
Contributor

iqis commented Jul 18, 2019

Done @ 389ba1e

@iqis iqis closed this as completed Jul 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high priority Meta-work Description, README, CI, documentation, test question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants