If we think of the PSF Board as being representative of the Python Community, and making decisions on behalf of the community, then there’s three things I think about a lot in terms of that representation:
- Regional representation
- Project representation
- Board member responsibilities and compensation
(1) we’ve already started talking about here, and I am strongly in favor of making the board seats regional and having voters self-select the region they would like to vote for. If this means changing the board seats, let’s do it, and I believe in our excellent infra team’s ability to make an election like this happen.
(2) I’ve chatted about with some board members already, but the core argument goes like this: some members Python community feel less affinity for their regional group, but a ton of affinity for their Python project group. Making up some examples, a Django developer in Des Moines or a Numpy developer in Nome will feel more affinity and representation with those projects than with their region. I would argue that the decisions in the world of Python that affect those projects are more important to Pythonista than the regional decisions. These project-based Pythonistas are less well represented by regional coverage, so what do we do about that?
(3): By making membership on the PSF Board a purely volunteer effort, we are saying something about the people we want to be on the board. Namely, we are saying that we only want people who have the socioeconomic status that lets them dedicate large chunks of time to a volunteer effort. This is equivalent to most American City Councils, and is why you get affluent retirees making up so much of the representatives there. It’s not really a surprise to me that so many of the board candidates are employees from large Silicon Valley companies, because being an employee at one of those companies often gives you more flexibility to do work like being on an Open Source board of directors.
What do we do about (3)? We combine the PSF Ambassadors idea with a reasonable compensation model. We turn being a board member into a paid part-time job, and place expectations on those members that part of being a Board Member is spending time out in the community being an ambassador. This would be a self-funding effort, I believe, because part of that time would be spent helping Betsy and the PSF staff fundraise for the PSF.
With this, we’ve hopefully opened up PSF Board Membership to a wider group of Pythonistas, because we’ve reduced the number of people needing to choose between “serving their community” and “making rent”.
I recognize this is a fairly radical departure from where we are today, but I feel it’s pretty important to point out the implicit bias towards certain socioeconomic groups in our current board practices, and suggest a way forward out of it.
Thanks for starting this, Lorena, and I’m excited to see where the discussion goes.