This has been in the works since April: github.com/mono/mono/issues/21

I'm not explicitly mentioned in the post, but effectively the maintainer duties for the Mono project now fall on me. It sort of worked out that Wine Mono (which I maintain) became the primary user of Mono that hadn't moved to modern .NET, with the other common use case being winforms on Linux. I might be the only person left who cares enough and has the generalist knowledge to muddle through.

It was just pointed out to me: keeping Mono maintained is important for preservation. .NET Framework images can't always be recompiled. That's most obvious with Wine, but sometimes upstream Mono is used for that too.

Follow

@voltagex There's nothing for Mono specifically, but Winehq accepts donations through SFC: winehq.org/donate

@madewokherd Just hope you personally are doing okay with this shift and this ongoing responsibility.

@voltagex Thankfully CodeWeavers is supporting me in this, it wouldn't be possible otherwise.

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!