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

[FEATURE REQUEST] Add license to repo #219

Open
darigovresearch opened this issue Sep 10, 2023 · 5 comments · May be fixed by #234
Open

[FEATURE REQUEST] Add license to repo #219

darigovresearch opened this issue Sep 10, 2023 · 5 comments · May be fixed by #234

Comments

@darigovresearch
Copy link
Contributor

Would be helpful to have a license file to know what the license of the repo is, would encourage contributions and forking of the site for other similar hackspaces

@tolland
Copy link
Contributor

tolland commented Sep 29, 2023

I think it might be possible to have a license for new contributions. i.e. put something in the Pull request template to ask the contributor to agree to license the change similarly. I don't really see how this can be done retrospectively without getting agreement from all previous contributors....

@marksteward
Copy link
Member

It's intended to be MIT

@tolland
Copy link
Contributor

tolland commented Sep 29, 2023

who would be the <copyright holders> ? hackspace foundation or London hackspace?

The MIT License (MIT)

Copyright © 2023 <copyright holders>

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.

tolland added a commit to tolland/hackspace-foundation-sites that referenced this issue Sep 29, 2023
@marksteward
Copy link
Member

London Hackspace, the hackspace-foundation bit is legacy from when we were trying to do everything in one place.

@tolland tolland linked a pull request Sep 29, 2023 that will close this issue
tolland added a commit to tolland/hackspace-foundation-sites that referenced this issue Sep 29, 2023
@darigovresearch
Copy link
Contributor Author

Yeah Mozilla does it in an interesting way like "Hackspace foundation and individual contributors"

who would be the ? hackspace foundation or London hackspace?

The MIT License (MIT)
Copyright © 2023
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.

Agree that retroactive will be difficult but potentially can coordinate with previous contributors to post somewhere in the repo that their contributions are under the same license.

Pull request template for future pull requests makes sense too

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 a pull request may close this issue.

3 participants