In theory, sure, but the reality is that "development activity" revolves around "codebase". Plenty of projects have separate bug tracker, source code control and CI system. Most people likely prefer GitHub's all-in-one solution, especially for small-medium open source projects.
And do we not see how terrible this is as a result? Hitching your tent to corporations, especially American corporations, is always an exercise in misery.
I recently had to rebuild a jira frontend from scratch just so a single jira tab didn't take down my 8gb MacBook. Support only the subset of features I actually use and it's great. Makes me hate jira even more.
I disagree. The integrated workflow of actions, issues, code review and source control is a huge productivity win. There’s a reason people chase a “single pane of glass”.
A website where one views and interacts with all of these things does not necessitate that all of these things run on the same system. Since this most recent GitHub outage, I'm looking into modularizing my git server, issues, and actions; there's no reason why one going down should bring down all the others.
In theory, sure, but the reality is that "development activity" revolves around "codebase". Plenty of projects have separate bug tracker, source code control and CI system. Most people likely prefer GitHub's all-in-one solution, especially for small-medium open source projects.
They've already separated the wiki's version control, why not CI? And the issues/discussions are just vendor lock-in wrapped in a shiny UI.
And do we not see how terrible this is as a result? Hitching your tent to corporations, especially American corporations, is always an exercise in misery.
*Atlassian from Australia has joined the chat*
Mostly they joined the chat to show you what real misery is. I tried Jira and they couldn't even handle simple billing without screwing it up. Ugh
I recently had to rebuild a jira frontend from scratch just so a single jira tab didn't take down my 8gb MacBook. Support only the subset of features I actually use and it's great. Makes me hate jira even more.
Thankfully, there is a Jira CLI tool[1].
[1] https://github.com/ankitpokhrel/jira-cli/
I'm not saying it's an objectively "good" solution, just how damn smooth the experience is.
[flagged]
I disagree. The integrated workflow of actions, issues, code review and source control is a huge productivity win. There’s a reason people chase a “single pane of glass”.
A website where one views and interacts with all of these things does not necessitate that all of these things run on the same system. Since this most recent GitHub outage, I'm looking into modularizing my git server, issues, and actions; there's no reason why one going down should bring down all the others.