open-sauced / docs

OpenSauced documentation built with docusaurus

Home Page:http://opensauced.pizza/docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bug: License information is incomplete

dominicduffin1 opened this issue Β· comments

Describe the bug

Under the License heading it states that contributors agree to their contributions being licensed under the MIT license, but not all Open Sauced repositories use that license. For example, open-sauced/app uses the Apache-2.0 license.

The License subsection in the docs should contain information that reflects the current legal status of the repositories, or more general language such as "you agree that your contributions will be licensed under the repository's license".

Steps to reproduce

  1. Go to https://docs.opensauced.pizza/contributing/introduction-to-contributing/#license

Browsers

Chrome, Firefox, Safari, Edge, Opera

Additional context (Is this in dev or production?)

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Hey @dominicduffin1. How are you doing with this?

Hi @CBID2 , sorry I didn't see I'd been assigned to the issue πŸ˜₯. Does the team have a preference between adding the different licenses or keeping the language more general?

Hi @CBID2 , sorry I didn't see I'd been assigned to the issue πŸ˜₯. Does the team have a preference between adding the different licenses or keeping the language more general?

Hey @dominicduffin1. I'm not too sure. @bdougie, what do you think?

I'd personally prefer more general language: different repos may carry different licenses which may carry their own different contributor attribution statements. And in the future, even if we did capture each of the different licenses and attributions we have today, we'd maybe adopt a different ones in new repos that would drift from fine grained documentation. So, more a more general approach in the docs makes sense to me.

Hi @CBID2 @jpmcb I've opened a PR with some potential general language, let me know what you think! Happy to revise to meet requirements.

πŸŽ‰ This issue has been resolved in version 1.43.0 πŸŽ‰

The release is available on:

Your semantic-release bot πŸ“¦πŸš€