GitHub <a href="https://www.theatlantic.com/technology/archive/2020/01/ice-contract-github-sparks-developer-protests/604339/">has

a for-profit software services contract with the USA Immigration and Customs

Enforcement (ICE)</a>.  Activists, including some GitHub employees, have been

calling on GitHub for two years to cancel that contract.  GitHub's primary

reply has been that their parent company, Microsoft, has sold Microsoft Word

for years to ICE without any public complaints.  They claim that this somehow

justifies <em>even more</em> business with an agency whose policies are

problematic.  Regardless of your views on ICE and its behavior, GitHub's

        ongoing <a href="https://www.latimes.com/business/technology/story/2020-06-12/github-ceo-black-lives-matter-employees-demand-end-ice-contract">dismissive and disingenuous</a> responses to the activists who raised this important issue show that GitHub puts its profits above concerns from the community.</p></li>

<li><p>While GitHub pretends to be pro-FOSS

  (like <a href="https://lwn.net/Articles/17822/">SourceForge before

    them</a>), their entire hosting site is, itself, proprietary and/or

  trade-secret software.  We appreciate that GitHub allows some of its

  employees to sometimes contribute FOSS to upstream projects, but our

  community has been burned so many times before by companies that claim to

  support FOSS, while actively convincing the community to rely on their

    proprietary software.  We won't let GitHub burn us in this same way!</p></li>

<li><p>GitHub differs from most of its peers in the FOSS project hosting

industry, as GitHub does not even offer any self-hosting FOSS option.

Their <em>entire</em> codebase is secret.  For example, while we have our

complaints about GitLab's business model of parallel “Community”

and “Enterprise” editions, at least GitLab's Community Edition

    publicly as FOSS.</p></li>

<li><p>GitHub has long sought to discredit copyleft generally.  Their various

CEOs have often spoken loudly and negatively about copyleft, including their

founder (and former CEO)

devoting <a href="https://www.youtube.com/watch?v=-bAAlPXB2-c">his entire

OSCON keynote on attacking copyleft and the GPL</a>.  There are also examples

of <a href="https://github.com/BenKallos/legislation/issues/2#issue-46911010">GitHub

employees filing bug tickets</a> in copylefted projects to cajole them to

    change to non-copyleft licenses.</p></li>

    <li><p>GitHub is wholly owned by Microsoft, a company whose executives have historically repeatedly attacked copyleft licensing.</p></li>

    </ul>

<h2>How Do I Give Up GitHub?</h2>

<p>The reason that it's difficult to leave GitHub is a side-effect of one of

the reasons to leave them: proprietary vendor lock-in.  We are aware that

GitHub, as the “Facebook of software development”, has succeeded

in creating the most enticing walled garden ever made for FOSS developers.

Just like leaving Facebook is painful because you're unsure how you'll find

and talk with your friends and family otherwise — leaving GitHub is

difficult because it's how you find and collaborate with

co-developers. GitHub may even be how you find and showcase your work to

prospective employers.  We also know that some Computer Science programs

newcomers and members of underrepresented groups in FOSS — to give up

on GitHub.  If you don't feel that you or your project can yet leave GitHub,

we ask that you raise awareness

by <a href="https://sfconservancy.org/docs/SupportGiveUpGitHub-README-snippet.md">adding

this section to your README.md</a> to share your concerns about GitHub with

your users.  If you're ready to leave GitHub, you

can <a href="https://sfconservancy.org/docs/GiveUpGitHub-README.md">use this

README.md template</a> to replace your current one.</p>

<p>

<blockquote><p>千里之行始於足下<br/>The journey of a thousand miles begins with a single step.</p></blockquote>

<div style="text-align: right"><p> &mdash; <cite>老子 (Lao Tsu) in Chapter 64

      of 道德经 (Tao Te Ching)</cite>

</p></div>

</p>

<h2>Resources to Give Up GitHub</h2>

<p>Here are some resources to help you quit GitHub.  We'll be expanding this

list regularly as we find more resources.  If you'd like to suggest a

resource not yet listed, you can discuss it on

the <a href="https://lists.sfconservancy.org/mailman/listinfo/give-up-github">Give-Up-GitHub

    mailing list</a>.</p>

<ul>

    <ul>

    <li><a href="https://codeberg.org">CodeBerg</a></li>

    <li><a href="https://sourcehut.org/">SourceHut</a></li>

        <ul><li><a href="https://gitea.io">Gitea</a></li>

        <li> <a href="https://gitlab.com/rluna-gitlab/gitlab-ce">GitLab

        Community Edition</a> (note, the GitLab Enterprise Edition, which is

        provided to the public on gitlab.com,  is (like GitHub) trade-secret,

          proprietary, vendor-lock-in software)</li>

    (We'll be adding tutorials soon on how to self-host!)

    </ul></p>

<h2>Ways To Help Even <em>Before</em> You Give Up GitHub</h2>

<p>Here are some ideas of how you can help raise the importance of this issue

even while you're still a GitHub user.  (We'll publish longer tutorials in

future about these and other ways to help.)

<ul>

<li><p><a href="https://sfconservancy.org/docs/SupportGiveUpGitHub-README-snippet.md">Add

    this section to your README.md</a> to share your concerns about GitHub

  with your users.</p></li>

<li><p>Respectfully and kindly ask, before you contribute to a project on

  GitHub, if they could provide alternative means to contribute other than

    using GitHub.</p></li>

<li><p>Explain to your employer the dangers of relying on GitHub's proprietary

    vendor lock-in products.</p></li>

<li><p>Join

  the <a href="https://lists.sfconservancy.org/mailman/listinfo/give-up-github">give-up-github

  mailing list</a> and start threads about your difficulties leaving GitHub.

  This will help us explore solutions with you and add material to this