Gitlab experiment status

Gabriel Ivăncescu gabrielopcode at
Fri Jun 3 09:28:17 CDT 2022

On 03/06/2022 02:50, Alex Henrie wrote:
> On Fri, May 27, 2022 at 12:03 PM Zebediah Figura
> <zfigura at> wrote:
>> On 5/27/22 10:46, Rémi Bernon wrote:
>>> On 5/27/22 17:30, Zebediah Figura (she/her) wrote:
>>>> On 5/27/22 07:34, Jacek Caban wrote:
>>>>> * I think that a mailing list dominated by a bot does not give an
>>>>> impression welcoming for general discussion. If we're moving forward
>>>>> with this, I think we should move Gitlab bridge to a separated
>>>>> mailing list. We had wine-patches in the past (although in this case
>>>>> it would contain review comments as well).
>>>> If our intent is to switch to gitlab because mailing lists are too
>>>> difficult for people to work with, then it seems we shouldn't have any
>>>> discussion at all take place on a mailing list, otherwise it'll be
>>>> missed by the people who are only using gitlab. Not that I know of a
>>>> better way to have such discussion...
>>> Imho the mailing list still makes sense, for general Wine development
>>> discussion, though the volume may be much smaller than what we currently
>>> have.
>>> Maybe we don't currently have many discussion either because the mailing
>>> list is felt more as a place for patches, and that discussions are
>>> believed to happen elsewhere, or because discussions go more often
>>> unnoticed under the volume of patches.
>> I've seen this kind of thought floated several times, and I'm not sure I
>> understand the reasoning. What kind of discussions or replies are you
>> expecting to see that don't currently happen?
> This thread itself is an example: I didn't see it until today. GitLab
> allows me to subscribe to the patch discussions that I care about
> rather than getting the deafening torrent of every single message. So,
> for me, resurrecting the wine-patches list as the GitLab bridge while
> leaving process and architecture discussion on wine-devel would be a
> welcome change. Mailing lists also aren't very friendly when a
> newcomer wants to reply to a message that was sent before they were
> subscribed to the list, but GitLab allows newcomers to jump right in.
> -Alex

FWIW, I see you use gmail, so you can just use a filter to send all the 
mails coming to this list that have [PATCH] in Subject line to a 
different tag. Which is the same as having two different mailing lists 
and sending them to different tags (or even remove the mails with 
[PATCH] which is akin to not subscribing to wine-patches).

More information about the wine-devel mailing list