Eligibility requirements in tech are dumb.
-
Eligibility requirements in tech are dumb.
One of my best decisions with DEFNA and DjangoCon US was inviting people with full access from day one.
We didn't need a policy or hand-wavy requirements for who could or couldn't have access to our documents or even a git commit. There were no hoops to jump through other than you wanted to be involved.
Every year, we asked that people opt back in if they wanted to or we would remove them after x-date.
-
Jeff "weBOOOOlogy" Triplettreplied to Jeff "weBOOOOlogy" Triplett last edited by
Everything was meant to be low friction for joining and leaving. No pressure.
Git commit access doesn't scale for every project, but a low-friction way to join a foundation or membership does.
In almost a decade, we had only one git delete branch accident, and that was a learning opportunity that was easily fixed.
So it frustrates me to no end to see overqualified people fall through the cracks because of some arbitrary membership requirements that really don't mean much.
-
Jeff "weBOOOOlogy" Triplettreplied to Jeff "weBOOOOlogy" Triplett last edited by
Just in the last **two months**, here is the pedigree of people who I have heard mention or bring up that they are not qualified to run for a position:
- Former DSF President (technically two)
- CPython Core dev
- Multi-year summer of code mentor
- Past or present Django Fellow
- Former BDFL
- Former DSF Director
- Popular Django package maintainerSo yes. "Eligibility requirements in tech are dumb," and Django's needs re-thought.
Python doesn't get a pass either.
