aboutsummaryrefslogtreecommitdiffhomepage
path: root/_drafts/beginners-guide-sourcehut.md
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2025-01-24 13:47:54 -0500
committerBradley Taunt <bt@btxx.org>2025-01-24 13:47:54 -0500
commitea58f827d1315cd5ab2ee3fdfb6e5f428c281682 (patch)
tree8846c6e454bc57d0b02349cca096e91bbe03c0c1 /_drafts/beginners-guide-sourcehut.md
parentdf433722c963c5c2ef44c5ada9f7b0912841f6d7 (diff)
Initial pass of minor styling updates, post about Sourcehut
Diffstat (limited to '_drafts/beginners-guide-sourcehut.md')
-rw-r--r--_drafts/beginners-guide-sourcehut.md83
1 files changed, 0 insertions, 83 deletions
diff --git a/_drafts/beginners-guide-sourcehut.md b/_drafts/beginners-guide-sourcehut.md
deleted file mode 100644
index c859c9a..0000000
--- a/_drafts/beginners-guide-sourcehut.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# Git Your Freedom Back: A Beginner's Guide to Sourcehut
-{:.no_toc}
-
-2025-01-20
-
-This article (or guide) is targeted towards users and contributors who are currently hosting their git repositories through GitHub. The goal of this post is to convince developers to move away from GitHub altogether. I will breakdown each of GitHub's core features and provide details on Sourcehut's alternative approach for each of these. Hopefully by the end of this guide developers will try Sourcehut or, at the very least, begin to question *why* they are still using GitHub.
-
-> **Note:** Clearly the most "free" git solution would be hosting your own git server. Self-hosting is a great idea and you should do so if you have the means. That being said, this article is focused on Sourcehut since most users do not have the time to manage both their projects **and** maintain a self-hosted instance.
-
-## Before We Begin
-{:.no_toc}
-
-It is important to make this clear: I am in *no way* affiliated with Sourcehut, nor have I been approached to write this guide. I'm simply a happy Sourcehut user who wants to see the community thrive!
-
-You'll also need to approach this guide with an open-mind. If you start off angry or feel like this is an attack on you for using (and maybe even enjoying!) GitHub, then you should come back once you're in a better *headspace*. This is merely a detailed guide on how to achieve a solid set of feature parity between GitHub and Sourcehut.
-
-Alright, enough talk. Let's get into it!
-
-## Table of Contents
-{:.no_toc}
-
-* toc
-{:toc}
-
-## Why GitHub Isn't Great
-
-### 1. Microsoft Ownership and Data Privacy
-
-GitHub is owned by Microsoft, a company known for aggressive data collection practices. This should raise concerns to most developers about their privacy and how it's handled.
-
-### 2. Telemetry and Tracking
-
-GitHub tracks user behavior through telemetry data, including interactions on the platform. Not to mention, most developers tend to use VS Code which sends additional telemetry (unless using the "open source" variation).
-
-### 3. Proprietary Nature
-
-GitHub is a proprietary platform, limiting user control over their data and infrastructure compared to self-hosted or open-source alternatives. If you can't see it - you shouldn't trust it.
-
-### 4. Copilot and Code Scraping
-
-The **BIG** one. GitHub Copilot uses publicly available code repositories to train its AI. This raises a lot of concerns about copyright infringement and unauthorized use of user content. Additonally, having Copilot default as an opt-out feature is very shady.
-
-### 5. Geopolitical Censorship
-
-GitHub has complied with government requests for content takedowns and blocked users in certain countries (e.g., Iran, Syria) due to U.S. trade sanctions.
-
-> We are in the process of moving SourceHut to the European Union, and have incorporated in the Netherlands. Consequently, the terms have been updated to clarify that users are required to comply with Dutch law in addition to US law. The requirement to comply with US law will be removed in a future update after we close the US entity. [Source](https://sourcehut.org/blog/2022-10-31-tos-update-cryptocurrency/)
-
-### 6. Centralization Risk
-
-GitHub represents a centralization of the open-source ecosystem, which goes against the decentralized ethos of open-source software. This feels at odds with those publishing *open source projects* on a closed platform...
-
-### 7. Dependency on Proprietary Features
-
-Features like GitHub Actions, Copilot, and Codespaces create vendor lock-in, making it harder for users to migrate to alternatives. (Hence the existence of this article)
-
-### 8. Lack of Transparency
-
-GitHub's decision-making processes, especially regarding policy changes and feature implementations, lack sufficient community involvement and transparency. It's difficult to trust or depend on policies that can change at any time without notice given to the community.
-
-## GitHub's Core Features
-
-- Issues (Tickets)
-- Pull Requests
-- Actions
-- Pages
-- Wiki
-
-## Sourcehut's Alternatives
-
-### Pull Requests &rarr; Patches
-
-Lorem ipsum dolor sit, amet consectetur adipisicing elit. Maiores blanditiis consequatur possimus reprehenderit, ratione architecto magnam officia. Quos culpa vel eligendi molestias, enim aperiam fugit impedit labore at, nam autem.
-
-### Actions &rarr; Builds
-
-### Issues &rarr; TODOs
-
-### Pages &rarr; Pages
-
-### Wiki &rarr; Wiki
-
-## Why Not Use...? \ No newline at end of file