REmove commons clause

[baristaGeek]

Description

To continue committing to openness and transparency as much as we can, we're removing the commons clause from this repo.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Chore: cleanup/renaming, etc
• RFC

Notes

This makes us a Buyer Based Open Core company. We'll later add a /ee dir with paid-only features (no free usage, not even limited).

Acceptance

• I have read the Contributing guidelines
• I have read the Code of Conduct

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
watermelon	✅ Ready (Inspect)	Visit Preview	Nov 20, 2023 8:50pm

[watermelon-copilot-for-code-review]

WatermelonAI Summary

This PR removes the commons clause from the repository, aligning with the company's commitment to openness and transparency. It signifies a transition to a Buyer Based Open Core model, where paid-only features will be added in the future.

GitHub PRs

• #389 - REmove commons clause - By baristaGeek Just now

• #388 - Bugfix - Deactivate comenting on bot PRs - By baristaGeek 43 minutes ago

• #376 - Feature/simplified labeling - By EstebanDalelR 6 days ago

Click here to login to Jira
Click here to login to Confluence
Click here to login to Slack
No results found in Notion Pages :(

No results found in Linear Tickets :(

Click here to login to Asana
watermelon is an open repo and Watermelon will serve it for free.
🍉🫶

[EstebanDalelR]

Hoping we don't get abused