2 ms·
I can confirm that for me, most of my own OSS projects serve the singular purpose of scratch-itching. :) Sometimes I feel like a tool that I write is generic en
by majewsky 9y ago
I can confirm that for me, most of my own OSS projects serve the singular purpose of scratch-itching. :) Sometimes I feel like a tool that I write is generic enough to be able to serve other people, and I market them a bit (most commonly when someone happens to ask "what do you use to do X?", both in real life and on the internet).
To answer your specific questions, I'll take my most-starred repository, https://github.com/holocm/holo https://github.com/holocm/holo (47 stars).
1) I wanted to use configuration management on my private notebook, but all existing systems seemed to be optimized for much bigger use-cases and have a lot of moving parts that need to be understood. So I thought "It can't be that hard to just deploy a few config files." Classic scratch-itching. What a fool I was. :D
2) As said above, when the discussion happened to come to the configuration mgmt topic, I chimed in and noted that my tool exists. Also, I made a website (http://holocm.org http://holocm.org ) for documentation and a Twitter account (https://twitter.com/holocm https://twitter.com/holocm ) to announce releases, and retweeted the announcements into my private account to spread them.
3) I never did a "Show HN" for some reason. I did, however, give a lightning talk at the 31C3 (the recording is in the pinned tweet on the Twitter account, if you're interested).
4) How is that "unfair"?
Everything you do you do because of some sort of motivation. For me, my OSS projects are all about "I need something that works for me", so a working system on my machine is all the reward that I need. I do a small amount of publicity, such as replying here ;), but not because I need the attention. It's just a nice bonus.