Migrating from Github

[phabricator-migrator]

Information

ID: 800
PHID: PHID-TASK-wo55qbljscjnuu4bnt5x
Author: HulaHoop
Status at Migration Time: resolved
Priority at Migration Time: High

Description

In the longterm it would be a good idea to migrate from github. Lets discuss alternatives in this ticket. Fortunately our bugtracker issues have long been migrated to our infrastructure.

The first question is whether we should self-host the code or use third parties. If we decide on a third party we should see which cannot impose lock-in on our git data.

Comments

---

yzxd

2018-06-23 21:23:00 UTC

I’ve done a little research into this. I found the following (free) self-hosted alternatives to GitHub.

• [[ https://about.gitlab.com/ | GitLab CE ]] ([[ Explore projects · GitLab | demo ]])
• [[ http://gitblit.com/ | Gitblit ]] ([[ https://dev.gitblit.com/ | demo ]])
• [[ https://rhodecode.com/ | RhodeCode ]] ([[ https://code.rhodecode.com/ | demo ]])
• [[ https://gogs.io/ | Gogs ]] ([[ https://try.gogs.io/ | demo ]])
• [[ Gitea Official Website | Gitea ]] ([[ https://try.gitea.io/ | demo ]]; this is a fork of Gogs)

---

Patrick

2019-01-03 12:22:23 UTC

https://qubes-os.org/faq/#what-does-it-mean-to-distrust-the-infrastructure

What does it mean to “distrust the infrastructure”?

A core tenet of the Qubes philosophy is “distrust the infrastructure,” where “the infrastructure” refers to things like hosting providers, CDNs, DNS services, package repositories, email servers, PGP keyservers, etc. As a project, we focus on securing endpoints instead of attempting to secure “the middle” (i.e., the infrastructure), since one of our primary goals is to free users from being forced to entrust their security to unknown third parties. Instead, our aim is for users to be required to trust as few entities as possible (ideally, only themselves and any known persons whom they voluntarily decide to trust).

Users can never fully control all the infrastructure they rely upon, and they can never fully trust all the entities who do control it. Therefore, we believe the best solution is not to attempt to make the infrastructure trustworthy, but instead to concentrate on solutions that obviate the need to do so. We believe that many attempts to make the infrastructure appear trustworthy actually provide only the illusion of security and are ultimately a disservice to real users. Since we don’t want to encourage or endorse this, we make our distrust of the infrastructure explicit.

https://qubes-os.org/faq/#why-do-you-use-github

Why do you use GitHub?

Three main reasons:

1. We distrust the infrastructure, including GitHub (though there are aspects we’re still working on).
2. It’s free (as in beer). We’d have to spend either time or money to implement a solution ourselves or pay someone to do so, and we can’t spare either one right now.
3. It has low admin/overhead requirements, which is very important, given how little time we have to spare.

---

Patrick

2020-06-04 17:00:08 UTC

Alternative to github.com now needed.

Github allows maximum file size 100 MB and at time of writing monero-wallet-gui was slightly bigger.

git push origin master

remote: Resolving deltas: 100% (24/24), completed with 13 local objects.
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
remote: error: Trace: 524ad74301f8bed01b8fae36025cbadf
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File usr/bin/monero-wallet-gui is 110.91 MB; this exceeds GitHub's file size limit of 100.00 MB
To ssh://github.com/Whonix/monero-gui.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://git@github.com/Whonix/monero-gui.git'

Managing large files - GitHub Docs

Can’t use gitlab… There is…

Whonix · GitLab

…but… gitlab.com blocking Tor users:
Gitlab.com blocking TOR? - How to Use GitLab - GitLab Forum

---

Patrick

2020-06-10 16:20:56 UTC

Whonix moving from GitHub to GitLab