# Core Contributor Nomination – Ramya Gopal Rao **URL:** \ **Category:** Core Contributors\ **Created:** [May 15, 2026, 10:11am UTC](https://discuss.openedx.org/t/core-contributor-nomination-ramya-gopal-rao/19057 "2026-05-15T10:11:54Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ramya\_Gopal\_Rao](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/ramya_gopal_rao/32/9614_2.png) [@Ramya\_Gopal\_Rao](https://discuss.openedx.org/u/Ramya_Gopal_Rao)\ **Post date:** [May 15, 2026, 10:11am UTC](https://discuss.openedx.org/t/core-contributor-nomination-ramya-gopal-rao/19057/1 "2026-05-15T10:11:54Z")
Hi Open edX community, I am putting myself forward as an **organic candidate** for **Core Contributor (Coding)** status, per the process defined in [OEP-54](https://docs.openedx.org/projects/openedx-proposals/en/latest/processes/oep-0054-core-contributors.html). * * * **About Me** I’m **Ramya Gopal Rao** , a Technical Lead at 2U on the Lakshy team (GitHub: [@rgopalrao-sonata-png](https://github.com/rgopalrao-sonata-png)). My background is in backend engineering and data systems. I focus on building solutions that are reliable, maintainable, and designed for long-term scalability. Beyond individual contributions, I lead engineering efforts within my team — driving design decisions, mentoring developers, and reviewing code across repositories. * * * **Demonstrating the 3 C’s** **Commitment** Over the past several months I have contributed consistently and with strong ownership across multiple enterprise repositories. My work spans backend services, async workflows, data pipelines, APIs, and frontend features — all contributed back to the open community. **Caliber** Selected merged PRs demonstrating code quality and technical depth: _edx-enterprise-data_ - [feat: snowflake-only course progress enrichment and tests #660](https://github.com/openedx/edx-enterprise-data/pull/660) — Closed a key visibility gap for admins tracking learner progress with passing grade data, using Snowflake-backed enrichment with full test coverage. - [fix: add snowflake-connector-python to base requirements #662](https://github.com/openedx/edx-enterprise-data/pull/662) — Dependency fix ensuring reliable Snowflake integration across environments. _edx-enterprise_ - [feat: Admin invite flow with Braze integration improvements #2542](https://github.com/openedx/edx-enterprise/pull/2542) — Implemented self-service admin onboarding with Braze email integration, reducing operational dependency on support teams. - [fix: restrict admin manage endpoints and bump version #2601](https://github.com/openedx/edx-enterprise/pull/2601) — Security-focused fix tightening API endpoint access controls. - [fix: emails displayed incorrectly in pending customer admin #2614](https://github.com/openedx/edx-enterprise/pull/2614) — Fixed a bug causing name/email mismatch in the admin UI. Additional contributions include enabling multiple subscription support in `enterprise-access`, the Edit Highlights feature in `enterprise-catalog`, and cross-repository integration work to improve consistency across services. **Conduct** I actively participate in code reviews across repositories, contribute to design discussions, mentor team members, and support contributors navigating the codebase. I aim to raise concerns constructively and help improve system quality collaboratively. * * * **Cross-Repository Experience** Within a short period I have contributed meaningfully across: - `edx-enterprise` - `edx-enterprise-data` - `enterprise-catalog` - `enterprise-access` This breadth has given me a strong understanding of system boundaries, integration patterns, and the dependencies between enterprise services. * * * **Commitment Going Forward** As a Core Contributor I commit to: - Writing clear, well-tested, maintainable PRs - Providing thoughtful and timely code reviews - Actively participating in technical discussions - Supporting contributors and sharing knowledge within the community - Upholding the Open edX [Code of Conduct](https://openedx.org/code-of-conduct/) * * * **Comment period closes: 1 June 2026** I welcome all feedback, questions, and votes. Thank you for your time and for considering this nomination. -– Ramya Gopal Rao, Technical Lead, Lakshy Team — 2U ---
**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-ramya-gopal-rao/19057/2 "2026-05-15T15:49:03Z")
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.