Earlier quoted context omitted.
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.)
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.
Mozilla Firefox – Official GitHub repo
61–70 of 481 posts
Re: Mozilla Firefox – Official GitHub repo
#62Earlier quoted context omitted.
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
#63Pretty 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.)
Re: Mozilla Firefox – Official GitHub repo
#64Pretty 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.
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…
Re: Mozilla Firefox – Official GitHub repo
#65Earlier quoted context omitted.
If you had checked you would've seen issues are not enabled. I assume they still use their Bugzilla
> If you had checked you would've seen issues are not enabled That was the point of the (obviously ill-received) joke.
Re: Mozilla Firefox – Official GitHub repo
#66Pretty 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.
People who are very insistent on distributed solutions never seem to understand that the economic, social and organizational reasons for division of labor, hierarchy and centralization didn't suddenly go away.
Re: Mozilla Firefox – Official GitHub repo
#67Earlier quoted context omitted.
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.)
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.
Re: Mozilla Firefox – Official GitHub repo
#68Great to see, but I wonder what lead to the decision of creating a new org instead of using github.com/mozilla
GitHub are terrible at this, because you can't have levels other than Org and Repository. And many things (SSO, visibility rules, common configs) are on the org level. Unfortunately often the cleaner option is to create a separate org, which is a pain to use (e.g. you log in to each separately, even if they share the same SSO, PATs have to be authorised on each one separately, etc). In Gitlab, you would have had one…
Re: Mozilla Firefox – Official GitHub repo
#69Pretty 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.
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…