* feat: Cal.diy — community-driven MIT-licensed fork of Cal.com This squashed commit contains all Cal.diy changes applied on top of calcom/cal.com main: - Rebrand Cal.com to Cal.diy across the entire codebase - Remove Enterprise Edition (EE) features, license checks, and AGPL restrictions - Switch license from AGPL-3.0 to MIT - Remove docs/ directory (migrated to Nextra at cal.diy) - Remove dead code: org tests, EE tips, platform nav, premium username, SAML/SSO, etc. - Clean up .env.example for self-hosted Cal.diy - Update Docker image references to calcom/cal.diy - Update README, CONTRIBUTING.md, and issue templates for Cal.diy community fork - Add PR welcome bot for Cal.diy contributors - Fix API v2 breaking changes oasdiff ignore entries - Replace Blacksmith CI runners with default GitHub Actions 3893 files changed, 20789 insertions(+), 411020 deletions(-) Co-Authored-By: benny@cal.com <sldisek783@gmail.com> * refactor: remove org-specific /organizations/:orgId endpoints from API v2 atoms controllers (#1701) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * fix: revert Cal.diy Inc to Cal.com, Inc. in license files, copyright notices, and package metadata (#1702) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * rip out org related comments in api v2 --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
59 lines
1.4 KiB
Markdown
59 lines
1.4 KiB
Markdown
---
|
|
name: Feature request
|
|
about: Suggest a feature or idea
|
|
title: ""
|
|
labels: ["✨ feature", "🚨 needs approval"]
|
|
assignees: ""
|
|
---
|
|
|
|
### Is your proposal related to a problem?
|
|
|
|
<!--
|
|
Provide a clear and concise description of what the problem is.
|
|
For example, "I'm always frustrated when..."
|
|
-->
|
|
|
|
(Write your answer here.)
|
|
|
|
### Describe the solution you'd like
|
|
|
|
<!--
|
|
Provide a clear and concise description of what you want to happen.
|
|
-->
|
|
|
|
(Describe your proposed solution here.)
|
|
|
|
### Describe alternatives you've considered
|
|
|
|
<!--
|
|
Let us know about other solutions you've tried or researched.
|
|
-->
|
|
|
|
(Write your answer here.)
|
|
|
|
### Additional context
|
|
|
|
<!--
|
|
Is there anything else you can add about the proposal?
|
|
You might want to link to related issues here, if you haven't already.
|
|
-->
|
|
|
|
(Write your answer here.)
|
|
|
|
### Requirement/Document
|
|
|
|
<!--
|
|
Is there any type of document that could support that feature?
|
|
-->
|
|
|
|
(Share it here.)
|
|
|
|
---
|
|
|
|
##### 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](https://github.com/calcom/cal.diy/blob/main/CONTRIBUTING.md)
|