It’s that fun time of the year for most people at work. It’s the beginning of the fiscal year, it’s review cycle time, it’s the beginning of a new quarter. For most managers, myself included, it means that there is a huge amount of work that needs to happen.
I head up the Open Source efforts at BrowserStack and, like most engineering leadership, I am looking at how we can promote our work without being overbearing in a community. Be equal partners. Friends, not foes. Democracy over Autocracy. For me, I don’t want to be creating Public Source code. I want to be growing communities, making lasting connections, and since I am an engineer, shipping code!
But what about metrics?
We can’t have all the fancy analytics that most “corporate” teams have, for the most part, as it goes against the general ethos of open source. This means the normal “metrics” that developer teams use are not available.
Measuring community is notoriously hard. We could look at Github stars, we could look at NPM downloads, and so on. Those are nothing more than vanity metrics in reality. They can be gamed. Imagine if I asked all engineers that worked at a Selenium in the cloud provider to star the Selenium project? Silly, isn’t it.
What about contributors? This can be a very good mechanism for newer projects but when they are more mature? I mean for something like Selenium, it’s been around for over decade. Contributors come and go but we’re not going to have the 200+ pull requests a month that something like React has. Does this make it any less successful? I don’t think so.
So what does this mean for corporate entities investing in Open Source?
For them I suggest that looking at the holistic view of the community is worthwhile. Open Source is about the general availability of code for people to use. Companies build on top of this daily to make multi-(m|b)illion companies. If it was about supporting, and I am not suggesting that volunteers don’t support, then a business can be built around that. Redhat and others have built a billion dollar company around that.
Some companies throw money at open source communities and think that is good enough. For smaller companies this make sense, make sure that there is money for those projects that help you grow, but this shouldn’t be seen as merely tax right offs or marketing ploys.
Open Source is a form of corporate responsibility. I don’t think that enough people are aware of this or that they think of it this way. Sometimes you can’t fully measure what is happening in the community and that’s fine but making sure you, as a company, are engaged in a meaningful way will allow you to see how healthy that community is. If you really need a metric then surveys tend to be a good measure but are really biased so your mileage will vary.
Invest where you feel it makes sense for your company and throw “time” at the problem rather than money. It doesn’t need to be a lot but a regular face, as part of company, can help when needed. And… Rarely do you need work on the latest and greatest. After all… you would think that jQuery is dead and React is the best from below. jQuery is still used on over 75% of the web.
At the end the day, Open Source is there as a great leveler. It’s there to help everyone and needs to be given the time to grow.