{"id":20585550,"url":"https://github.com/syngenta/open-source-guide","last_synced_at":"2026-03-07T16:03:32.911Z","repository":{"id":193167332,"uuid":"624153891","full_name":"syngenta/open-source-guide","owner":"syngenta","description":"Open Source Guide","archived":false,"fork":false,"pushed_at":"2023-09-10T23:47:22.000Z","size":16,"stargazers_count":7,"open_issues_count":0,"forks_count":0,"subscribers_count":3,"default_branch":"main","last_synced_at":"2025-12-09T00:27:30.812Z","etag":null,"topics":["documentation","guide","guidelines"],"latest_commit_sha":null,"homepage":"https://syngenta.github.io/open-source-guide/","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/syngenta.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2023-04-05T21:26:48.000Z","updated_at":"2025-07-01T10:16:09.000Z","dependencies_parsed_at":"2023-09-07T03:30:16.025Z","dependency_job_id":"753cd93a-b706-4bd9-becf-5d26c78f1061","html_url":"https://github.com/syngenta/open-source-guide","commit_stats":{"total_commits":2,"total_committers":1,"mean_commits":2.0,"dds":0.0,"last_synced_commit":"3ede542c568be4492fd09db3caff4ea8f40f66b5"},"previous_names":["syngenta/open-source-guide"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/syngenta/open-source-guide","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/syngenta%2Fopen-source-guide","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/syngenta%2Fopen-source-guide/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/syngenta%2Fopen-source-guide/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/syngenta%2Fopen-source-guide/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/syngenta","download_url":"https://codeload.github.com/syngenta/open-source-guide/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/syngenta%2Fopen-source-guide/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":30221193,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-07T14:02:48.375Z","status":"ssl_error","status_checked_at":"2026-03-07T14:02:43.192Z","response_time":53,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["documentation","guide","guidelines"],"created_at":"2024-11-16T07:08:34.380Z","updated_at":"2026-03-07T16:03:32.885Z","avatar_url":"https://github.com/syngenta.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Open Source Software (OSS) Guide\n\n**NOTE:** This document is neither legal nor comprehensive advice. It should not be taken as such.\n\n- [Introduction](#introduction)\n- [OSPO (Open Source Program Office) team](#ospo-open-source-program-office-team)\n- [Why should we pay attention to properly using open-source software?](#why-should-we-pay-attention-to-properly-using-open-source-software)\n- [Why should we contribute to open-source?](#why-should-we-contribute-to-open-source)\n- [How to use open-source code in closed-source projects](how-to-use-open-source-code-in-closed-source-projects.md)\n- [How to contribute to open source](how-to-contribute-to-open-source.md)\n- [How to open source our code](how-to-open-source-our-code.md)\n- [Notes](#notes)\n\n## Introduction\n\n\u003e Open-source software (OSS) is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose.\n\u003e\n\u003e [https://en.wikipedia.org/wiki/Open-source_software](https://en.wikipedia.org/wiki/Open-source_software)\n\nIt's impossible to find or create any modern software that does not rely on open-source code in its foundation.\n\nWe heavily use open-source code to develop software for both internal users and external clients and depend on it in our operations.\n\nThis guide will try to cover three main questions:\n\n1. [How to properly use open-source code in closed-source projects?](how-to-use-open-source-code-in-closed-source-projects.md)\n2. [How to properly contribute to open-source?](how-to-contribute-to-open-source.md)\n3. [How to open source our code?](how-to-open-source-our-code.md)\n\n## OSPO (Open Source Program Office) team\n\nThe OSPO team is an informal team of open-source enthusiasts and advocates in Syngenta.\n\nWe are working with R\u0026D and digital teams to educate and assist them with:\n\n- open-sourcing their code;\n- contributing to open-source projects;\n- applying the best community and industry standards and practices for their open-source projects;\n- guiding on Open Source Software (OSS) licensing.\n\nWe are glad to help you with any questions you may have about open-source, licensing, best practices, etc. Talk to us via [ospo@syngenta.com](mailto:ospo@syngenta.com) email or MS Teams chat.\n\n## Why should we pay attention to properly using open-source software?\n\n**TL;DR — violation of OSS licenses may lead to lawsuits, fines, and reputation losses for the company.**\n\nOpen-source software doesn't always mean we can freely use it in our projects — **open-source ≠ free**.\n\nThere are tens of different [OSS licenses](https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses#General_comparison). Different licenses have [different permissions, conditions and limitations](https://choosealicense.com/licenses/) for use.\n\nSome of them, such as [MIT License](https://choosealicense.com/licenses/mit/), are **permissive** — you are allowed to do almost anything. But you must keep the License text and copyright notice.\n\nOthers, such as [GNU AGPLv3](https://choosealicense.com/licenses/agpl-3.0/) are **strictly copyleft**. Using GNU AGPLv3 licensed library in your project — automatically requires you to open-source your project's code under the same GNU AGPLv3 license. Missing this requirement will result in a license violation — possible lawsuits, fines, and reputations losses for the company.\n\nSome OSS software may have **commercial-only** licenses. This means that even if the code of such a library is open-sourced, we can't use it in our projects without buying a commercial license.\n\nUsing some Open Source License Scanning Tool (OSS License Scanner) is highly recommended to check if your project uses open-source code properly. It could be a 3-rd party service or a self-hosted tool — choose based on your project's needs and technology stack.\n\n## Why should we contribute to open-source?\n\nThere are many ways we could contribute to open-source:\n\n- Upstream our changes/features/fixes to open-source libraries.\n- Publishing some of our code as open-source:\n  - our infrastructure and helper libraries (frameworks, etc.);\n  - client libraries for Syngenta's products;\n  - client libraries for third-party products (ORMs, wrappers, etc.);\n  - scientific code in the R\u0026D environment.\n\n### Benefits of open-sourcing our projects and code\n\n- Contributions are valuable to the open-source community. It's a meaningful way to support open-source projects and the community.\n- Collaborating with scientific research communities and other industrial organizations via open-source projects would benefit all parties and our industry.\n- Upstreaming our changes/features/fixes reduces maintenance costs as we don't need to update our forks constantly.\n- Some of our open-sourced code may receive valuable support and improvements from the open-source community.\n- We may not always be able to justify the continued internal support and development of our internal code and tools. Open-sourcing such code and tools helps to preserve and continuously improve our work. This is particularly valid for scientific code.\n\n### Considerations for open-sourcing our projects and code\n\n- We should ensure that open-sourcing code will not disclose information, know-how or code that gives us a significant competitive advantage.\n- We must be sure that we do not release code that does not belong to us.\n- In general, we do not open source highly-specific code that we expect not to be helpful for the community.\n\n## How to use open-source code in closed-source projects\n\n[How to use open-source code in closed-source projects](how-to-use-open-source-code-in-closed-source-projects.md)\n\n## How to open source our code\n\n[How to open source our code](how-to-open-source-our-code.md)\n\n## How to contribute to open source\n\n[How to contribute to open source](how-to-contribute-to-open-source.md)\n\n## Notes\n\n1. Inspired by [GitLab's Handbook OSS Guide](https://about.gitlab.com/handbook/engineering/open-source/).\n2. Parts of this document are taken from Syngenta's \"Open Source Release Checklist (R+D) 2013\".\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsyngenta%2Fopen-source-guide","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsyngenta%2Fopen-source-guide","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsyngenta%2Fopen-source-guide/lists"}