Re: Request for assistance maintaining LibreWolf

[Ian Eure <ian@retrospec.tv>]

Hi Ludo’,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Tomas, Ian, and all,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> Ian Eure <ian@retrospec.tv> writes:
>>
>>>>
>>>> I believe the usual way of doing something like this is via 
>>>> teams (see
>>>> ./etc/teams.scm ).
>>>>
>>>
>>> I’m not sure whether/how well this mechanism works for 
>>> non-committers.
>>
>> I believe it should.  AFAIK pretty much all it does is to 
>> automatically
>> add the team members onto CC list when running `git 
>> send-email'.
>
> Yes, it works whether or not one has commit rights, and I agree 
> that it
> could be helpful here.
>

Sounds good -- I’ll send in a patch to add myself.  I’ve run into 
a couple cases where patches got merged while I’ve had other 
patches open, and getting notified will help coordinate which 
stuff goes when.


>> 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.
>

This makes a lot of sense to me, and I think it would solve my 
immediate problem.  Would it make sense to set up a browser-team 
mailing list and etc/team.scm which notifies that of patches/bug 
reports sent on any of the browser packages?


> PS: I too have been a happy LibreWolf user for some time now, so 
> I join
>     others in thanking you for the great work!
>

I really appreciate hearing this, thank you for saying.

Thank,

  — Ian