<M <Y

: 10+ Years Later: Back in 2009, my spouse and I edited and published an anthology of original speculative fiction and art called Thoughtcrime Experiments (here's why, and how you can do it yourself).

I wrote some followup posts: a few months later, a little after that, one year later, four years later, five years later. It cheers me whenever I meet one of our authors or artists in person. And I get to brag about the Ken Liu story we published and how (as he keeps saying) TE publishing that story was a huge turning point in his writing career.

There's a newish New York Times piece today about Liu's work as a translator, bridging the worlds of English- and Chinese-language scifi. His experience, fame, and connections as an author of speculative fiction help him advocate for Chinese-language science fiction in Anglophone markets.

We planted seeds more than a decade back, and they're still sprouting.

In the last few years I made, encouraged, and promoted performance art about making technology. This year I'm handing those responsibilities over to others, passing the baton to title of conf and other events, so I can concentrate on my clients, my family, and writing about open source maintainership.

So I've just set a calendar reminder for myself, for 2030, to ask myself: how is the legacy of "The Art of Python" doing?

I don't have a ten-year plan. But I have at least one ten-year question.

Filed under:

: Everyone Has Bugs To Report, Everyone Has Bug Reports To Accept: I was partway through college. I was taking a class about US films of 1939 and their social/historical context. The professor said something in a lecture about Upton Sinclair. I went to his office hours and checked: had he meant Sinclair Lewis? He had! And in the next lecture, he said: I made an error last time, I said Upton Sinclair when I meant Sinclair Lewis in [context], Sumana corrected me, thanks Sumana!

And then several weeks later, we were discussing some movie and I raised my hand and said something about a male character seeming "effete" but I pronounced it like "eff et", like the "ette" part was like how you pronounce the end of "suffragette". I think I'd never heard it aloud before, just read it. Classic autodidact pronunciation mistake.

And Professor Michael Rogin said: what?

And I said: Effete. Like, effeminate.

And he said: Oh, you mean effete! [And he pronounced it like "ef-feet".] But you corrected me about Sinclair Lewis before, so it's fine. And then we carried on the actual conversation and I didn't feel bad. It was like: well, we've both made mistakes and corrected each other, and we're fine, and let's talk about the substantive point now.

I'm using italics instead of quotation marks here because I'm sure my memory is paraphrasing. My point is: Professor Rogin, you made me feel okay about taking that particular bug report, may you rest in peace, and I still remember the nonchalant humility and self-confidence you demonstrated and encouraged in me.

Filed under:

(1) : MOSS Video, BSSw Honorable Mention, and The Maintainership Book I Am Writing:


Mozilla interviewed me about the Python Package Index (PyPI), a USD$170,000 Mozilla Open Source Support award I helped the Python Software Foundation get in 2017, and how we used that money to revamp PyPI and drive it forward in 2017 and 2018.

From that interview, they condensed a video (2 minutes, 14 seconds) featuring, for instance, slo-mo footage of me making air quotes. Their tweet calls me "a driving force behind" PyPI, and given how many people were working on it way before I was, that's quite a compliment!

I will put a transcript in the comments of this blog post.

(Please note that they massively condensed this video from 30+ minutes of interview. In the video, I say, "the site got popular before the code got good". In the interview, I did not just say that without acknowledging the tremendous effort of past volunteers who worked on the previous iteration of PyPI and kept the site going through massive infrastructure challenges, but that's been edited (for brevity, I assume).)

This video is the first in a series meant to encourage people to apply for MOSS funding. I mentioned MOSS in my grants roundup last month. If you want to figure out whether to apply for MOSS funding for your open source software project, and you need help, ping me for a free 20-minute chat or phone call and I can give you some quick advice. (Offer limited in case literally a hundred people contact me, which is unlikely.)


The Better Scientific Software (BSSw) Fellowship Program "gives recognition and funding to leaders and advocates of high-quality scientific software." I'm one of three Honorable Mentions for 2020.

The main goal of the BSSw Fellowship program is to foster and promote practices, processes, and tools to improve developer productivity and software sustainability of scientific code. We also anticipate accumulating a growing community of BSSw Fellowship alums who can serve as leaders, mentors, and consultants to increase the visibility of those involved in scientific software production and sustainability in the pursuit of scientific discovery.

Exascale Computing Project logoThat's why I'll be at the Exascale Computing Project Annual Meeting next week in Houston, so if you're there, I hope to meet you. In particular I'd like to meet the leaders of open source projects who want help streamlining contribution processes, growing more maintainers, managing communications with stakeholders, participating in internship projects like Google Summer of Code and Outreachy, expediting releases, and getting more out of hackathons. My consulting firm provides these services, and at ECPAM I can give you some free advice.


And here's the project I'm working on -- why I received this honor.

In 2020, I am writing the first draft of a book teaching the skills open source software maintainers need, aimed at those working scientists and other contributors who have never managed public-facing projects before.

More than developer time, maintainership -- coordination, leadership, and management -- is a bottleneck in software sustainability. The lack of skilled managers is a huge blocker to the sustainability of Free/Libre Open Source Software (FLOSS) infrastructure.

Many FLOSS project maintainers lack management experience and skill. This textbook/self-help guide for new and current maintainers of existing projects ("brownfield projects") will focus on teaching specific project management skills in the context of FLOSS. This will provide scalable guidance, enabling existing FLOSS contributors to become more effective maintainers.

Existing "how to run a FLOSS project" documentation (such as Karl Fogel's Producing Open Source Software) addresses fresh-start "greenfield" projects rather than more common "brownfield", and doesn't teach specific project management skills (e.g., getting to know a team, creating roadmaps, running asynchronous meetings, managing budgets, and writing email memos). Existing educational pathways for scientists and developers (The Carpentries, internships and code schools) don't cover FLOSS-specific management skills.

So I'm writing a sequel to Karl's book -- with his blessing -- and I'm excited to see how I can more scalably share the lessons I've learned in more than a decade of leading open source projects.

I don't yet have a full outline, a publisher, or a length in mind. I'll be posting more here as I grow my plans. Thanks to BSSw and all my colleagues and friends who have encouraged me.

Filed under:


You can hire me through Changeset Consulting.

Creative Commons License
This work by Sumana Harihareswara is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Permissions beyond the scope of this license may be available by emailing the author at sh@changeset.nyc.