# Core Contributor Nomination - Tanuja

**URL:** <https://discuss.openedx.org/t/core-contributor-nomination-tanuja/19058>\
**Category:** Core Contributors\
**Created:** [May 15, 2026, 10:27am UTC](https://discuss.openedx.org/t/core-contributor-nomination-tanuja/19058 "2026-05-15T10:27:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tanuja\_Sunkara](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/tanuja_sunkara/32/9615_2.png) [@Tanuja\_Sunkara](https://discuss.openedx.org/u/Tanuja_Sunkara)\
**Post date:** [May 15, 2026, 10:27am UTC](https://discuss.openedx.org/t/core-contributor-nomination-tanuja/19058/1 "2026-05-15T10:27:12Z")

</div>

## Hi Everyone,

I would like to nominate myself, **Tanuja Sunkara (@tsunkara-sonata)**, for Core Contributor status in the Open edX community.

* * *

## Contributions

I bring strong frontend expertise across modern technologies, including **React, TypeScript, TanStack Query, Zustand, react-hook-form (with Zod), Paragon**, and **Stripe integrations**.

My recent work has been focused on the **enterprise checkout (SSP flow)**, where I have contributed to improving functionality, reliability, and overall user experience.

In addition, I have:

- Improved test coverage to strengthen code quality

- Delivered bug fixes aligned with Open edX standards

- Collaborated on pull requests, ensuring consistency with established frontend patterns and best practices

* * *

## Collaboration

I actively collaborate with **frontend, backend, and product teams** through:

- Code reviews

- Issue investigation and debugging

- Technical discussions and design alignment

I follow established architecture and coding standards to ensure that the solutions I build are **maintainable, reusable, and aligned with community expectations**.

* * *

## Commitment

I am committed to continuing my contributions to the Open edX ecosystem through:

- Feature development and enhancements

- Bug fixes and ongoing improvements

- Thoughtful and consistent code reviews

- Repository maintenance and support

- Expanding contributions across additional edX frontend repositories

* * *

## Closing

I look forward to continued collaboration and contributing more deeply to the community.

**Feedback is welcome over the next two weeks.**  
**Comment period ends: June 1, 2026**

* * *

**Thank you**  
Tanuja Sunkara

---

<div class="post-metadata">

**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\
**Post date:** [May 15, 2026, 3:49pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-tanuja/19058/2 "2026-05-15T15:49:27Z")

</div>

Hi! Could you kindly read through [OEP-54: Core Contributors — Open edX Proposals 1.0 documentation](https://docs.openedx.org/projects/openedx-proposals/en/latest/processes/oep-0054-core-contributors.html#new-core-contributor-nomination-process) and update your nomination according to the guidelines? Particularly, you haven’t provided any links to merged PRs or specified what repo(s) you’re interested in becoming a CC to. Looking throughout this forum for other examples of successful nomination posts would be helpful.