From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Migrate to notabug.org
Date: Mon, 30 Sep 2019 04:52:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14835@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
New issue by mahaer-mahmud on void-packages repository
https://github.com/void-linux/void-packages/issues/14835
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
## Why I think we should abandon GitHub and move to NotABug.org
You may feel tempted to use GitHub since it's the moat popular website for code hosting... you should think twice, however. GitHub has a couple of issues with itself. The free software alternative ``notabug.org`` gets rid of those issues.
1. GitHub does not allow some countries to use its service
For example, [look at what they did to Iranian developers](https://medium.com/@d.aliyamini/microsoft-enters-github-banned-iranian-developers-843f7c60a146). GitHub is doing this because the state government is anti-American, and does not fit Microsoft's pro-American agenda. In reality, most Iranian developers are innocent people who would not decline to meet an American. Based on this, it seems GitHub will ban other countries with crazy governments but good people (for example, Indonesia). So if you don't condone developer discrimination, don't develop on GitHub.
2. GitHub is not free (as in freedom) software
Since GitHub is not free software, it does not respect your four freedoms. It can mess with you whatever it wants, even if it's harmful to the developer, so as long as it benefits the company.
3. GitHub may not be secure
I get it, you're not looking for state-of-the-art encryption here. But since GitHub's owned by the big Microsoft, the big security agencies can judge you based on your activity. And they can treat you unfairly; as far as I know, these agencies aren't required to follow the constitution.
Thankfully, at least one of those reasons made you switch to ``notabug.org``. If you do switch, it would be a big benefit to you, as you are using a service oriented to the hacker and not the corporation.
However, if you don't have the nerve to go to ``notabug.org``, go to ``codeberg.org``, or set up your own Gittea instance.
Thank you for your time.
next reply other threads:[~2019-09-30 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 2:52 voidlinux-github [this message]
2019-09-30 5:01 ` voidlinux-github
2019-09-30 6:02 ` [ISSUE] [CLOSED] " voidlinux-github
2019-09-30 8:17 ` voidlinux-github
2019-09-30 9:52 ` voidlinux-github
2019-09-30 9:53 ` voidlinux-github
2019-09-30 9:53 ` voidlinux-github
2019-09-30 9:54 ` voidlinux-github
2019-09-30 10:30 ` voidlinux-github
2019-09-30 10:33 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14835@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).