Earlier quoted context omitted.
Lucky for us GitHub unlike Facebook don't rely on selling advertisments to make revenue. Plus git is decentralised. You can migrate your entire code anywhere you want. As far as issues are concerned I am pretty sure competitors like GitLab supports exporting them via GitHubs awesome API. It's not as bad as make you sound it. Things could have been much more worse.
I can migrate my code, but not all my consumers which use "github.com/my/package" as the import qualifiers all over the place.
Apache Software Foundation joins GitHub open source community
161–170 of 255 posts
Re: Apache Software Foundation joins GitHub open source community
#162Earlier quoted context omitted.
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 intend to contribute to one project ever. It's a fixed cost that you will pay N times, where N is the number of projects you contribute to.
You do push to origin in a PR-based workflow. The origin you push to is your fork of the project. Fork, push, pull request.
1. https://news.ycombinator.com/item?id=19779664
I'm going to skip ahead here. You're going to replace the `add unnecessary-third-fork` command with `set-url origin $THIRDFORK`. Either that, or you swap for a `git clone $THIRDFORK` so "origin" is set as a result of the clone.
How many steps do you need to eliminate before you can match the cost first sequence (2 steps)? How many steps does your advice eliminate? What are the total number of steps involved in the GitHub approach? I'll wait for your answer this time.
Re: Apache Software Foundation joins GitHub open source community
#163Earlier quoted context omitted.
"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 $THIRDFORK git push unnecessary-third-fork bugfix firefox $THIRDFORK # now click around to file a PR # now wait for your PR to be merged # now click around on github.com to delete $THIRDFORK # ... unless…
You can create a pr with the open source "hub" tool with a single command.
Re: Apache Software Foundation joins GitHub open source community
#164Earlier quoted context omitted.
I'm kind of cynical about this sort of thing and I don't think the hosting really changes the quality of contributions. The amount, maybe, but you get a lot of crappy drive-bys that are about one particular but very enthusiastic person's pet peeves, which probably don't affect the wider userbase. The drive-bys require a lot of work to integrate for relatively little profit. Mediagoblin is dying not so much because it…
> basically there are other things that got ActivityPub before it and could replace it (Pixelfed, Mastodon, Write Freely). Nobody really wants to work on Mediagoblin now because the alternatives are pretty much all better. Uh, maybe, except that none of the things you list actually do anything close to the core promise of MediaGoblin. MediaGoblin was going to be the libre Flickr/YouTube replacer. Nothing focusing on…
Re: Apache Software Foundation joins GitHub open source community
#165Earlier quoted context omitted.
It's not a direct consequence of anything that was said. It's a possible implication - in the conversational sense of implication, not the logical sense - but those get to be disclaimed.
His stance is literally that using a GUI is harder. That isn't a consequence, it's his core position.
To continue saying otherwise (explicitly, even) is a case of outright intellectual dishonesty.
Re: Apache Software Foundation joins GitHub open source community
#166Earlier quoted context omitted.
> Does it matter that GitHub themselves is not open source? That's for Apache to decide, but consider: Git itself was written, by Linus Torvalds, because Linux (the kernel) was using non-open source version control at the time called BitKeeper, and the non-open source nature of it was causing increasing problems in the Linux developer community, both ideological and eventually practical problems too, caused by the li…
"Ideological and eventual practical problems too" is way too general. The very specific flash-point was Linus throwing an unjustified hissy-fit defending Larry McVoy of BitKeeper being difficult about Andrew Tridgel (Tridge of Samba fame) "reverse engineering" the data traffic of Bitkeeper for inter-operability (really just sniffing client packets with wireshark or something). Whether the name "git" pertains to Tridg…
I was there, and I was told in private mail by the author of BitKeeper that I did not have permission to use it, because of my work on respository analysis software that looked like it would get too close for comfort.
That's without any reverse engineering. I never used BitKeeper, or connected to the server, or read the infamous "help" text.
It meant I couldn't participate in kernel development in the same way as most folks.
I wasn't the only one, and that's what I mean by practical problems, not just ideological.
Re: Apache Software Foundation joins GitHub open source community
#167Apparently, one of the big motivating reasons for this was "cost". > The foundation’s 2018 five-year strategic plan noted that infrastructure services account for more than 80 percent of the total ASF expense budget, adding: “Increasingly, project communities have infrastructure requirements that strain the capabilities of the ASF.” > The report noted that, given burgeoning costs, encouraging the use of more external…
May I ask why? Them moving doesn't look like an issue to me at least.
Re: Apache Software Foundation joins GitHub open source community
#168Earlier quoted context omitted.
I think the comment meant that git took ideas from Mercurial rather than BK taking ideas from Mercurial.
Git start before mercurial.
They were both released extremely close together, and I don't remember why I associate Mercurial ideas as being something Git learned from. Maybe I'm wrong about it.
Re: Apache Software Foundation joins GitHub open source community
#169For many years now, it's felt like Apache software foundation is where projects go to die. It's a shame its taken so long, but I'm glad to see this news - it's pretty much guaranteed to increase participation in Apache projects.
What do you mean to die? Projects like Kafka, Airflow and Spark are widely used today and the teams are constantly releasing new features.
Re: Apache Software Foundation joins GitHub open source community
#170Earlier quoted context omitted.
I guess gitlab is the same. The important flow is that there's a very easy way to fork and send a pull/merge request.
"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 $THIRDFORK git push unnecessary-third-fork bugfix firefox $THIRDFORK # now click around to file a PR # now wait for your PR to be merged # now click around on github.com to delete $THIRDFORK # ... unless…
As much as I hate centralization, especially when the central entity is a for-profit corporation running closed software, often that ends up giving you a standardized experience that makes things easier. "Easier" doesn't have to mean fewer steps; I agree that the GitHub workflow you describe isn't simpler, but if you've done it a few times, it's mechanical and you don't need to think about it. GH even provides a command-line tool[0] that lets you avoid most of the click-around-on-website steps.