Live data from Hacker News

Mozilla Firefox – Official GitHub repo

github.com

371–380 of 481 posts

Re: Mozilla Firefox – Official GitHub repo

#371
post #59

Earlier quoted context omitted.

I find this comment really interesting, because NONE of my clients in the last 10 years of (self-) employment had even a single codebase on GitHub. I am contributing to a few open source projects on GitHub here and there though.

GitHub is not Git. Git is by far the most widely used VCS. The majority of code hosting services use it.

Yes, I am aware. I didn't claim anything else.

My clients don't use GitHub.

Most of my clients do use Git. (some use other VCS)

What made you think I thought differently?

Re: Mozilla Firefox – Official GitHub repo

#373

Earlier quoted context omitted.

Time will tell. I would love to be wrong.

You didn't even provide any actual context making it impossible to argue with you. HN should have better conversations than shallow dismissals (according to the guidelines).

I sorta agree with this comment, but would rephrase that to "unclear what direction is being referred to".

(Arguing may come next, but first comes communicating.)

Re: Mozilla Firefox – Official GitHub repo

#374
post #105

Earlier quoted context omitted.

Can you expand on that? I’m probably younger but I can’t imagine a more comfortable way to review code.

Pull requests are great, but the typical github UI isn't necessarily the best way to review code. It's often useful. But sometimes you want to use other tools, like firing up your editor to explore.

No, they're terrible. We should be reviewing stacks of commits not branches

Re: Mozilla Firefox – Official GitHub repo

#375
post #53

Earlier quoted context omitted.

Git should have issue support or something like it as a convention but pull requests are an abomination that we are stuck with. No thank you.

Can you expand on that? I’m probably younger but I can’t imagine a more comfortable way to review code.

Phabricator.

Re: Mozilla Firefox – Official GitHub repo

#377

(I work at Mozilla, but not on the VCS tooling, or this transition) To give a bit of additional context here, since the link doesn't have any: The Firefox code has indeed recently moved from having its canonical home on mercurial at hg.mozilla.org to GitHub. This only affects the code; bugzilla is still being used for issue tracking, phabricator for code review and landing, and our taskcluster system for CI. In the s…

Will GeckoView and Mozilla Android Components be on GitHub too?

Re: Mozilla Firefox – Official GitHub repo

#378

Earlier quoted context omitted.

> This only affects the code; bugzilla is still being used for issue tracking Grim. The best reason to be using github at all is to maximize the portion of your users who are comfortable submitting bug reports, as they already have an account and are familiar with how the platform works (due to network effects.) Projects which host code on github but chose not to take bug reports there are effectively gate keeping bu…

If you really want bug reports just make it a single form without the need to create an account. Github, Gitlab, etc., is a wall for 99% of web browser users.

99% of browser users shouldn't file bug reports. I'd rather wait for a high-quality report than drown in low-quality reports.

Re: Mozilla Firefox – Official GitHub repo

#379
post #100

Earlier quoted context omitted.

It might feel like that now, but in 2011 github was just one of a bunch of code forges and at the time they were all similar in quality. Gitorious was chosen for the meego/maemo team for example.

In those days GitHub probably had more eyes on it in a day then Gitorious did in a quarter. And I am one of the people saddened by the convergence on a single platform. But you can't deny, it's always been pretty great.

> And I am one of the people saddened by the convergence on a single platform.

Hardly surprising, though, social networks are prone to centralization (due to network effect), and GitHub & its competitors (anything that offers git repos + issue tracking + fork-ability, really) are social networks.

Also, GitHub offering private repos for free right after they got acquired by Microsoft helped a lot. A lot of people, myself included, were using gitlab.com for private repos at that time

Re: Mozilla Firefox – Official GitHub repo

#380

(I work at Mozilla, but not on the VCS tooling, or this transition) To give a bit of additional context here, since the link doesn't have any: The Firefox code has indeed recently moved from having its canonical home on mercurial at hg.mozilla.org to GitHub. This only affects the code; bugzilla is still being used for issue tracking, phabricator for code review and landing, and our taskcluster system for CI. In the s…

Given that Phabricator has been discontinued, are there any plans to replace that with something else? Phorge perhaps?
Post reply on HN