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

We need a license #4

Closed
jacobhinkle opened this issue Feb 23, 2012 · 4 comments
Closed

We need a license #4

jacobhinkle opened this issue Feb 23, 2012 · 4 comments
Labels

Comments

@jacobhinkle
Copy link
Owner

Title says it all. GPL, BSD, other?

@ghost
Copy link

ghost commented Feb 23, 2012

I like GPL because it keeps things open, and I like BSD because it keeps
things free (in the most libertarian sense). Really it's up to mr. manager.
On Feb 22, 2012 10:39 PM, "Jacob Hinkle" <
reply@reply.github.com>
wrote:

Title says it all. GPL, BSD, other?


Reply to this email directly or view it on GitHub:
#4

@jacobhinkle
Copy link
Owner Author

yes, let's not have a general GPL-BSD debate. For this tiny program I think GPL is probably appropriate even though I advocate BSD for lots of other stuff. The thing is this is not an end-user program, but more part of a toolchain, so I think it should be GPL. That matches octave, julia, R, and probably others. On the vis client side, VTK has a BSD-like license and vistrails is GPL. This is only an issue if we want to have some sort of plugin architecture where people link our code or something. I'm not sure how shmem would effect license issues. Depends how we implement it I suppose.

@cscheid
Copy link
Collaborator

cscheid commented Feb 24, 2012

There was some discussion at some point about moving vistrails to bsd, for whatever that's worth.

@jacobhinkle
Copy link
Owner Author

Then as Herr Manager I'll declare us GPL :-)

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

No branches or pull requests

2 participants