Navigating the Path to Open Source: A Guide for Company-Owned Software

As a seasoned SEOer, I have managed the open source processes at Yahoo and have closely observed how other tech companies handle similar situations. While the process isn't complicated, a thorough understanding of the requirements and steps is crucial to ensure everything is done correctly.

Ensuring the Right to Publish

To publish your company's software as open source, you must have the right to do so. This means you either need to be the copyright holder or have explicit permission from the copyright holder to publish under an open source license. It's vital to gain this permission in writing, such as through a durable medium, to protect against any future disputes about unauthorized publication.

Understanding Your Company's Policy

Most tech companies, particularly those in the US, have policies that stipulate when an employee writes code for work, the company receives the copyright. This means the company, or an authorized representative, has the ultimate decision on whether the code is published. In some cases, the company might choose to transfer the copyright to an individual, which can be beneficial if the company wants to distance itself from the code. However, such transfers are straightforward and can be managed with signed forms.

Reviewing and Preparing the Code

Once you have the necessary permission, the next step is to review and prepare the code for publication. Here are the key steps:

1. Copyright Ownership Validation

Verify that the company owns the copyright on the code. If you include third-party code within your project, ensure you review and confirm its license to avoid conflicts. Tools like BlackDuck and Palamida can help scan the code for embedded open source components and check their licensing compliance.

2. Additional Code Review

Scour the code for any proprietary content or references to internal systems. You should also check for any hints of a proprietary nature, such as internal email addresses or comments about competitors' future plans. Tools can also scan the code for profanity and certain keywords that might indicate proprietary content.

3. Granting Permission to Publish

After thorough review, grant permission for the code to be published under an appropriate open source license. Typically, a permissive license, like the Apache License, is chosen, but the final decision depends on the nature of the code and the project.

Considerations Beyond the Code

Before publishing, consider whether you should write a blog post to draw attention to the project. It's crucial to weigh the potential benefits against the risk of revealing sensitive information or infringing on patent and copyright rights.

Sample Publishing Process

Let's take an example. If you worked at my company and wanted to open source a project, you would request permission to publish the project. I would review the code, verifying its copyright status, and check for any third-party components. I might also use code analysis tools to ensure compliance with license requirements. If everything checks out, I would grant permission to publish.

Notable Differences Among Companies

While the core process is similar for many companies, there can be variations. For instance, at Google or Facebook, the process might be slightly more or less efficient in certain areas. However, the fundamental steps of obtaining permission and reviewing the code are universally applicable.

Remember, the goal is not just to publish the code but to do so responsibly. Make sure you are not revealing any sensitive information and that the project aligns with your company's broader strategic objectives.

Feel free to share your thoughts or ask any questions; I'm here to help!