4 ms·

So changes get pushed immediately in their own fork but are they again pushed upstream for the general Firefox release? I would presume that many of the changes

So changes get pushed immediately in their own fork but are they again pushed upstream for the general Firefox release? I would presume that many of the changes that they would like to make to the project, while not high enough priority for the Mozilla team, would actually be beneficial to them.

emily37 15y ago
Mike Perry gave a talk in one of my classes today, and he mentioned that he would like to push changes upstream, and that Mozilla has expressed some interest in that as well. A lot of the TorButton features are also desirable private browsing mode features that haven't been implemented yet.
keeperofdakeys 15y ago
The Tor Browser bugs on the other hand are more directly usable by Firefox in its own Private Browsing Mode, which makes them more likely to merge quicker, and be maintained long-term. Also, because we are releasing our own Firefox-based browser, we will also have more control over experimenting with them and deploying these fixes to our users rapidly, as opposed to waiting for the next major Firefox release. This is from the article. Although these features may be beneficial for Firefox, they may not be a part of their priorities. By Tor making their own fork and doing all the hard work (designing, coding and testing), they can just give Mozilla some patches. This only leaves a bit of their own testing, maybe some marge conflicts, so that the Firefox devs don't need to do the design and initial coding. This means that both guys win.