Build an Open Source Project: Behind the Scenes

1

Hacker News

At some point in time, I decided to try the power of Hacker News, and it was so impressive. Tons of feedback and feature requests alongside the increasing number of "stars." I'm not a very active Twitter user and have a few followers, but after the post to Hacker News, I found there are a lot of bots on Twitter trying to repost every piece of news. There were even a couple of discussions after such reposts.

#Social Networks #Social News #Startups 500 social mentions

2

Homebrew

We like to push our Open Source project to GitHub, but it's code-centric. We should help our users with clear and easy installation instructions. And here is a trap. I use Mac and want my "xq" utility installable using Homebrew:.

#Package Manager #Front End Package Manager #Windows Tools 877 social mentions

3

Codecov

Usually, you can't build a product without using various tools. Some of them can be free, and some of them can be commercial. The great benefit of working on Open Source projects is that a lot of companies with commercial products have special offers for non-commercial development. In the case of the "xq" utility, which is written in Go, I use GoLand IDE by JetBrains. I paid for it for several months but later tried to apply to their Open Source Program. They provided me with a license not only for GoLand but for the whole product pack! Another example is the CodeCov service. I want to track code coverage in an easy way to control the quality and ensure all major scenarios are covered by tests. CodeCov is quite expensive for commercial products (especially the hosted version, which costs ~50K USD), but it's absolutely free for Open Source projects, and this is awesome! If you need project hosting (e.g., for demo purposes), you may try to apply to the DigitalOcean Open Source initiative, and there are other alternatives available. This is just a few examples.

#Code Coverage #Code Quality #Code Analysis 18 social mentions