Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mozilla Firefox – Official GitHub repo

github.com

Post reply on HN
Print view View original

41–50 of 481 posts

Re: Mozilla Firefox – Official GitHub repo

#41

Post by enos_feedler »

littlestymaar wrote: post #35
SCdF wrote: post #26

Earlier quoted context omitted.

I get what you're saying, but tbf hosting on github doesn't (yet!) box you out of just moving back to that system. It's still just git. It's still distributed, in the sense that if github goes down you could still generate patches and email them around, and then push back to github when it's back. Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a story that is answered by dist…

> Everything surrounding code: issues, CICD, etc, is obviously another story That's what Github is though, it's not about the code itself it's about all your project management being on Github, and once you move it, moving out isn't realistic.

And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic. I think we should be grateful that the core underlying protocol for the most important data has the distributed properties we want. It's a lot more than we can say vs. lots of other platforms out there.

Re: Mozilla Firefox – Official GitHub repo

#42

Post by formerly_proven »

snickerbockers wrote: post #33
bandrami wrote: post #12

Pretty cool that Linus Torvalds invented a completely distributed version control system and 20 years later we all use it to store our code in a single place.

ironically hardly anybody outside of the linux kernel community uses it the way it was intended lol. Didn't all this start with Linus getting into a spat with the bitkeeper dev involving some sort of punitive measure as a response to somebody making a reverse-engineered FOSS client? I don't remember the details and I'm sure I have at least half of them wrong, but that's easily one of the most disastrous decisions in…

It would've made sense to change many defaults in git for "normal users" ages ago (git 2?) instead of keeping the kernel-workflow defaults.

Re: Mozilla Firefox – Official GitHub repo

#43

Post by mmis1000 »

IshKebab wrote: post #19
bandrami wrote: post #12

Pretty cool that Linus Torvalds invented a completely distributed version control system and 20 years later we all use it to store our code in a single place.

Plenty of people use Codeberg and Gitlab. And it's still distributed - I don't need to lock files and ask coworkers if I can work on them. Maybe if Git had native support for PRs and issues this wouldn't have happened. (And yes I'm aware of git send-email etc.)

I think it would be great if git have some kind of soft lock by default (like attach a text on some file without make it into actual commit). It could probably make peoples' live easier when you and teamates need to communicate what files you are changing thus reduce the chance of conflict.

Re: Mozilla Firefox – Official GitHub repo

#44

Post by gbil »

dtech wrote: post #16
rrr_oh_man wrote: post #9

[flagged]

If you had checked you would've seen issues are not enabled. I assume they still use their Bugzilla

and they moved anyway the android firefox issues from github to bugzilla some time ago, it would be quite "funny" moving them back to github now

Re: Mozilla Firefox – Official GitHub repo

#45

Post by SCdF »

littlestymaar wrote: post #35
SCdF wrote: post #26

Earlier quoted context omitted.

I get what you're saying, but tbf hosting on github doesn't (yet!) box you out of just moving back to that system. It's still just git. It's still distributed, in the sense that if github goes down you could still generate patches and email them around, and then push back to github when it's back. Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a story that is answered by dist…

> Everything surrounding code: issues, CICD, etc, is obviously another story That's what Github is though, it's not about the code itself it's about all your project management being on Github, and once you move it, moving out isn't realistic.

Right, but distributed git As Torvalds Intended™ doesn't solve those problems, so it's not related.

For the actual event we are commenting on, they have disabled all features other than code hosting and PRs.

Re: Mozilla Firefox – Official GitHub repo

#46

Post by kgeist »

joha4270 wrote: post #24
moralestapia wrote: post #17

Earlier quoted context omitted.

Care to explain?

If GitHub went down, how much would it impact the open source world? Sure, there would be local copies everywhere, but for a distribution version control system, it's pretty centralized at GitHub

If GitHub went down, the code would be fine (just announce a new official URL), but the main thing that would be lost is issues and pull requests. Maybe Git should add official support for issues and pull requests in its metadata to be fully decentralized.

Re: Mozilla Firefox – Official GitHub repo

#47

Post by rurban »

reddalo wrote: post #6

Why GitHub? If they truly cared about open-source they would've chosen something else, such as a self-hosted Forgejo [1], or its most common public instance Codeberg [2]. [1] https://forgejo.org/ [2] https://codeberg.org/

I maintain some project on all forges in parallel, even savannah. Savannah is even the default. But 99% of all reports and contributions are on the github mirror, 1% on savannah, 0% on gitlab and 0% on codeberg. Nobody cares about those islands.

issues are stored in git bug and automatically synced. Github is the only viable option, but you can keep the others as mirrors when github chooses to strike you.

Re: Mozilla Firefox – Official GitHub repo

#48

Post by mmis1000 »

ratatoskrt wrote: post #21
bandrami wrote: post #12

Pretty cool that Linus Torvalds invented a completely distributed version control system and 20 years later we all use it to store our code in a single place.

To be fair, Git itself is a bit of a pain, and GitHub's main achievement is/was to make it somewhat bearable.

In some sense, git is actually like advanced zip versioning system. A commit is literally just a snapshot of code base except it tell you what is the previous version of this version.

Also, git store the files in a smarter way so file size won't explode like zip versioning.

Re: Mozilla Firefox – Official GitHub repo

#49

Post by tigroferoce »

littlestymaar wrote: post #35
SCdF wrote: post #26

Earlier quoted context omitted.

I get what you're saying, but tbf hosting on github doesn't (yet!) box you out of just moving back to that system. It's still just git. It's still distributed, in the sense that if github goes down you could still generate patches and email them around, and then push back to github when it's back. Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a story that is answered by dist…

> Everything surrounding code: issues, CICD, etc, is obviously another story That's what Github is though, it's not about the code itself it's about all your project management being on Github, and once you move it, moving out isn't realistic.

GitHub is about the community. There are others alternatives, more in line with what Mozilla claim to be their view (I'm thinking to GitLab, for instance), but nothing gives you visibility like GitHub.

Sad to see that Mozilla is becoming less and less what they promised to be once Google funding are depleting.

Re: Mozilla Firefox – Official GitHub repo

#50

Post by groestl »

enos_feedler wrote: post #41
littlestymaar wrote: post #35

Earlier quoted context omitted.

> Everything surrounding code: issues, CICD, etc, is obviously another story That's what Github is though, it's not about the code itself it's about all your project management being on Github, and once you move it, moving out isn't realistic.

And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic. I think we should be grateful that the core underlying protocol for the most important data has the distributed properties we want. It's a lot more than we can say vs. lots of other platforms out there.

> And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic.

That's how we started out.

Post reply on HN