fabric


Fri, Sep 18, 2020 | fabric, invoke, maintainership, paramiko
A quick followup to my previous missive. Triage I’ve lined up a handful of other Github users for each of my major repos, granted them the triage bit in most cases, and am easing into a weekly review cadence. In one case, I gave a couple folks more privileges as I’ve already collaborated with them for a while - though until more of the below is taken care of, it’s largely symbolic.

The first step

is admitting you have a problem; so with that in mind:

Hi. My name’s Jeff, I maintain several OSS projects you may be familiar with1, and I’m burned out.

I lie awake at night, unable to sleep, crippled by guilt. During the day, it’s anxiety and fear that cripple instead, making the thought of facing the issue tracker unbearable.

Development on my projects has slowed far more than I ever intended, and while I have excuses2, push has clearly come to shove. Something must change.


Wed, May 9, 2018 | announcements, fabric, invoke

It took (much) longer than anticipated, for a number of reasons, and like any good .0 release it’ll take a few minor releases to really get up to speed – but it’s here! Fabric 2.0.0 is now out on PyPI, along with the project that does much of the heavy lifting, Invoke 1.0.0.

Please see the upgrade documentation for the gory details, and if you like, read on for some non-instructive reflection on the occasion.


Mon, Apr 17, 2017 | announcements, fabric, invoke

Opening remarks

This has been a hard blog post to write; not in a technical sense (though blogging always is - it’s why I don’t do more of it!) but simply because Fabric 2 has been “coming soon” for what feels like ages, and putting it out in the open turns out to involve a lot of emotions.

But here we are: Fabric 2 is no longer private!


Tue, Jul 5, 2016 | announcements, career, fabric, personal
Being picky As mentioned in my 2015 round-up post, I’ve been trying to make ends meet, re: open source plus a paying job. In March, I parted ways with a bunch of great people to take time off1 and embark on a job hunt. My goal was to find a company that could dedicate time to upstream maintenance, used my projects heavily in production, or both: Without a clear split between “internal” and “external” development time, prioritization becomes a tug of war leaving both sides unhappy.