Skip to content

Latest commit

 

History

History
43 lines (30 loc) · 2.37 KB

release-policy.md

File metadata and controls

43 lines (30 loc) · 2.37 KB
Raw

🛳️ Release policy

While releasing <COMPANY_NAME> code as open source is highly encouraged, we also need to be mindful that we shouldn't be giving away code that could be used by competitors to undermine our core business.

🖇️ Process

All open sourcing of <COMPANY_NAME> source code and content (e.g., text, images, fonts, data) should be registered by following the release process at XXX repo. If it's truly a personal project, not created as part of your job, related to <COMPANY_NAME>'s business, or incorporating <COMPANY_NAME>'s intellectual property, this policy does not apply. Just take care to not imply any endorsement by <COMPANY_NAME>. If you have any uncertainty talk with your manager, your HR business partner, or a member of the legal team.

If you are looking to release non-product code (such as utility libraries, tools, and sample code), complete the registration process. It will not require further review if the following conditions are met:

  • ✔️ You exercise good judgment and only release open source in the best interest of <COMPANY_NAME>.
  • ✔️ You release under the MIT license.
  • ✔️ The release does not collect telemetry.
  • ✔️ The release does not contain cryptography.
  • ✔️ The release does not contain data.

🏡 Location

All <COMPANY_NAME> open source on GitHub must live in a <COMPANY_NAME>-managed organization. These are projects that employees create as part of their jobs. Of course existing projects with their own multi-stakeholder governance like Homebrew belong within that community. But the vast majority of projects will go into the <COMPANY_NAME> organization.

✏️ Security

All <COMPANY_NAME> open source code must follow all applicable security requirements related to our software development lifecycle.

📖 License

All <COMPANY_NAME> open source code must be released under the MIT license. Where we are participating in existing community that does not use the MIT license, work with legal to determine the appropriate license. Our intention is to fit in with the existing community. We just need to confirm that the terms work for the business.

📤 Contributions

Contributions to a <COMPANY_NAME>-managed open source project are made under the project license in an inbound==outbound model.