I wanted to get this out there before people start noticing my inactivity and start drawing their own conclusions:
I’m taking a break from all Elm-related open source work.
The main reason stems from something really cool that happened this summer: I became a father
As such, the time I’ve got to spend on hobbies and open source work is diminished and hard choices has had to be made. Stopping open source Elm work, is one of those hard choices.
Me stepping away does mean that certain packages will go unmaintained. The most important of which I guess is
elm-git-install. For packages that reside in the
elm-community namespace, I hope that new maintainers will step in in time. For packages that have been published under my username (Skinney), I recommend that people fork those packages if they need to fix bugs or add features, as I will not be giving away write access to those repos.
Now, some might be remembering that my employer lets me spend up to 20% of my time working on Elm related things. If I can spend work hours contributing to Elm, how does becoming a parent change that?
It turns out that 20% time is actually a small amount of time There were some days which largely went into research. As in, there where whole days were I almost didn’t write any code, just read papers and went through issues and PRs on github, trying to figure out how best to contribute to the community. After a while, I started spending free time doing all the things which wasn’t code, just so I could spend those days feeling productive. Ironicly, having 20% of work hours to contribute to Elm actually increased the amount of free time I spent on contributing to Elm.
Because of that, and with some thinking on how life would be after this summer, I stopped spending 20% of my work time on Elm already back in march. Turns out, with the whole COVID-19 thing and the unforseen amount of time I spent on getting elm-warrior ready for a workshop, it was one of the better decisions I’ve made all year.
But I want to underline that this is, in fact, a break and not a good bye. I’ll still hang around the slack and in these forums, and I do still get a lot of exposure to Elm in my day-to-day job. I also expect to come over an interesting implementation in search of a problem every now and again too.