[arp242]

People forget things etc.

Should probably have just asked again, or sent a small one-line patch. It's "mention something on Slack" vs "creating a GitHub issue/PR"

[lazyasciiart]

Then you get stories like Greg in the linked mail thread, who emailed to check after not hearing anything and got told that now he'd been annoying and it would never be done.

[account42]

A story about a 17000 line patch with seemingly no discussion before dumping it on the kernel maintainers. Understandable that noone felt like reviewing it.

[samus]

Which sounds inefficient and exactly the sort of problem that doesn't happen with a Github issue/PR.

[BlueTemplar]

But Github, being a platform, is a nonstarter.

Have there been any recent popular developments on a similar workflow that is as robust as e-mail ?

[samus]

They "just" need to settle on a platform. GitLab sounds good and is used by a lot of important Open Source projects.

[BlueTemplar]

Did you miss the part where being a platform was most of the issue ?

I'm not sure how long GitLab can be trusted either, as well as git becoming a bit too synonymous with GitHub...

[arp242]

> exactly the sort of problem that doesn't happen with a Github issue/PR

What? PRs or issues being forgotten happens all the time, especially for large projects.

[samus]

It would still be easier to track the progress (or lack thereof) with a proper ticketing system.

[account42]

Yeah instead the issue will be auto-closed by some bot. Yay.