Gitlab experiment status
Rémi Bernon
rbernon at codeweavers.com
Fri May 27 10:46:01 CDT 2022
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.
Then I personally also don't think that the mailing list bridge is doing
a great job, and if we decide to use Gitlab as the primary platform I'd
also vote for using a different mailing list for the bridge, for people
willing to stick to it. (*)
(*) Actually, if we decide to adopt Gitlab as the primary development
platform, I think it'd be better if reviews were done on Gitlab
entirely, if we cannot find a way to better format mail replies, they
are hardly readable at the moment. Even replying to Gitlab builtin mail
notifications does a better job.
Cheers,
--
Rémi Bernon <rbernon at codeweavers.com>
More information about the wine-devel
mailing list