search

cos-archives / hgrid

[UNMAINTAINED] A Javascript-based hierarchical grid that can be used to manage and organize file/folder-like data
Apache License 2.0
23 stars 14 forks source link

Needs a license #55

Closed sloria closed 7 years ago

sloria commented 10 years ago

I am partial to MIT for its simplicity. It is also the license used by both Dropzone and SlickGrid.

It would read like so:

Copyright (c) 2014 Center For Open Science

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

attn: @JeffSpies @jakerose27 @xferguson : Any objections to this?

xferguson commented 10 years ago

Sounds good to me!

jakerose27 commented 10 years ago

Sounds good to me.

Sent from my iPhone

On Feb 23, 2014, at 5:57 PM, Steven Loria notifications@github.com wrote:

I am partial to MIT for its simplicity. It is also the license used by both Dropzone and SlickGrid.

It would read like so:

Copyright (c) 2014 Center For Open Science

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. attn: @JeffSpies @jakerose27 @xferguson : Any objections to this?

— Reply to this email directly or view it on GitHub.

sloria commented 10 years ago

@JeffSpies, this all right with you?

JeffSpies commented 10 years ago

As previously discussed, we've been advised to seek counsel before licensing. As such, we'll have to delay this decision until that happens. I hope to have some of this dealt with within the next several weeks.

We'll take that information, discuss it with all in-house COS developers, and then touch base again with Jake and Alexander.

On Thu, Jun 12, 2014 at 9:24 AM, Steven Loria notifications@github.com wrote:

@JeffSpies https://github.com/JeffSpies, this all right with you?

— Reply to this email directly or view it on GitHub https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45890327 .

xferguson commented 10 years ago

Hey Guys,

Sorry, my email didn't sync and I just got this message!

I'm curious why you want to make it licensed? Just to add a revenue
stream? I think this is potentially dangerous as paywalls can severely
impact adoption rates.

But maybe you already decided and made it licensed. Just let me know
what you are thinking (since my email will sync now!)

Cheers, Alexander

Quoting Jeffrey Spies notifications@github.com:

As previously discussed, we've been advised to seek counsel before licensing. As such, we'll have to delay this decision until that happens. I hope to have some of this dealt with within the next several weeks.

We'll take that information, discuss it with all in-house COS developers, and then touch base again with Jake and Alexander.

On Thu, Jun 12, 2014 at 9:24 AM, Steven Loria notifications@github.com wrote:

@JeffSpies https://github.com/JeffSpies, this all right with you?

— Reply to this email directly or view it on GitHub https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45890327 .

Reply to this email directly or view it on GitHub: https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45900805

bnosek commented 10 years ago

Hi Alexander. We need a license to define the terms of the free distribution and use of the software. Licenses are just as important (if not more so) for free distribution as it is for locking down material for commercialization.

On Sun, Aug 17, 2014 at 6:22 PM, Alexander Ferguson < notifications@github.com> wrote:

Hey Guys,

Sorry, my email didn't sync and I just got this message!

I'm curious why you want to make it licensed? Just to add a revenue stream? I think this is potentially dangerous as paywalls can severely impact adoption rates.

But maybe you already decided and made it licensed. Just let me know what you are thinking (since my email will sync now!)

Cheers, Alexander

Quoting Jeffrey Spies notifications@github.com:

As previously discussed, we've been advised to seek counsel before licensing. As such, we'll have to delay this decision until that happens. I hope to have some of this dealt with within the next several weeks.

We'll take that information, discuss it with all in-house COS developers, and then touch base again with Jake and Alexander.

On Thu, Jun 12, 2014 at 9:24 AM, Steven Loria notifications@github.com wrote:

@JeffSpies https://github.com/JeffSpies, this all right with you?

— Reply to this email directly or view it on GitHub < https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45890327

.

Reply to this email directly or view it on GitHub:

https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45900805

— Reply to this email directly or view it on GitHub https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-52437414 .

xferguson commented 10 years ago

Sure. So which licenses were you considering?

I am completely fin with the MIT license. I am not a lawyer though, and don't know what I should be paying attention to here.

Sent from my Verizon Wireless 4G LTE DROID

Brian Nosek notifications@github.com wrote:

Hi Alexander. We need a license to define the terms of the free distribution and use of the software. Licenses are just as important (if not more so) for free distribution as it is for locking down material for commercialization.

On Sun, Aug 17, 2014 at 6:22 PM, Alexander Ferguson < notifications@github.com> wrote:

Hey Guys,

Sorry, my email didn't sync and I just got this message!

I'm curious why you want to make it licensed? Just to add a revenue stream? I think this is potentially dangerous as paywalls can severely impact adoption rates.

But maybe you already decided and made it licensed. Just let me know what you are thinking (since my email will sync now!)

Cheers, Alexander

Quoting Jeffrey Spies notifications@github.com:

As previously discussed, we've been advised to seek counsel before licensing. As such, we'll have to delay this decision until that happens. I hope to have some of this dealt with within the next several weeks.

We'll take that information, discuss it with all in-house COS developers, and then touch base again with Jake and Alexander.

On Thu, Jun 12, 2014 at 9:24 AM, Steven Loria notifications@github.com wrote:

@JeffSpies https://github.com/JeffSpies, this all right with you?

— Reply to this email directly or view it on GitHub < https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45890327

.

Reply to this email directly or view it on GitHub:

https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-45900805

— Reply to this email directly or view it on GitHub https://github.com/CenterForOpenScience/hgrid/issues/55#issuecomment-52437414 .

— Reply to this email directly or view it on GitHub.

xferguson commented 7 years ago

Was this ever decided? There doesn't seem to be a license attached to the repo/project. Seems like a long time to go without. I still think MIT is the way to go.

JeffSpies commented 7 years ago

Good catch! Osf.io is apache2. @sloria, can we update this one?

On Jul 23, 2017, at 2:50 AM, Alexander Ferguson notifications@github.com wrote:

Was this ever decided? There doesn't seem to be a license attached to the repo/project. Seems like a long time to go without. I still think MIT is the way to go.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

sloria commented 7 years ago

Done.