In June of 2019, Tidelift and The New Stack jointly fielded a survey of professional software developers. Almost 400 people responded with thoughts about how they use open source software today, what holds them back, and what tools and strategies would help them use it even more effectively. In particular, with this survey, we were interested in learning how a managed open source strategy might help developers reclaim time, speed up development, and reduce risk.
In this post, we share the fifth of eight key findings. If you don’t wait to wait for the rest of the results, you can download the full survey report right now at the link below.
Finding #5: Project activity, licensing, and maintainer responsiveness are key factors in choosing open source projects.
Given the maintenance headaches respondents described in earlier findings from this survey, one obvious way to avoid them is to make good package choices in the first place. In the next part of our survey, we asked developers to tell us more about how they make decisions regarding which open source packages to use.
The first question on the subject asked how important some key project characteristics are when developers select packages.
When it comes to choosing packages, licensing is the most crucial issue: 61% of respondents said having an acceptable software license is extremely important. An additional 25% report licensing is somewhat important, for a total of 86% rating open source licensing as either extremely or somewhat important. Only 4% of respondents don’t see this as an important issue.
This is particularly meaningful for companies with more than 1,000 employees, where 78% of respondents say having an acceptable open source license is extremely important. These findings clearly show that there are some “dealbreaker” licenses out there that most users attempt to avoid.
When it comes to choosing packages, licensing is the most crucial issue: 61% of respondents said having an acceptable software license is extremely important. An additional 25% report licensing is somewhat important, for a total of 86% rating open source licensing as either extremely or somewhat important.
While activity (e.g., recent and volume of issues, commits and pull requests) tied with licensing in overall importance (86%), it had a lower percentage rating extremely important (43%) than licensing.
Also important when choosing open source packages is maintainer responsiveness, which 80% of respondents view as either extremely important or somewhat important when selecting an open source package to use. This is followed by established policies and documentation (e.g., code of conduct, contributing guide), with 72% of respondents rating this characteristic as important.