3 ms·

Wait, are you saying email is reinventing the wheel that is GitLab etc.? I think your history might be a bit backward here. My advice is to develop your own pe

Wait, are you saying email is reinventing the wheel that is GitLab etc.? I think your history might be a bit backward here. My advice is to develop your own personal tools in such a way that you can handle all kinds of interactions with other developers and projects. It's pointless saying "I prefer this or that" when you probably don't get to make those decisions. Projects develop workflows and common tooling like forges for practical reasons. But you, as an individual, shouldn't be tied to any one of them. My point isn't at all about trying to switch projects from forges to email based workflows, it's merely saying that you can do things to improve your tools such that you can interact with those projects. If you find it difficult to work with a successful project with many contributors then you are the problem, not them.

sofixa 3y ago
> Wait, are you saying email is reinventing the wheel that is GitLab etc Bolting a million custom tools around email to force it to do something it was never meant to do is reinventing the wheel, yes. > Projects develop workflows and common tooling like forges for practical reasons. But you, as an individual, shouldn't be tied to any one of them. Yes, and very very few of them prefer arcane workflows such as patches over email. Some highly critical ones like the Linux kernel do, but the vast vast vast majority of products use well oiled machines like GitHub, GitLab, Gogs, Gitea, etc.