Why am I running for the OSI Board?

If elected to the board, I have three goals I'd like to accomplish:

  • To grow the OSI's membership,
  • To defend the Open Source Definition, and
  • To define the future of open source.

Grow the OSI's membership

Nearly 5300 developers completed GitLab's 2018 developer survey; 43% of the 100k developers who completed StackOverflow's 2018 developer survey contribute to open source. The OSI has approximately 500 individual members. If the OSI is to be representative of the wider open source community, it must broaden its membership.

To demonstrate my commitment, during my campaign, I pledge to recruit 25 new Individual Members, which would grow the OSI's membership by 5%.

  • Current new member count: 2/25 (last updated 2019-02-10)
  • Inspired by my platform? Sign up for an Individual Membership, reach out to me, and I'll send you a shoutout on the fediverse or Twitter ^_^

As a board member, I will advocate for offering gratis Individual Membership to all members of Affiliate Projects, and focus on outreach to recruit new Affiliate Projects.

Defend the OSI Definition

Recently, we've seen the proliferation of a number of new protectionist licenses, as corporations become more concerned about their open source projects being monetized by other corporations that don't contribute back. I think corporate sustainability and community sustainability are different things, and I'm concerned that the idea of "sustainability" is being co-opted by companies that define it as seeing greater financial returns from their open source projects.

Non-free licenses masquerading as "open source" jeopardize the free software commons. As a Debian Developer, I've made a commitment to the community to uphold the Debian Free Software Guidelines. The OSI's prominence gives me the opportunity to take on that responsibility with greater reach in upholding the Open Source Definition.

Define the future of Open Source

Software licenses are a means, not an end, to open source software. Focusing on licensing is necessary but not sufficient to ensure a vibrant, thriving open source community. Focus on licensing to the exclusion of other serious community concerns is to our collective detriment.

All of the software communities I participate in consider themselves to be "open source communities". And yet, I see very few folks from the core JavaScript, or Python, or Clojure communities involved with or advocating for the OSI. The vast majority of my colleagues would not be able to tell you what the OSI does beyond maintaining the OSD, and for most of them, software licensing is a minimal concern, a "solved problem." If open source is for everyone, and if the OSI is to continue to represent the open source community and play a key role in the future of open source, then it is critical for it to engage the wider community for input and collaboration.

To this end, as a board member, I will advocate for running a community survey on the broader topic of open source: what open source means, what open source can achieve, what challenges the growth and sustainability of open source. I think it's a shame that the only available self-reported data from the open source community are from corporate surveys like GitLab's or StackOverflow's. Community data provides a foundation for the OSI to defend the present and define the future of open source software.

Who am I?

I'm the Queen of Debian Clojure, Empress of Symbol Versioning, Conqueress of ABIs, Python Packaging Authority, ELF Herder and the winner of the Software Freedom Conservancy's 2018 Award for most odd, but needful volunteer assistance. I care deeply about not just the philosophy but the practice of free and open source software, and seek to further both ideals and implementation through my community work.

As a Debian Developer, I upload and maintain the 50-some Clojure package ecosystem between the Clojure and Java Teams in Debian and Ubuntu, and as a Python Packaging Authority committer, I hack on portable binary Python wheels for Linux. I was elected a Python Software Foundation Fellow in 2018 for my contributions to the Python ecosystem. I'm also a current member of the Kubernetes Instrumentation SIG, where I work on benchmarking and metrics usability. I've submitted patches and documentation to projects spanning many languages, from Pelican and Molecule to Leiningen and clojure.java.jdbc. My first contributions to open source were through OpenHatch, beginning in 2013, where I later served as a core maintainer and login team member until the project was sunset.

blog mastodon salsa Twitter GitHub

Created by Patrick Masson on 2019.02.04 at 12:39:00 PST

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 7.4.2 - Documentation