186
submitted 2 weeks ago* (last edited 2 weeks ago) by neme@lemm.ee to c/firefox@lemmy.ml
top 39 comments
sorted by: hot top controversial new old
[-] Dirk@lemmy.ml 72 points 2 weeks ago

Sad to see they only use MS GitHub instead of selfhosting something like GitLab. Just another vendor lock-in.

[-] shnizmuffin@lemmy.inbutts.lol 75 points 2 weeks ago

We will continue to use Bugzilla, moz-phab, Phabricator, and Lando.

Although we'll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time.

The cool thing about distributed version control is that it's distributed. It sounds like GitHub will just be a public remote, rather than the place where active development happens.

[-] Rednax@lemmy.world 24 points 2 weeks ago

Since they will not use Github for Pull Requests, bug tracking, or any other bonus feature on top of git, I have to disagree. It would be super easy to change the host of their git repo.

[-] cmhe@lemmy.world -4 points 2 weeks ago* (last edited 2 weeks ago)

Depends a bit on what the default cloning url will be. If the domain is in control of mozilla, which forwards it to github, then fine, if most people start using the github url, then it is still a vendor lock in, because many people and projects will use it, and that is not so easy to move away.

Update: To the people down-voting my comment, I would love to hear why you either disagree with me, or find that my that my contribution to this discussion is worthless.

The upstream URL of a project or repo is important, because it will be used in other projects, like in build scripts for fetching the sources. If a projects changes that URL in the future, and the old URL is no longer available/functional, all those scripts need to be changed and the old versions of these scripts do not work anymore out of the box.

If the project owns the URL, then can add redirect rules, that might help alleviate some of these issues. I don't think github allows projects that move away from it to do that. So this is a sort of vendor lock-in. The project needs to maintain the repo on github, because they want to break the internet as little as possible.

[-] kill_dash_nine@lemm.ee 22 points 2 weeks ago

Honest question - is GitLab really that different of a vendor lock-in over GitHub?

[-] 4am@lemm.ee 36 points 2 weeks ago

Gitlab can be self-hosted. GitHub is a cloud-only service.

So they could do git.mozilla.com and it would be their own instance of git, on their own hardware (or, probably, from their own AWS account). They control it entirely.

[-] jayknight@lemmy.ml 14 points 2 weeks ago

They did host a git server at git.mozilla.org, but took it down years ago.

https://bugzilla.mozilla.org/show_bug.cgi?id=1277297

[-] ShortN0te@lemmy.ml 8 points 2 weeks ago

And you need a team managing it. I doubt that they have not considered it.

[-] pivot_root@lemmy.world 2 points 2 weeks ago

You can self-host GitHub. It takes around 32 GB of memory, however.

[-] PlexSheep@infosec.pub 1 points 2 weeks ago
[-] pivot_root@lemmy.world 1 points 2 weeks ago

If you can find the download for GitHub Enterprise, Ruby Concealer is little more than an XOR cipher. Make of that what you will.

[-] Dirk@lemmy.ml 10 points 2 weeks ago

It absolutely is. Yes. You can run and maintain it on an own server and it is open core (yeah 😥) using the MIT license - unlike GitHub where you have to rely 100% on the goodwill of Microsoft and everything is closed and locked behind a TOS.

[-] Lemzlez@lemmy.world 2 points 2 weeks ago

So why not use forejo, which is completely open source?

If your criticism is MS pulling the plug, then Gitlab pulling a Redis/Hashicorp move and re-licensing their core should also be a concern

[-] Dirk@lemmy.ml 2 points 2 weeks ago

So why not use forejo, which is completely open source?

Absolutely! I’d always go the Forgejo route!

The thing is: I don’t see Firefox being hosted with Forgejo. The code base and amount of data might be way too massive. I see Forgejo as a forge for smaller projects.

[-] Feyd@programming.dev 2 points 2 weeks ago

Is there a reason you think Forgejo is only for smaller projects?

[-] Dirk@lemmy.ml 2 points 2 weeks ago

I've never seen larger projects like Firefox hosted with Forgejo.

[-] Feyd@programming.dev 2 points 2 weeks ago

Probably because it has only existed for 2 years

[-] ScreaminOctopus@sh.itjust.works 1 points 2 weeks ago

Gitlab's AGPL so I don't think there's anything stopping you from moving to a self managed instance.

[-] ShortN0te@lemmy.ml 6 points 2 weeks ago

No Gitlab is not AGPL, it is partly MIT and the corporate branch is under a proprietary license

[-] Dirk@lemmy.ml 2 points 2 weeks ago

Still better than a fully closed, 100% proprietary, cloud-only Microsoft service.

[-] slazer2au@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago)

~~Where do they mention GH? They only mention git in the post.~~

nevermind

[-] Ephera@lemmy.ml 3 points 2 weeks ago

Although we'll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time

[-] slazer2au@lemmy.world 2 points 2 weeks ago

I read that thing 3 times, how did I miss that?

[-] fossphi@lemm.ee 35 points 2 weeks ago

Damn. Wow, it seems like Mozilla is getting more fired up lately. They are also actively communicating (recent couple of AMAs) and listening to their users (through Mozilla connect and working on much requested features)!

[-] boredsquirrel@slrpnk.net 6 points 2 weeks ago

They plan on doing that change since over a year lol

And their build docs are incredibly confusing, I have no idea how distro packagers can do this.

I built Firefox from source for a while, and it just broke after a while.

[-] sugar_in_your_tea@sh.itjust.works 3 points 2 weeks ago

I'm guessing someone figured it out once, and everyone just copies from them...

[-] boredsquirrel@slrpnk.net 2 points 2 weeks ago

I mean they have some form of docs, and I got it to build. But hell even installing mercurial is totally weird.

[-] boredsquirrel@slrpnk.net 2 points 2 weeks ago

Btw, you can see the build flags your distro uses from within FF, I think it is about:build

[-] Deebster@programming.dev 29 points 2 weeks ago

So they're switching from using both Mercurial and Git to just Git... How did they end up using both? Was it just that each had its supporters so they just compromised and made everyone use both?

[-] mke@lemmy.world 22 points 2 weeks ago

If you have a bit of time to spare, see this great article for a some history on Mozilla and version control.

[-] pedroapero@lemmy.ml 3 points 2 weeks ago

This is very detailed 😆 I would have appreciated going for Codeberg too. This is not so bad as used just for hosting the repo, a future migration away from GH would be a breeze.

[-] Asudox@lemmy.world 5 points 2 weeks ago

They could have self hosted a Forgejo instance but they really went with MS GitHub. Kind of sad.

[-] fmstrat@lemmy.nowsci.com 2 points 2 weeks ago

I just wish they'd put their mobile releases on a standard release page. I can't use Obtainium with their current GitHub mirror because it's always out of date from the Play Store.

[-] mke@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago)

Anyone know if Mozilla ever made a statement on the state of MS's LLM training on Github data? I'm curious if they don't care about having Firefox be part of the dataset or if they just think the benefits of the platform outweigh that.

[-] nitefox@sh.itjust.works 1 points 2 weeks ago

Pretty sure it’s possible to opt out

this post was submitted on 14 Jun 2024
186 points (99.5% liked)

Firefox

16767 readers
19 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS