Have Doubts related to contribution as well as Jira

Hi @bawanthathilan I’m interested in contributing to the Improved Appointments Calendar View GSoC project. I’ve been exploring the codebase and went ahead and implemented an initial proof-of-concept to demonstrate my understanding of the project scope. What I built so far:

  1. Monthly / Weekly / Daily view switcher using Carbon’s ContentSwitcher

2. Full Weekly calendar view — 7-column grid with Prev/Next week navigation and service counts per day 3. Full Daily calendar view — single day focus with a service breakdown table and Prev/Next navigation

  • Replaced the disruptive navigate() calls with Carbon Modals on day click across all views — users stay in calendar context

  • All changes are TypeScript error-free

I’ve attached screenshots showing the working UI.

A few questions:

  1. Could I get Jira access to create a ticket for this work, or would you prefer I open a draft PR directly on GitHub?

  2. Should I open a separate ticket per feature (weekly view, daily view, modal) or one umbrella ticket for the calendar improvements?

  3. Are there any design specs or Figma mockups I should follow for the UI?

It will be helpful if you help me with this.

1 Like

Hi Brijesh, great work.

To answer your questions:

Go ahead and open a draft PR. that will make it easiest for us to review your code directly.

For the tickets, I think it would be better if we create separate tickets for each task/feature so it’s easier to track and identify them. We can still keep one ticket for the overall calendar improvements and link the individual tasks under it if needed.

We don’t have Figma mockups yet for this. Your implementation will actually help inform the design direction, so please keep going with the Carbon components as you have been.

Looking forward to seeing the PR.

Kindly fix your username. You can’t use an email as a username please!

Hi, I cant able to change my username. Can you help me with it ?

yeah sure, I’ll create the PR now.