Nomination Process for Community Recognition
This is a draft
Inspired by prestigious awards like the Oscars or the Nobel Prize, we suggest that approach to recognition is based on accomplishments, not popularity. These awards don't begin by asking, "Who should win?" — they start by identifying what has been achieved. Only then do they uncover who was behind the work.
The same principle should guide our community recognition:
🏆 Focus first on the contribution, then recognize the contributor.
By starting with accomplishments — impactful projects, community leadership, technical breakthroughs, or efforts that broadened adoption — we ensure that recognition is impact-based, fair, and deeply meaningful. It honors the work itself and shines a light on the individuals or teams who made it possible.
Process Overview
Every year, two months ahead of the conference, we distribute a survey to the Open edX community.
The survey invites community members to outline the most important accomplishments in the following tracks:
Engineering Excellence
Outstanding technical contributions, code improvements, or platform enhancements.Open edX Advocacy and Adoption
Efforts that helped spread awareness, drive adoption, or improve understanding of the Open edX platform.Innovation and Impact
Creative ideas, breakthrough solutions, or new approaches that advanced the Open edX ecosystem.Rising Stars
Recognising and supporting new contributors who are already making positive impact
Once responses are collected, the Review Panel:
Identifies the accomplishments that received the most recognition or impact.
Investigates who was behind each accomplishment.
The individuals or teams behind these recognized accomplishments are automatically nominated for community awards.
Communication Timeline for the Program 2025
Goal: Raise awareness, inspire participation, and collect meaningful nominations — while reinforcing a culture of recognition in the Open edX community.
Date 2025 | Channel | Activity | Message Brief | Status |
|---|---|---|---|---|
May 23 | CRM Email | Sent out initial survey email |
| sent |
May 27 | Discuss Forum | Posted first message on the forum (program intro + survey) |
| sent |
June 18th | Internal Slack@Natalia Vynogradenko @Mahnoor Sarwat | Internal heads-up | Let’s celebrate meaningful contributions + FAQ | to do |
June 18th | CRM Email @Eden Huthmacher | New Deadline and Conference Event Announcement | Nominations extended to July 15 | to do
|
June 18th | Conference App @Eden Huthmacher | Launch message in announcement tab | Short, link + context (additional points?) | to do |
June 25–28 | CRM Email @Eden Huthmacher | Reminder about join us at the conference for discussion of the program | Explain the program + link to nomination form | to do |
July 1–4 | Slack (community channels) @Mahnoor Sarwat @Natalia Vynogradenko | Real-time messages during conference | Informal post + pinned message to keep visibility | to do |
July 1–4 | Discuss Forum @Natalia Vynogradenko | Pinned program post | Full details + link to nominate; engage replies | to do |
July 2 or 3 | LinkedIn (Program Supporters) @Eden Huthmacher @Natalia Vynogradenko @Mahnoor Sarwat @Vineet Manuja | Public story-driven launch | Highlight community spirit and the why behind the program | to do |
July 5–10 | CRM Email @Eden Huthmacher | Midway reminder to nominate | Share an example, keep energy up | to do |
July 11–15 | CRM + Slack + Discuss @Eden Huthmacher @Mahnoor Sarwat @Natalia Vynogradenko | Final call for nominations | Friendly urgency: “Last chance to recognize someone meaningful” | to do |