My phone number is listed on my home page. Please give me a call.
I agree with some of what you say—one caveat is that you're still on the hook, for example, for finding out which GitHub URL/repo maps to the project you want to contribute to. In practice, this is roughly on par with…
It's literally not my stance. And I've literally said that it's not my stance—in a comment (that should have never been necessary to begin with) meant to remove all doubt. And you know this. To continue saying otherwise…
I only counted opening a pull request as a single operation to begin with.
> If you contribute many times to the same repo, you only have to fork once. If you do a lot of drive-by contributions, you'll end up forking a lot of repositories. That doesn't contradict anything I've written here, or…
I'm not going to be strawmanned for the third time in this conversation. I didn't say it wasn't GitHub/GitLab/gerrit/reviewboard/etc and not a mailing list. I said it's not a mailing list. This message board is a…
I feel like I'm in bizarro world here. I know that these things have to be done. That should be clear. Didn't I make it clear, in my rundown near the root of this conversation, that I'm aware of the existence of these…
Buddy, the entire premise here is user "Monotonic" telling me that configuring remotes is unnecessary and that that in fact he or she just pushes to origin. Don't jump in to the middle of the conversation here and then…
Yes, exactly. Literally anything that has an upload button in the bugtracker for you attach your patch that fixes the bug.
> you can almost always push to origin Why am I having to repeat myself here? You can never push to origin unless it's your own project or your team's project. > It's a constant cost in the same way that looking up…
You can't push to origin unless it's your own project or your team's. We're talking about PR-based workflows. > Adding a remote is generally a one-time cost It's not a constant cost, unless you're saying you only ever…
What? You get to imagine some bad argument that would make it most convenient for you, and then demand that I defend that argument, as if it were one that I wanted to make? This is what I'm responsible for? Dealing with…
Everyone is trying to get me to defend mailing lists. I have no idea why. I haven't said anything about them. In fact, I hate mailing lists.
> You might like the mailing list Wrong. I fucking hate mailing lists. > You _tried_ to make it look like using GitHub.com is somehow... complicated. Please actually point out how the GitHub workflow can be even more…
I'm mystified about what's going on right now. Both versions involve clicking. Both versions involve command-line steps. The difference is that the GitHub version requires more of both, needlessly. That's the point of…
Please explain how you got there, because I'm at a loss. Both examples involve using the CLI. The GitHub version I ran through actually includes more CLI steps. How could that possibly have been my intention?
What makes either of those things harder than what you have to do to use github.com?
Let me ask, do you think that the content of my message reduces to "graphical user interfaces are harder to use than CLI"?
"Easy" like: git diff master..bugfix > bugfix.patch # or `format-patch` # now attach/upload bugfix.patch Instead of: # make sure you click around github.com to create third fork git remote add unnecessary-third-fork…
This is exactly right. People can pretty easily make their own lunch, and yet every day there are millions of transactions involving people forking over, say, $8 for an overpriced and overspiced pasta dish. Programmers…
Completely separate from the submission of this link: I've been working on triplescripts.org, and I have plans to dive into Gnome and GJS, with the goal being to highlight GJS as a potential target for the system layer.…
Related: https://news.ycombinator.com/item?id=15725942
My phone number is listed on my home page. Please give me a call.
I agree with some of what you say—one caveat is that you're still on the hook, for example, for finding out which GitHub URL/repo maps to the project you want to contribute to. In practice, this is roughly on par with…
It's literally not my stance. And I've literally said that it's not my stance—in a comment (that should have never been necessary to begin with) meant to remove all doubt. And you know this. To continue saying otherwise…
I only counted opening a pull request as a single operation to begin with.
> If you contribute many times to the same repo, you only have to fork once. If you do a lot of drive-by contributions, you'll end up forking a lot of repositories. That doesn't contradict anything I've written here, or…
I'm not going to be strawmanned for the third time in this conversation. I didn't say it wasn't GitHub/GitLab/gerrit/reviewboard/etc and not a mailing list. I said it's not a mailing list. This message board is a…
I feel like I'm in bizarro world here. I know that these things have to be done. That should be clear. Didn't I make it clear, in my rundown near the root of this conversation, that I'm aware of the existence of these…
Buddy, the entire premise here is user "Monotonic" telling me that configuring remotes is unnecessary and that that in fact he or she just pushes to origin. Don't jump in to the middle of the conversation here and then…
Yes, exactly. Literally anything that has an upload button in the bugtracker for you attach your patch that fixes the bug.
> you can almost always push to origin Why am I having to repeat myself here? You can never push to origin unless it's your own project or your team's project. > It's a constant cost in the same way that looking up…
You can't push to origin unless it's your own project or your team's. We're talking about PR-based workflows. > Adding a remote is generally a one-time cost It's not a constant cost, unless you're saying you only ever…
What? You get to imagine some bad argument that would make it most convenient for you, and then demand that I defend that argument, as if it were one that I wanted to make? This is what I'm responsible for? Dealing with…
Everyone is trying to get me to defend mailing lists. I have no idea why. I haven't said anything about them. In fact, I hate mailing lists.
> You might like the mailing list Wrong. I fucking hate mailing lists. > You _tried_ to make it look like using GitHub.com is somehow... complicated. Please actually point out how the GitHub workflow can be even more…
I'm mystified about what's going on right now. Both versions involve clicking. Both versions involve command-line steps. The difference is that the GitHub version requires more of both, needlessly. That's the point of…
Please explain how you got there, because I'm at a loss. Both examples involve using the CLI. The GitHub version I ran through actually includes more CLI steps. How could that possibly have been my intention?
What makes either of those things harder than what you have to do to use github.com?
Let me ask, do you think that the content of my message reduces to "graphical user interfaces are harder to use than CLI"?
"Easy" like: git diff master..bugfix > bugfix.patch # or `format-patch` # now attach/upload bugfix.patch Instead of: # make sure you click around github.com to create third fork git remote add unnecessary-third-fork…
This is exactly right. People can pretty easily make their own lunch, and yet every day there are millions of transactions involving people forking over, say, $8 for an overpriced and overspiced pasta dish. Programmers…
Completely separate from the submission of this link: I've been working on triplescripts.org, and I have plans to dive into Gnome and GJS, with the goal being to highlight GJS as a potential target for the system layer.…
Related: https://news.ycombinator.com/item?id=15725942