├── .github └── issue_template.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── GitHub AI Action RFI.pdf ├── GitHub Response to CA AI Frontier Models Draft Report.pdf ├── LICENSE ├── README.md ├── enisa-nis2-consultation-response.pdf └── issue-areas ├── global-collaboration.md ├── inclusion.md ├── innovation.md ├── open-source.md └── platform-responsibility.md /.github/issue_template.md: -------------------------------------------------------------------------------- 1 | 4 | 5 | Hi GitHub Policy, I have a policy suggestion that I’d :heart: your :eyes: on! 6 | 7 | - [ ] I have read the [Contributing Guidelines](CONTRIBUTING.md) 8 | - [ ] I have reviewed your priorities and examples of past work at [developer-policy/issue-areas](https://github.com/github/developer-policy/tree/main/issue-areas) 9 | 10 | ### What are you asking us to do? 11 | 12 | ### Why do you think this is important for developers? 13 | 14 | ### Where is this? Which jurisdictions does this impact? 15 | 16 | ### Who else is involved? Are there other groups that we should consider partnering with? 17 | 18 | ### Is there anything else we should know about your suggestion? 19 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at opensource@github.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Hi there! We're thrilled that you'd like to contribute to our Policy work to advance the interests of developers and the future of software. Be sure to read our [README](README.md) - it describes the project and its purpose. 4 | 5 | We welcome issues on the following topics: 6 | - Policy opportunities for GitHub to advance developers’ rights to innovation, collaboration, and equal opportunity, particularly in our priority policy areas stated on our [website](www.policy.github.com) and detailed in [developer-policy/issue-areas](https://github.com/github/developer-policy/tree/main/issue-areas). These should be concrete actions for us to take: support a bill, submit a regulatory filing, join an industry coalition, or the like. 7 | - Additional policy areas that GitHub should consider engaging on in order to support developers. 8 | 9 | To keep the conversation focused on how we can best help developers through our policy work, we moderate off-topic content. GitHub maintains a number of ways for you to get in touch on other topics, including: 10 | - You can review changes to our site policies and offer feedback in our dedicated [site-policy repository](https://github.com/github/site-policy) 11 | - You can share feedback on our products using our dedicated [feedback repository](https://github.com/github/feedback) 12 | 13 | Contributions to this project are dedicated to the public domain under [CC0-1.0](LICENSE.md). 14 | 15 | Please note that this project is released with a [Contributor Code of Conduct](CODE-OF-CONDUCT.md). By participating in this project you agree to abide by its terms. 16 | 17 | ## Open an issue 18 | 19 | We want your ideas for how GitHub can help advance developers’ rights to innovation, collaboration, and equal opportunity around the world. If you’re passionate about a policy topic that is particularly important to or disproportionately impacts developers, we want to hear from you. Open an issue and tell us how the policy affects you as a developer. 20 | 21 | We do not accept pull requests to alter the contents of this repository directly. If you see the need for a change and it is within scope, please help us by opening an issue. 22 | 23 | ## Resources 24 | 25 | - [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) 26 | - [Using Issues](https://docs.github.com/en/github/managing-your-work-on-github/about-issues) 27 | - [GitHub Help](https://help.github.com) 28 | -------------------------------------------------------------------------------- /GitHub AI Action RFI.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/developer-policy/fce35b47af5abea414f30b2d2f4ce4d366cf9605/GitHub AI Action RFI.pdf -------------------------------------------------------------------------------- /GitHub Response to CA AI Frontier Models Draft Report.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/developer-policy/fce35b47af5abea414f30b2d2f4ce4d366cf9605/GitHub Response to CA AI Frontier Models Draft Report.pdf -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # GitHub Policy: Fighting for developers 2 | 3 | As the home for all developers, GitHub is committed to shaping policies that promote their interests and the future of software. We work on policy in its many forms -- laws, regulations, norms, and standard practices -- to fight for developers and their rights to innovation, collaboration, and equal opportunity. 4 | 5 | The GitHub Policy Team created and maintains this repository as a place for developers to contribute to our policy work. We want to hear from you! 6 | 7 | ## How you can help 8 | 9 | We are interested in what you think we can do to best help developers. We want to hear about policy opportunities and new policy areas that you think GitHub should pursue to advance developers’ rights to innovation, collaboration, and equal opportunity. Please check out our [Contribution Guidelines](CONTRIBUTING.md) before opening an issue. 10 | 11 | ## Follow GitHub Policy 12 | 13 | Periodically we will update content here to highlight our work for developers. You can also visit our [webpage](https://github.com/about/developer-policy), read our [Policy Blog](https://github.blog/category/company/policy/), and follow us on Twitter at [@GitHubPolicy](https://twitter.com/githubpolicy). 14 | -------------------------------------------------------------------------------- /enisa-nis2-consultation-response.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/developer-policy/fce35b47af5abea414f30b2d2f4ce4d366cf9605/enisa-nis2-consultation-response.pdf -------------------------------------------------------------------------------- /issue-areas/global-collaboration.md: -------------------------------------------------------------------------------- 1 | # Global collaboration 2 | We support developers to work with anyone, anywhere because building and maintaining useful, secure software is a group effort that transcends borders. We work to reduce policy barriers to global collaboration and to demonstrate the local benefits that globally connected developers deliver. 3 | 4 | ## Our approach 5 | We engage policymakers to reduce the impact that trade restrictions, including sanctions and export controls, have on developers and their ability to collaborate. As part of this effort, we also support think tanks and researchers to demonstrate the value that global software collaboration brings, especially to local communities and national governments. In administering our platform, we try to make as many features on GitHub available to as many developers around the world as possible. 6 | 7 | Some examples of our past work on global collaboration: 8 | - [GitHub has secured a license to fully serve Iranian developers](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran/) 9 | - [We argue for open innovation as a way to address calls for digital sovereignty](https://thenewstack.io/bad-policies-around-open-innovation-will-cripple-economic-prosperity/) 10 | - [GitHub complies with sanctions while aiming to reduce their impact on developers as much as possible](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/) 11 | -------------------------------------------------------------------------------- /issue-areas/inclusion.md: -------------------------------------------------------------------------------- 1 | # Inclusion 2 | At GitHub, we take a holistic approach to [diversity, inclusion, and belonging](https://github.com/about/diversity) by aligning our efforts across our platform, people, philanthropy and policy efforts. Policy plays a critical role in lowering barriers and providing access for current and future developers from underrepresented backgrounds and regions. 3 | 4 | ## Our approach 5 | We support social sector organizations and grassroots efforts, intervene in court cases, and engage policymakers on policies that ensure opportunities for anyone to become a developer. This fosters the developer community to better reflect the vibrant diversity of our world. GitHub leverages its voice, resources and position in the ecosystem to advocate for voting rights, immigration reform, and net neutrality, among other issues. 6 | 7 | Some examples of our past work on inclusion: 8 | - [GitHub rallied developers to promote voter turnout in the 2020 U.S. Election](https://github.blog/2020-11-02-commit-your-vote-on-election-day/) 9 | - [GitHub joined court briefs to support developers’ and students’ ability to immigrate to the U.S.]( https://github.blog/2021-02-03-fighting-for-developers-github-policy-2020-in-review/#tech-inclusion) 10 | - [GitHub supported and helped mobilize developers on net neutrality in the U.S.](https://github.blog/2018-08-01-net-neutrality-updates-from-india-and-the-us/) and more recently [filed a comment in Mexico](http://www.ift.org.mx/sites/default/files/industria/temasrelevantes/consultaspublicas/documentos/20-07-15-373github.pdf) 11 | -------------------------------------------------------------------------------- /issue-areas/innovation.md: -------------------------------------------------------------------------------- 1 | # Innovation 2 | We advocate for copyright, patent, and employment rules that further developers’ interests and the software ecosystem as a whole. We aim to lead by example with the policies that we administer on our platform and for our employees. 3 | 4 | ## Our approach 5 | We engage policymakers, courts, and other venues to ensure that the developer perspective is considered whenever innovation policies change. On our own platform, we run a developer-first [DMCA takedown process](https://docs.github.com/en/github/site-policy/dmca-takedown-policy). For example, we do not automatically disable forks when disabling a parent repository because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by fair use. 6 | 7 | 8 | Some examples of our past work on innovation: 9 | - [GitHub refers developers to independent legal counsel when confronted with DMCA 1201 claims](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) 10 | - [We assed what Google v. Oracle meant for developers](https://github.blog/2021-04-06-supreme-court-sides-with-developers-in-google-v-oracle/) 11 | - [GitHub filed a comment with the U.S. Copyright Office rulemaking on DMCA 1201 exemptions](https://github.blog/2021-03-15-fud-chills-github-stands-with-security-researchers-on-dmca-section-1201/) and [explains how developers can do so as well](https://github.blog/2020-11-19-take-action-dmca-anti-circumvention-and-developer-innovation/) 12 | - [We open sourced GitHub’s Balanced Employee IP Agreement that provides clarity in contributing to projects](https://github.blog/2020-12-14-inspired-by-open-source-balanced-employee-intellectual-property-agreement-2-0/) 13 | - [We joined a letter to the U.S. Senate to weigh in on needed reform to the way patents are challenged and assessed](https://www.uspto.gov/sites/default/files/documents/11192020GitHubInc.pdf) 14 | - [GitHub worked to gain an exemption for open source developers in the EU Copyright Directive](https://github.blog/2018-10-23-github-goes-to-brussels/) and [help developers get engaged directly](https://github.blog/2018-09-10-how-developers-can-defend-open-source-from-the-eu-copyright-proposal/) 15 | -------------------------------------------------------------------------------- /issue-areas/open-source.md: -------------------------------------------------------------------------------- 1 | # Open source 2 | GitHub is the home for much of the world’s open source development. We believe that collaborative development through the open source process accelerates innovation. 3 | 4 | ## Our approach 5 | GitHub fights for open source to ensure the world’s open source code is available and accessible for everyone to use, modify, and learn from. We provide open source legal tools and policy analysis to the community. We also engage policymakers to ensure that their policies and laws enable and encourage the use of open source. 6 | 7 | Some examples of our past work on open source 8 | - [We open sourced a tool to help scale project governance](https://github.blog/2021-07-22-minimum-viable-governance-lightweight-community-structure-foss-projects/) 9 | - [We provided analysis of the trend towards ‘source available’ licenses](https://github.blog/2021-03-18-whats-up-with-these-new-not-open-source-licenses/) 10 | - [GitHub offered comments to the U.S. NTIA on promoting open source in 5G](https://github.blog/2021-02-23-open-source-in-the-5g-stack/) 11 | - [We joined a petition to save the Open Technology Fund, which funds open source software for the public good](https://github.blog/2020-07-02-github-supports-the-open-technology-fund/) 12 | - [GitHub joined the GPL Cooperation Commitment](https://github.blog/2018-11-07-github-joins-gpl-cooperation-commitment/) 13 | -------------------------------------------------------------------------------- /issue-areas/platform-responsibility.md: -------------------------------------------------------------------------------- 1 | # Platform responsibility 2 | We aim to protect developers’ ability to collaborate by ensuring changes to intermediary liability rules and safe harbors affecting developer collaboration platforms do not impose requirements to proactively filter or increase takedowns of code. We strive to provide a safe and inclusive space that transparently respects rights to free expression, assembly, and association. 3 | 4 | ## Our approach 5 | Our primary message to policymakers is that “code is different.” In contrast to other hosted content, code is less likely to be abusive content and is more likely to have open copyright licenses attached to it. The harms imposed by filtering or taking down code content are also different than the content hosted on most platforms: projects have dependencies on one-another and thus one takedown can have effects on countless more. 6 | 7 | Some examples of our past work on platform responsibility: 8 | - [GitHub scores high in content moderation report from EFF](https://github.blog/2019-06-25-github-scores-high-in-content-moderation-report/) 9 | - Our legislative and tracking efforts on safe harbors for software collaboration, [part 1 (focused on the US)](https://github.blog/2020-10-06-safe-harbors-for-software-collaboration-part-1/) and [part 2 (focused globally)](https://github.blog/2021-04-08-safe-harbors-for-software-collaboration-part-2/) 10 | - Our latest [Transparency Report](https://github.blog/2021-08-25-2021-transparency-report-january-to-june/) 11 | --------------------------------------------------------------------------------