Hi folks,
Last year, I spent several months getting the LibreWolf web
browser packaged, reviewed, and contributed to Guix. I’m happy to
have done so, and glad that it’s proved useful to others. One of
the concerns raised as I was going through that process was
responsibility for ongoing maintenance. I offered to take that
on, and have followed through, continuing to contribute patches
which improve the package and update it as new upstream releases
occur -- which is very frequently. Unfortunately, much of this
work is wasted, as the patches remain mired in the review backlog.
The package is now three major version out of date and suffers
from numerous CVEs. The initial patch to update the version to
127.x was submitted on June 29th; updated to 128.x on July 17th;
and I’ll be sending the patch updating it to 129.x later today,
after I’ve finished building and testing it.
I’m stuck in an impossible situation. I can’t apply for committer
access until I have more accepted contributions, but can’t build
those contributions unless my patches are reviewed. It’s
frustrating and demoralizing.
Are there, perhaps, one or two committers who’d be willing to work
more closely with me on LibreWolf on an ongoing basis? I’m not
asking for help doing the work of maintaining the browser itself,
which I remain committed to doing. I’m purely looking to
consitently get timely feedback and review, because the normal
process for contributions cannot reliably provide it.
A second, and smaller question, is: is there a mechanism to direct
others’ contributions to LibreWolf to me for review, without
subscribing to every patch sent to Guix? I have seen some
patches, and participated, but I have to go look for those, and
it’d be more convenient if they were directed to me in the first
place.
Thanks,
— Ian
- Request for assistance maintaining LibreWolf Ian Eure
-
