unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: "André Batista" <nandre@riseup.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Tomas Volf" <~@wolfsden.cz>,
	"Jonathan Brielmaier" <jonathan.brielmaier@web.de>,
	"Mark H Weaver" <mhw@netris.org>,
	guix-devel@gnu.org
Subject: Re: Request for assistance maintaining LibreWolf
Date: Wed, 28 Aug 2024 16:16:26 -0700	[thread overview]
Message-ID: <8734mo2pqa.fsf@meson> (raw)
In-Reply-To: <ZsdoVBIYgD0sskqi@andel>

Hi André,

André Batista <nandre@riseup.net> writes:

>> > At the same time it is not really meant as a general 
>> > notification
>> > system, so usefulness for you depends on whether some 
>> > committer will
>> > merge the commit adding librewolf team (with you in it).
>> 
>> Ian, what about teaming up with other Firefox derivative 
>> maintainers?
>> I’m thinking notably of André and Clément who’ve worked on Tor 
>> Browser
>> on Mullvad Browser, Mark H Weaver who’s been maintaining 
>> IceCat, and
>> perhaps Jonathan who’s been taking care of IceDove (Cc’d)?
>> 
>> Of course, each of these package is different but they’re in 
>> the same
>> area so it probably makes sense to share reviewing efforts 
>> here.
>
> I was reticent on this mainly because (i) I have never actually 
> used
> LibreWolf and I don't have a clear picture of it besides it 
> being a
> "Firefox + Arkenfox - Mozilla Branding" [1](?); (ii) I expect 
> that most
> of these security (aka urgent) patches will land on the same day 
> on a
> regular basis for all 4 browsers and given Mullvad and 
> TorBrowser
> sources will be late in the game, I'll probably not be able to 
> do such
> a timely (yet again, urgent) review, which could add to Ian's
> frustration, instead of relieving it; and (iii) AFAIUI, 
> LibreWolf moves
> at a faster pace, which adds to my concern of not being able to 
> keep up
> in the long run.
>
> That being said, given those patches have remained unreviewed 
> for weeks
> in a row, I guess I can at least help improve the current 
> situation and
> give commiters some more confidence that a given patch will not 
> break
> hell loose when commited and so I'm willing to help with these 
> reviews.
> However, I cannot promise to maintain it if/when Ian's lead 
> happens to
> go missing.
>

This sounds reasonable to me, and I would greatly appreciate any 
assistance that could be provided.  My hope is that with some 
closer working relationships with existing Guix folks and more 
contributions, I can apply for commit access and maintain 
LibreWolf autonomously.  Perhaps next year.


> One question in that regard: is there any difference between 
> reviewing
> through QA's web interface and sending mail commands to debbugs'
> control? Is any of them preferable? I'd rather use the mail 
> interface if
> that's enough.
>

There’s no major difference, whichever you prefer.  I think email 
is more likely to keep threads grouped.


> Cheers.
>
> 1. No disrespect meant to the project or its users, just my own
> current cluelessness exposed. I'll read the docs on it to 
> understand
> it better though.
>

None taken, and you’re on the right track.  LibreWolf ships 
several improvements combined into one package, including 
hardening the default preferences, disables the numerous 
anti-features that ship with Firefox (full page ads on update, 
Pocket, telemetry, DRM, etc).  They also don’t have the onerous 
trademark and logo requirements, which lets distrbutions ship with 
the upstream branding.  The combination of better defaults, 
relaxed branding requiements, and closely tracking upstream make 
it a very compelling choice, IMO.  I’ve been daily driving it for 
several years.

Thanks,

  — Ian



  parent reply	other threads:[~2024-08-28 23:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17 16:44 Request for assistance maintaining LibreWolf Ian Eure
2024-08-17 18:00 ` Sergio Pastor Pérez
2024-08-17 19:43   ` Ian Eure
2024-08-18  8:35   ` Christopher Baines
2024-08-18 16:50     ` Ian Eure
2024-08-19  1:53       ` Suhail Singh
2024-08-19  8:53       ` Christopher Baines
2024-08-19 23:14         ` Ian Eure
2024-09-12  1:01           ` Maxim Cournoyer
2024-08-19 17:01     ` Sergio Pastor Pérez
2024-08-18  8:37   ` Attila Lendvai
2024-08-18  9:07     ` Lars-Dominik Braun
2024-08-17 20:36 ` Ian Eure
2024-08-17 23:08 ` Suhail Singh
2024-08-18  4:07   ` Ian Eure
2024-08-18 21:17     ` Tomas Volf
2024-08-21 20:54       ` Ludovic Courtès
2024-08-22 15:00         ` Ian Eure
2024-08-28 20:48           ` Ludovic Courtès
2024-08-28 23:15             ` Ian Eure
2024-08-29  7:30               ` Tobias Geerinckx-Rice
2024-08-29 20:24                 ` [Browser-Team] " André Batista
2024-08-30 20:14                   ` Ludovic Courtès
2024-08-22 16:37         ` André Batista
2024-08-28 20:46           ` Ludovic Courtès
2024-08-30 20:18             ` Defining the role of teams Ludovic Courtès
2024-08-28 23:16           ` Ian Eure [this message]
     [not found] <mailman.5970.1723926982.21382.guix-devel@gnu.org>
2024-08-18  0:11 ` Request for assistance maintaining LibreWolf Andy Tai
2024-08-18  0:48   ` Ian Eure

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8734mo2pqa.fsf@meson \
    --to=ian@retrospec.tv \
    --cc=guix-devel@gnu.org \
    --cc=jonathan.brielmaier@web.de \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.org \
    --cc=nandre@riseup.net \
    --cc=~@wolfsden.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).