Skip to content

Update LICENSE file to clarify Core Contributor status management and… #66

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.

Sign up for GitHub

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

Merged
webdevcody merged 4 commits into from
Dec 14, 2025
Merged

Update LICENSE file to clarify Core Contributor status management and… #66

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a08641a
Update LICENSE file to clarify Core Contributor status management and…
webdevcody Dec 14, 2025
f2eb6c3
Update LICENSE file to amend Core Contributor status management
webdevcody Dec 14, 2025
1f71614
Refine Core Contributor status revocation criteria in LICENSE file
webdevcody Dec 14, 2025
d9440e8
Update LICENSE file to clarify amendment process and section numbering
webdevcody Dec 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 30 additions & 5 deletions LICENSE
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,10 @@ b) Licensee may run the Software on personal or organizational infrastructure fo

c) Core Contributors are each individually granted a perpetual, worldwide, royalty-free, non-exclusive license to use, copy, modify, distribute, and sublicense the Software for any purpose, including Monetization, without payment of any fees or royalties. Each Core Contributor may exercise these rights independently and does not require permission, consent, or approval from any other Core Contributor to Monetize the Software in any way they see fit.

d) Commercial licenses for the Software may be discussed and issued to external parties or companies seeking to use the Software for financial gain or Monetization purposes. Core Contributors already have full rights under section 2(c) and do not require commercial licenses. Any commercial license issued to external parties shall require a unanimous vote by all Core Contributors and shall be granted in writing and signed by all Core Contributors.

e) The list of individuals defined as "Core Contributors" in Section 1 shall be amended to reflect any revocation or reinstatement of status made under this section.

3. RESTRICTIONS

Licensee may NOT:
Expand All @@ -63,7 +67,24 @@ Licensee MAY:
- Use the Software to build other commercial products (products that do NOT contain the Software or Derivative Works)
- Modify the Software for internal use within their organization (commercial or non-profit)

4. CONTRIBUTIONS AND RIGHTS ASSIGNMENT
4. CORE CONTRIBUTOR STATUS MANAGEMENT

a) Core Contributor status may be revoked indefinitely by the remaining Core Contributors if:

- A Core Contributor cannot be reached for a period of one (1) month through reasonable means of communication (including but not limited to email, Discord, GitHub, or other project communication channels)
- AND the Core Contributor has not contributed to the project during that one-month period. For purposes of this section, "contributed" means at least one of the following activities:
- Discussing the Software through project communication channels
- Committing code changes to the project repository
- Submitting bug fixes or patches
- Participating in project-related discussions or decision-making

b) Revocation of Core Contributor status requires a unanimous vote by all other Core Contributors (excluding the Core Contributor whose status is being considered for revocation).

c) Upon revocation of Core Contributor status, the individual shall no longer be considered a Core Contributor and shall lose the rights granted under section 2(c) of this Agreement. However, any Contributions made prior to revocation shall remain subject to the terms of section 5 (CONTRIBUTIONS AND RIGHTS ASSIGNMENT).

d) A revoked Core Contributor may be reinstated to Core Contributor status with a unanimous vote by all current Core Contributors. Upon reinstatement, the individual shall regain all rights granted under section 2(c) of this Agreement.
Comment on lines 70 to 85
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Dec 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This new section introduces dynamic management of Core Contributor status, but the definition of "Core Contributors" in Section 1 (line 29) is a static list of names. This creates a potential conflict:

  • Section 4(c) states a revoked person "shall no longer be considered a Core Contributor," but their name would remain in the list in Section 1.
  • Section 4(d) allows for reinstatement, but the process for updating the list isn't specified.

This ambiguity could lead to disputes over who holds Core Contributor rights.

To resolve this, consider adding a clause to clarify that the list in Section 1 is the canonical list and must be updated to reflect status changes. For example, you could add a new subsection e):

e) The list of individuals defined as "Core Contributors" in Section 1 shall be amended to reflect any revocation or reinstatement of status made under this section.

This would ensure the license document remains the single source of truth for who the Core Contributors are.


5. CONTRIBUTIONS AND RIGHTS ASSIGNMENT

By submitting, pushing, or contributing any code, documentation, pull requests, issues, or other materials ("Contributions") to the Automaker project, you agree to the following terms without reservation:

Expand All @@ -75,11 +96,11 @@ c) **Waiver of Moral Rights:** You waive any "moral rights" or other rights with

d) **Right to Contribute:** You represent and warrant that you are the original author of the Contributions, or that you have sufficient rights to grant the rights conveyed by this section, and that your Contributions do not infringe upon the rights of any third party.

5. TERMINATION
6. TERMINATION

This license will terminate automatically if Licensee breaches any term of this Agreement. Upon termination, Licensee must immediately cease all use of the Software and destroy all copies in their possession.

6. HIGH RISK DISCLAIMER AND LIMITATION OF LIABILITY
7. HIGH RISK DISCLAIMER AND LIMITATION OF LIABILITY

a) **AI RISKS:** THE SOFTWARE UTILIZES ARTIFICIAL INTELLIGENCE TO GENERATE CODE, EXECUTE COMMANDS, AND INTERACT WITH YOUR FILE SYSTEM. YOU ACKNOWLEDGE THAT AI SYSTEMS CAN BE UNPREDICTABLE, MAY GENERATE INCORRECT, INSECURE, OR DESTRUCTIVE CODE, AND MAY TAKE ACTIONS THAT COULD DAMAGE YOUR SYSTEM, FILES, OR HARDWARE.

Expand All @@ -95,7 +116,11 @@ d) **LIMITATION OF LIABILITY:** IN NO EVENT SHALL THE CORE CONTRIBUTORS, LICENSO
- FINANCIAL LOSSES
- BUSINESS INTERRUPTION

7. CONTACT
8. LICENSE AMENDMENTS

Any amendment, modification, or update to this License Agreement must be agreed upon unanimously by all Core Contributors. No changes to this Agreement shall be effective unless all Core Contributors have provided their written consent or approval through a unanimous vote.

9. CONTACT

For inquiries regarding this license or permissions for Monetization, please contact the Core Contributors through the official project channels:

Expand All @@ -105,7 +130,7 @@ For inquiries regarding this license or permissions for Monetization, please con

Any permission for Monetization requires the unanimous written consent of all Core Contributors.

8. GOVERNING LAW
10. GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of Tennessee, USA, without regard to conflict of law principles.

Expand Down