<<We still have a fair number of free slots for talks.>>
State of USB detection, the wiki intimates devices would need to be plugged in before wine starts. Is detection while wine is running in the roadmap and if so status?
Also, just an opinion, but I preferred it when patches had their own mailing list.... If you just want to monitor the wine development from time to time from the email digest, makes it hard to notice for instance WineConf amongst some verbose patch after patch. Possibly what maybe more constructive is only the mails with the excerpts of patches that are being commented on being present on the wine-devel list, this aids when following what is acceptable or not.
KK
On Wed, May 02, 2018 at 11:35:41AM +0100, KKing wrote:
Also, just an opinion, but I preferred it when patches had their own mailing list.... If you just want to monitor the wine development from time to time from the email digest, makes it hard to notice for instance WineConf amongst some verbose patch after patch. Possibly what maybe more constructive is only the mails with the excerpts of patches that are being commented on being present on the wine-devel list, this aids when following what is acceptable or not.
In the case of wineconf in particular, there is a separate mailing list where most of that discussion occurs:
https://www.winehq.org/mailman/listinfo/wineconf
It's mentioned on the WineConf2018 wiki page (but not the mailing lists page, apparently).
To your more general point, it's more convenient for wine devs to have one list, but I can see why it'd be annoying for observers and users. As a workaround, your mail client may be able to filter out mails with a Subject that start with "[PATCH".
Andrew