How Not To Retire Open-Source Projects

A couple of days ago I had a chat with a friend, an ex-Telerik employee, who was the driving force behind JustDecompile product. We discussed briefly the recent Telerik announcement that open-sourced JustDecompile has been retired.

This the moment when you say “Wait a moment! JustDecompile is not open-source project”. This is correct. However JustDecompileEngine, the decompilation engine behind JustDecompile is open-source project since 2015. And if try to access it on GitHub you are greeted with a 404 error

Can you see the problem? Let’s look at another retired Telerik product – JustAssembly.

Fortunately, there are a lot of forks that contain this particular JustDecompileEngine commit

I worked at Telerik for many years and I know in details how the decisions for open-sourcing or discontinuing a project are taken. Without revealing any details, let me assure you that a lot of people are involved in these processes and the decisions aren’t taken lightly. Considering sales and marketing people, product owners, team leads, support leads and VPs it is easy to involve 10-12 persons.

It is easy to conclude that the people involved in this process don’t know what open-source software development is. This is somewhat typical for many corporations. It is funny. It would be funnier if Telerik restores JustDecompileEngine repo (wink-wink).

In case you decide to retire an open-source project I would suggest the following steps:

  1. Edit main README.md file
    • briefly explain the reason to retire the project
    • provide a list of alternative, preferable open-source projects
  2. Disable, if any, CI builds
  3. Consider changing the project license to even more permissive if possible
  4. Archive the repo (make it read-only)

Anyway, JustDecompile is now CodemerxDecompile and JustDecompileEngine has a new home and is even better.