Skip to content

[proposal] Change the number of new Distinguished Contributors to 5 each year (down from 10) #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Carreau
Copy link
Member

@Carreau Carreau commented May 7, 2025

We had more spot than candidates for a few years,
this is in my opinion problematic.

Among other,

  • It decreases the recognition of the award
  • It forces us to change voting procedure

I'm open to decrease to less than 5, but I think
this is a first step.

Note that I suggested this a couple of time, but was told this was too close to next elections, as this time the election are just finished, I hope this is early enough.

I'm unsure if this is EC and/or SSC:

Executive Council Votes

@afshin

  • yes
  • no
  • abstain

@jasongrout

  • yes
  • no
  • abstain

@choldgraf

  • yes
  • no
  • abstain

@Ruv7

  • yes
  • no
  • abstain

@Zsailer

  • yes
  • no
  • abstain

@rpwagner

  • yes
  • no
  • abstain

Software Steering Council votes

DEI Standing Committee: Martha Cryan @marthacryan

  • yes
  • no
  • abstain

Jupyter Accessibility: Gabriel Fouasnon @gabalafou

  • yes
  • no
  • abstain

Jupyter Book: Angus Hollands @agoose77

  • yes
  • no
  • abstain

Jupyter Foundations and Standards: Paul Ivanov @ivanov

  • yes
  • no
  • abstain

Jupyter Frontends: Mike Krassowski @krassowski

  • yes
  • no
  • abstain

Jupyter Kernels: Johan Mabille @JohanMabille

  • yes
  • no
  • abstain

Jupyter Security: (currently vacant?)

Jupyter Server: Vidar Fauske @vidartf

  • yes
  • no
  • abstain

Jupyter Widgets: Sylvain Corlay @SylvainCorlay

  • yes
  • no
  • abstain

JupyterHub and Binder: Min Ragan-Kelley @minrk

  • yes
  • no
  • abstain

Voilà: Martin Renou @martinRenou

  • yes
  • no
  • abstain

We had more spot than candidates for a few years,
this is in my opinion problematic.

Among other,

 - It decreases the recognition of the award
 - It forces us to change voting procedure

I'm open to decrease to less than 5, but I think
this is  a first step.

Note that I suggested this a couple of time, but was told this
was too close to next elections, as this time the election are just finished,
I hope this is early enough.
@Carreau
Copy link
Member Author

Carreau commented May 7, 2025

FYI at least the past 3 years did not reach 10 Distinguished Contributors.

@choldgraf
Copy link
Contributor

Personally I think it's reasonable to shrink the number of new seats each year. If I remember, the first year we chose 10 because there was a large backlog of people that were likely deserving, and we didn't want to spend all of our time going through that backlog. I'd be fine capping this to 2-3 personally, but 5 is reasonable too.

@choldgraf choldgraf changed the title Half the number of yearly Distinguished Contributor [proposal] Change the number of new Distinguished Contributors to 5 each year (down from 10) May 7, 2025
@agoose77
Copy link

agoose77 commented May 7, 2025

Something that would concern me with shrinking this down is that it might become difficult to compare contributors to different projects for which the scope of a distinguished contribution may differ (e.g. between Jupyter Book and Jupyter Lab). I would like to avoid under representing one of our communities as a consequence of this change. Does this make sense?

@jasongrout
Copy link
Member

I would like to avoid under representing one of our communities as a consequence of this change.

I feel like right now we are on the other end of the spectrum. I would suggest limiting things like proposed for next year, and if this is a huge concern after the next election, we can iterate and adjust.

@Carreau
Copy link
Member Author

Carreau commented May 7, 2025

This is some of the reasons I choose 5, I tend to have the feeling that 3 would be good, but I don't want to be over restrictive. Let's note also that if we have many good contributors one year and few the year after, this can help to spread the recognition through time, so I don't see any reason to not have an informal "those people did not make the cut this year and have a 'boost' for next"

@jasongrout
Copy link
Member

Pinging the @jupyter/executive-council and @jupyter/software-steering-council for a vote

@jasongrout jasongrout moved this from Ready to In progress in EC Priorities and Tasks May 20, 2025
@jasongrout jasongrout self-assigned this May 20, 2025
@jasongrout
Copy link
Member

Pinging @gabalafou, @agoose77, @JohanMabille, @vidartf, @SylvainCorlay, @minrk, @martinRenou, @rpwagner, who haven't voted or abstained.

@minrk
Copy link
Member

minrk commented Jun 5, 2025

Thanks for the ping, missed the call the first time around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants