STANDARD: License

[glhays]

Institution of a license for Standard Compliant Repositories.

[glhays]

##Thoughts:
Will the addition of a Standard license require a new section for example [4. License Requirements]
If so how shall the tone of this new section present itself.
Is the license self enforcing.

=============DRAFT==============

Standard Compliant License (SCL)

© [2024] [The Standard Organization]. All rights reserved.

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, sub-license, 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:

1. Standard Compliance: Any use of the terms "Standard Compliant" or any depiction of an "Shields.io badge" indicating Standard Compliance must include this license as part of the software distribution.

2. Open Source Requirement: The Software and any derivative works must remain open source and free of charge. Redistribution of the Software must include this license.

3. Non-Harm Clause: The Software shall not be used for any purpose that causes harm, including but not limited to physical, mental, or financial harm.

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

5. All-In/All-Out Principle: Any and all software must abide by "must be fully embraced or entirely rejected" principle as stated in the Standard Documentation.

6. Self-Enforcing: This license, by use of the term "Standard Compliant" software, is self-enforcing.

7. Non-Modification: This license may not be modified in any way.

8. Warranty Disclaimer: 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 NON-INFRINGEMENT. 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.

By using the Software, you agree to comply with these terms.

^^^^^^^^^ @hassanhabib @cjdutoit @LBoullosa ^^^^^^^^

[LBoullosa]

do you think we should add whatever modification should be done according The Standard? (maybe this is too much requirement)