opensource/beekeeper-studio
1
0
Fork 0
mirror of https://github.com/beekeeper-studio/beekeeper-studio.git synced 2026-03-13 10:12:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source
This commit is contained in:
Matthew Rathbone
2022-02-27 12:57:10 -06:00
committed by GitHub
parent 3627e00395
commit 826029c753
1 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
CONTRIBUTING.md
View File

@@ -1,6 +1,6 @@
## Contributing Guidelines
Last updated: Feb 15 2022
Last updated: Feb 27 2022
We welcome community contributions! If you're thinking of contributing, thank you!
@@ -17,9 +17,13 @@ We have templates for questions, features, or bug reports, please follow the dir
### Pull Requests
We welcome code contributions. You maintain all copyright to your code, but agree that:
It's usually best to open an issue before spending a lot of time working on the code, just in case someone else is working on the same problem. We're always happy to discuss how to implement or design things to help you before you begin work.
- All contributions to this repository are made under the [MIT License](https://opensource.org/licenses/MIT)
Sometimes we don't merge pull requests if they don't meet our design goals, but we really never want this to happen, so please talk to us!
### Legal
We welcome code contributions. All contributions to this repository are made under the [MIT License](https://opensource.org/licenses/MIT).
What this means practically:
@@ -27,4 +31,14 @@ If you make a PR, the PR code is licensed as MIT. As soon as I merge the code in
Why do it this way?
This makes it easier to ensure that Beekeeper Studio code, and third party derivatives, stay open source, but also allows me to use contributed code as part of the ultimate edition.
Practically speaking, we need to have the ability to relicense Beekeeper Studio in the future if we need to, licensing contributions as MIT lets us do that without requiring all contributors to sign a [CLA](https://en.wikipedia.org/wiki/Contributor_License_Agreement) or requiring them to hand over their copyright to us. This is a pretty common way to manage contributions for a large-ish open source project, so it should be totally fine for 99% of contributors.
#### MIT License for Contributions
Copyright 2022 Code Contributor (whoever you are)
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.