Cal.com Feature Request: Discussion & Proposals

Let's dive into the exciting world of suggesting improvements and new features for Cal.com! This is where you, the awesome Cal.com community, can propose ideas, discuss potential solutions, and help shape the future of this amazing scheduling tool. Think of this as your personal suggestion box for all things Cal.com. We're stoked to hear your thoughts and collaborate on making Cal.com even better.

Is your proposal related to a problem?

Okay, guys, let's get down to brass tacks. Every great solution starts with a well-defined problem. So, what's bugging you? What's that itch that needs scratching? Maybe you're finding a particular workflow clunky, or perhaps there's a missing feature that would make your life a whole lot easier. This section is all about clearly and concisely describing the problem you're facing. The more detail you provide, the better we can understand the issue and come up with an effective solution. Don't be shy; lay it all out there! Remember, the goal here is to paint a vivid picture of the problem so that everyone's on the same page. When describing the problem, think about the impact it has on your workflow, how often you encounter it, and any specific scenarios where it becomes particularly frustrating. Providing concrete examples and use cases will really help to illustrate the issue and make it easier for others to relate to it. The more specific you are, the easier it will be for the Cal.com team and the community to understand the root cause of the problem and brainstorm potential solutions. So, take your time, be thorough, and let us know what's not working for you. Your feedback is invaluable in helping us make Cal.com the best it can be. And who knows, your problem might be shared by many other users, so by bringing it to our attention, you could be helping the entire Cal.com community!

Describe the solution you'd like

Alright, now that we've identified the problem, let's talk solutions! This is where you get to put on your thinking cap and describe your ideal fix. What would the perfect solution look like? How would it work? Be as specific as possible. Imagine you're explaining it to a developer who's going to build it. The more details you provide, the better the chances of your vision becoming a reality. Don't just say "make it better"; tell us how to make it better. Consider the user interface, the workflow, the functionality, and any other relevant aspects of the solution. Think about how the solution would integrate with the existing Cal.com features and how it would impact the overall user experience. Would it require any changes to the database or the backend infrastructure? Would it introduce any new dependencies or security considerations? The more you think through these details, the more complete and compelling your proposal will be. And remember, it's okay to be creative and think outside the box! This is your chance to design the perfect solution to your problem. So, let your imagination run wild and tell us what you've got. We're all ears!

Describe alternatives you've considered

Before we jump headfirst into your proposed solution, let's take a step back and explore some alternatives. Have you considered other ways to solve the problem? Maybe there's an existing feature in Cal.com that could be tweaked to achieve the desired outcome, or perhaps there's a third-party integration that could do the trick. Exploring alternative solutions is important because it helps us to evaluate the pros and cons of different approaches and choose the one that's the most effective, efficient, and sustainable. It also demonstrates that you've put some thought into the problem and haven't just jumped to the first solution that came to mind. When describing the alternatives you've considered, be sure to explain why you ultimately rejected them in favor of your proposed solution. What were the drawbacks or limitations of each alternative? How does your proposed solution overcome those limitations? By providing a thorough analysis of the alternatives, you can strengthen your argument for your proposed solution and convince others that it's the best way forward. So, take some time to research and explore different options, and then share your findings with us. We appreciate your thoroughness and your commitment to finding the best possible solution.

Additional context

This is where you can add any extra information that might be helpful in understanding your proposal. Did you find a similar feature in another app that you particularly liked? Are there any related issues on GitHub that you want to link to? Any extra context will help give more information to the developers. This section is your chance to provide any additional information that might be relevant to your proposal but doesn't fit neatly into the other sections. Maybe you have some data or statistics that support your argument, or perhaps you have some user feedback that you want to share. Whatever it is, feel free to add it here. The more information you provide, the better we can understand the context of your proposal and make an informed decision about whether or not to implement it. You can also use this section to address any potential concerns or questions that others might have about your proposal. By anticipating these concerns and providing clear and concise answers, you can help to build consensus around your proposal and increase its chances of being accepted. So, don't be afraid to add as much detail as you think is necessary. We appreciate your thoroughness and your willingness to go the extra mile to make your proposal as clear and compelling as possible. After all, the more information we have, the better equipped we are to evaluate your proposal and make a decision that's in the best interest of the Cal.com community.

Requirement/Document

Do you have any supporting documents that would help illustrate your proposal? Mockups, wireframes, user stories – anything that can help us visualize your idea would be amazing! Providing supporting documents can significantly strengthen your proposal and make it easier for others to understand your vision. Mockups and wireframes can help to illustrate the user interface and workflow of your proposed solution, while user stories can help to describe the user experience from different perspectives. If you have any data or statistics that support your argument, be sure to include them as well. The more evidence you can provide to back up your proposal, the more convincing it will be. And remember, even if you don't have any formal documents, you can still provide screenshots, diagrams, or even just a detailed written description. The key is to make your proposal as clear and understandable as possible. After all, the easier it is for others to understand your vision, the more likely they are to support it. So, don't hesitate to share any supporting materials that you think would be helpful. We appreciate your effort and your commitment to making your proposal as comprehensive as possible.

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 We need to make sure the product is aligned with the team vision, so we appreciate the wait.