Why you do not need any resolutions when it comes to open source management

I always start the year sure that I will do things better. Keep things in order, work smarter, drink less coffee, yet get more done. It can’t be that difficult, right? But usually by spring the realization that I just can’t keep up with my resolutions sets in (those Easter chocolates… who can resist?).

As an engineering executive, you probably know that your developers use open source components to speed up things. So your open source management resolutions may look something like this:

  • I will always know what’s in my software. That means updating the list of all the open source components in my software on a regular basis.
  • I will not let my developers add open source libraries to the software without reporting to me.
  • I will ensure that open source components that make their way into our products will not risk our own intellectual property.
  • I will ensure that we comply with all the requirements of all the licenses of all the open source components that we use.
  • I will know, in time, about any security vulnerability in open source components that affect my product. At least, insofar as known vulnerabilities (CVEs).

While all these resolutions must be kept, they can be very time consuming. According to Bulletproofexec.com 92% of resolutions fail for three reasons: goals are unrealistic, people don’t equip themselves, and fear is the motivating factor.

So when it comes to open source management, you don’t really need to worry about keeping these resolutions. 2015 can be the year you equip yourself – if you want to make open source management effortless, just drop me a line.

Happy New Year!