Makes sense Daniel - By consensus, I meant majority votes. My intent was to try to recognize more people. Time is precious these days - totally agree. BTW - Thanks for sharing your thoughts in the previous thread - it was simple, hence I borrowed it:)
Sounds good Jarek! Revised proposal below. If it looks good, I will start a separate PROPOSE thread then. Quick question - do I need to wait for X days for the community to respond before moving onto the next step, so as to give sufficient time to the community to respond? Since https://github.com/apache/airflow/blob/main/contributing-docs/02_how_to_communicate.rst#devlist-details does not mention explicitly regarding the time to wait for community responses, I wanted to confirm the number of days (X days) I need to wait for DISCUSS and PROPOSE subject emails, before proceeding with next steps for VOTE subject emails. Voting is at least 3 votes to pass - that part is easy - from past observations on devlist communications:) *Mission statement : * *- to recognize meaningful contributions by new and budding contributors* *- inspire newcomers and novices relatively new to the community to pick up new PRs* *- make project feel more welcoming and inclusive* *Nomination process:* *- encourage self-nominations and community nominations, so it is convenient for anyone to recognize another fellow contributor.* *Qualifying Criteria:* *- These awards are FOR the Community and BY the community. The intent is to give a shout out to a Rookie with Apache Airflow project contribution.* *- Winner will be chosen based on the majority of votes by the community.* Warm Regards, Srabasti Banerjee On Wed, Dec 17, 2025 at 9:48 AM Jarek Potiuk <[email protected]> wrote: > Agree Daniel is - as usual - voice of reason.. Simpler is better. > > On Wed, Dec 17, 2025 at 3:48 PM Daniel Standish via dev < > [email protected]> wrote: > > > Some comments on the criteria section. > > > > In short, I think it's still too complicated / too much process and I > offer > > some suggestions for simplification. > > > > Re: > > > > > Same person cannot win every month for different categories. They > cannot > > > win a Top PR award in the same month. This is to ensure no repetitions > > for > > > winners each month. > > > > I still think this is too restrictive. People have enough to think about > > in life. Let's make it easy. If the same person wins two months in a > row, > > or wins both rookie and general, what's wrong with that? > > > > re > > > > > There can be a Rookie PR winner for each category, if the community > > > chooses to do so. > > > > > > Again my thought is to keep it simple. To me, while I appreciate the > > enthusiasm, I feel it's too much noise and mental cycles to start > thinking > > about a bunch of different categories for these awards *every month*. It > > also dilutes the value of each "award". > > > > I propose just one general PR of the month, and one rookie PR of the > month > > and that's it. Otherwise it becomes more like a "participation trophy". > > > > re: > > > > Winner(s) will be based on consensus or exceptional performance by the > > > community. > > > > > > Consensus has a specific meaning in a voting context and I think it might > > not be what you mean. > > > > > > > > On Tue, Dec 16, 2025 at 8:59 PM Srabasti Banerjee < > > [email protected]> wrote: > > > > > Hello All, > > > > > > It is awesome that we have the PR of the Month award to recognize the > PR > > > with the most impact each month, voted by the community. > > > > > > I would like to propose the addition of another award "Rookie PR" to > > > recognize new budding contributors. This will be an incentive for > > newcomers > > > and inspire them to pick up PRs. In the long run, this will result in > > > reduction of the list of open PRs as well. > > > > > > Name of the Award : Rookie PR > > > > > > Mission statement : > > > - to recognize meaningful contributions by new and budding contributors > > > - inspire newcomers and novices relatively new to the community to pick > > up > > > new PRs > > > - make project feel more welcoming and inclusive > > > > > > Nomination process: > > > - encourage self-nominations and community nominations, so it is > > convenient > > > for anyone to recognize another fellow contributor, in any category > (like > > > UI, Providers, Core, CI/CD, Helm Charts, AI). > > > > > > Qualifying Criteria: > > > - These awards are FOR the Community and BY the community. The intent > is > > to > > > give a shout out to (new and existing non top 100) team members who are > > > working on Apache Airflow project. > > > - Same person cannot win every month for different categories. They > > cannot > > > win a Top PR award in the same month. This is to ensure no repetitions > > for > > > winners each month. > > > - There can be a Rookie PR winner for each category, if the community > > > chooses to do so. > > > - Winner(s) will be based on consensus or exceptional performance by > the > > > community. > > > > > > Possibly we can have a list in one place - say Wiki, or Apache Airflow > > > website, so all winners are in one place at a glance. This way, it will > > be > > > easy for the community to check and then nominate accordingly to ensure > > no > > > repetitions for Rookie PR winners. > > > > > > As we discussed in past threads, we will start with Rookie PR and go > for > > > additional awards later, if there is appetite. Mentioning here for > > > reference sake. > > > > > > Appreciate your inputs to enhance this idea and eventually implement it > > for > > > the community. > > > > > > Warm Regards, > > > Srabasti Banerjee > > > > > >
