Is your proposal related to a problem?

Yes.

The README currently contains two separate "License" sections:

1. A detailed Open Core explanation that includes an AGPLv3 vs Enterprise Edition comparison table.

2. A second standalone AGPLv3 license section near the bottom of the file.

This duplication creates redundancy and may cause confusion for readers trying to understand the official licensing structure of the project. It is unclear whether both sections serve distinct purposes or if one unintentionally duplicates the other.

I have reviewed existing issues and did not find a similar report related to duplicate license sections.

Describe the solution you'd like

I would suggest one of the following improvements:

Merge both sections into a single comprehensive "License" section that clearly explains:

1. Open Core model
2. AGPLv3 licensing
3. Enterprise Edition differences

OR

Remove the duplicate AGPLv3 section at the bottom of the README and instead link back to the primary, detailed license explanation section.

This would make the licensing information more streamlined and easier to understand.

Describe alternatives you've considered

An alternative approach could be:

1. Retaining both sections but clearly distinguishing their purposes with different headings (e.g., "Open Core Licensing Overview" and "Repository License Notice").

2. Adding anchor links at the top of the README to clarify structure.

However, consolidation into a single section appears cleaner and less repetitive.

Additional context

This improvement is purely documentation-related and does not affect functionality.

It aims to:

1. Improve readability
2. Reduce redundancy
3. Prevent confusion regarding AGPL vs Enterprise licensing

If helpful, I am willing to submit a pull request implementing the chosen structure after approval.

Requirement/Document

Reference:

Current README.md file in the main branch of the repository.

No additional documentation is required for this proposal.

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.
  • Follow Best Practices lined out in our Contributor Docs