Can I apply fenix-liberate.patch and license the resulting source under MPL?
This is somewhat related to #3 (closed).
I'm working on a fork of Fenix with some additional customizability features and a bit of a different product direction at https://github.com/interfect/fenix.
I want to get it into F-Droid, which means ripping out all the proprietary dependencies, and it looks like you've already done a fair amount of that work @relan with the fenix-liberate.patch file in this repo.
But I'm licensing out my fork of Fenix under MPL 2.0 still, and I don't think I can just merge an AGPL patch and keep the MPL 2.0 license.
Since I'm wanting to permanently apply the patch to (a fork of) the actual software it's meant to patch, rather than using it as part of a server-side build system, I don't think the special provisions of the AGPL would be very important in my use case.
Can I have your permission to apply the patch to my fork and license the result under MPL 2.0?