Preface: I appreciate the sentiment, fuck Microsoft.
- Projects typically aren’t “hosted” on code repositories like GitHub.
- Because the underlying version control technology, git, is meant to be distributed - it’s super weird to draw that line in the sand. It’s like saying “show me TXT files written with SublimeText, I hate Notepad++!”
- I get that you might want to, like, judge a developer for using github? But, like… features are features. Build minutes are build minutes. If you fork a repo and use GitLab to manage it, does that make the project better?
- If it’s distributed through github, and there’s no push to move elsewhere by users and contributors, then it’s effectively hosted on/through github
- The analogy breaks down for collaborative projects, which is where the issues with github arise
- If their problem is with the project’s distribution method, presumably the answer is yes
If you want to contribute to a project developed on GitHub, you need to have a GitHub account. So it does matter.
Actually, you can send the diff patches by email/ pastebin/ gitlab/ etc. It’s up to the main developer to take your contribution seriously, given the level of annoyance you might be presenting. Same happens in the other direction, you can host your code on sourcehut, but many junior devs could be repelled by the old school ux.
I dont get how that works, you mail those lines with all those
+line +something -somethingAnd they can like transform that into git and have it work as an actual patch?
Yes, it’s called a diff and git was designed with exactly this workflow in mind because it’s how the Linux kernel has been developed for decades. GitHub is just a new fangled way to social network-ize the git workflow.
This website explains the process: https://git-send-email.io/
Thanks for being the last required part to push me to using sourcehut. I am already loving it.
