search

freckle / yesod-auth-oauth2

OAuth2 authentication for yesod
MIT License
71 stars 53 forks source link

License uncertainty #96

Closed pbrisbin closed 6 years ago

pbrisbin commented 6 years ago

The LICENSE file is a BSD 2-clause license naming Michael Snoyman through 2008. None of that is accurate :). The package file says BSD3, has an author and a maintainer, neither of which are Michael, and it's now 2018.

I want to resolve this. I would like to just bring this in line with all my packages and switch it over the MIT, my name, current year. But I'm not sure if there are any implications to doing this.

I'm not worried in a legal sense; I'm confident that a license change like this just means the code prior to the commit is licensed as it was and the code after the commit is licensed as it is -- I just wouldn't want to cause any annoyance for anyone using this library in a corporate setting.

Considering the current situation is basically too vague to be meaningful (IMO), I'd think my proposed change would be a clear improvement from any perspective. So if no one objects over the next week or so, I'll go ahead with it.

Ping @snoyberg -- you probably don't know your name's on this or how it got there, but I just want to confirm you have no issues with me replacing the LICENSE here.

jferris commented 6 years ago

I have no objection to changing the license as you describe.

snoyberg commented 6 years ago

Good catch, and you're absolutely correct: go ahead.

On Thu, Jan 25, 2018 at 11:17 PM, patrick brisbin notifications@github.com wrote:

The LICENSE file is a BSD 2-clause https://opensource.org/licenses/BSD-2-Clause license naming Michael Snoyman through 2008. None of that is accurate :). The package file says BSD3, has an author and a maintainer, neither of which are Michael, and it's now 2018.

I want to resolve this. I would like to just bring this in line with all my packages and switch it over the MIT, my name, current year. But I'm not sure if there are any implications to doing this.

I'm not worried in a legal sense; I'm confident that a license change like this just means the code prior to the commit is licensed as it was and the code after the commit is licensed as it is -- I just wouldn't want to cause any annoyance for anyone using this library in a corporate setting.

Considering the current situation is basically too vague to be meaningful (IMO), I'd think my proposed change would be a clear improvement from any perspective. So if no one objects over the next week or so, I'll go ahead with it.

Ping @snoyberg https://github.com/snoyberg -- you probably don't know your name's on this or how it got there, but I just want to confirm you have no issues with me replacing the LICENSE here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/thoughtbot/yesod-auth-oauth2/issues/96, or mute the thread https://github.com/notifications/unsubscribe-auth/AADBB-VP1rFMFiUH2Z9GK7b5UYMF3qP7ks5tOO9ygaJpZM4RtgHH .