Microsoft has acquired GitHub

https://thenextweb.com/dd/2018/06/03/bloomberg-reports-microsoft-has-acquired-github/

In light of this, I would like us to seriously consider self-hosting a Gogs or GitLab instance. We're not eating our own dog food and setting a rather bad example in regards to self-hosting by using GitHub for issues and pull requests.

If it is agreed upon that this is the way to go, I can help to move all of the issues to the new platform, keeping interlinking intact.

This is a duplicate of prism-break/prism-break#2011

example: year 2019

Microsoft: "Users, we wrote a new terms of service and privacy policy! Read or F off from here!"
"We (Microsoft) have a right to take down anti-Windows software and data at any time"

They really like to f**k their users. Skype, Nokia, etc.
Compare "Before MS bought their service" and "After MS bought their service".

[MrAxlee]

Confirmed they have https://blog.github.com/2018-06-04-github-microsoft/

GitLab has an importer to bring your project across https://docs.gitlab.com/ee/user/project/import/github.html

I'd suggest Gitea as a contender to Gogs if moving to selfhosted - https://github.com/go-gitea/gitea

We may change hosting but let's keep using GitHub for project management. If we decide to change hosting, I think it's best if @privacytoolsIO self-hosts it again, this time with some hooks that automatically update the website when a new commit is pushed.

Not everyone noticed Gitlab infrastructure is behind Microsoft Azure lol
https://twitter.com/gnaggnoyil/status/1003656811172413440

[angela-d]

Gitlab is also a few steps short of being owned in part by Google.. which is worse?

Google invested $20 mil to Gitlab's C funding.

Gitlab is also moving to Google Cloud.

Next step is their IPO where one can assume Google will take a huge chunk of ownership.

The only choices are to have your code on Microsoft -or- Google's stack (if opting for Gitlab over Github), unless you self-host or go to an independent code host like Not a Bug or another corp like Bitbucket.

https://www.reddit.com/r/onions/comments/3ykctz/free_git_repository_hosting_accessible_only_over/
http://gitweb2zl5eh7tp3.onion/

and http://haklab4ulibiyeix.onion/users/sign_in

[heyhippari]

You have to consider the potential for new contributors that using the largest platform brings, as well as the work/money needed to migrate and/or host something, compared to the marginal improvement in privacy it's going to bring.

Basically, right now Github already has access to what you do here. The repository is public, your account is, as well. Everything you do on Github while contributing to a public repository is public.
Github also uses Google Analytics, so chances are Google also knows you're here. And even if you block Google Analytics, Github is public and scraped by Google's bots, so they likely know you're here anyway.

It's ridiculous to leave Github and all the visibility it brings to the project simply because "Microsoft may now see what we do" when Github is already public and everybody can already see what you do.

[jonaharagon]

I think it's best if @privacytoolsIO self-hosts it again, this time with some hooks that automatically update the website when a new commit is pushed.

This is now what is happening: https://www.privacytools.io/ is hosted on our own infrastructure.

Do we want to re-discuss self hosting Git, or is everyone here generally still fine with using GitHub for project management?

Definitely GitHub. Look at what happened to PRISM BREAK after moving to GitLab (which isn't even self-hosted and is still pretty big).

[Mikaela]

I am fine with GitHub, but if self-hosting was preferred, I have understood that Gitea is an option without much pain (while I have heard GitLab being called as difficult to selfhost).