Hi,
Not sure if everyone is already aware of this, but see https://gitlab.gnome.org/GNOME/gtkmm/-/issues/110
"I will not continue forever with maintenance of gtkmm and other *mm modules. Unless someone else continues the work, glibmm, gtkmm and other modules will be abandoned in a near future."
Should we be worried?
Best regards,
Diederik
On Wed, 2022-03-30 at 12:01 +0200, Diederik van Lierop wrote:
Hi,
Not sure if everyone is already aware of this, but see https://gitlab.gnome.org/GNOME/gtkmm/-/issues/110
"I will not continue forever with maintenance of gtkmm and other *mm modules. Unless someone else continues the work, glibmm, gtkmm and other modules will be abandoned in a near future."
Should we be worried?
Gtkmm has been undermaintained for a while now. It's our part in the greater open source maintainability crisis that we're all currently having to think about.
As I've said before, /depending/ on volunteers is risky and forcing volunteers is immoral. If we were in a healthy ecosystem, we'd be able to make serious contributions of time and money to our most important upstreams if we actually want to have dependability. But we have our own resource problems too.
See also: cairo et al.
Specifically about gtkmm; I've always gotten the feeling that C++ is not as socially welcome in the gnome community. This is a personal opinion based on gruff interactions with their C programmers, but it feeds into how well cultivated a project's community is likely to be by it's parent org.
No solutions, I'm still thinking these problems through out loud.
Perhaps we can make a special request to the gnome foundation for material support for gtkmm?
Best Regards, Martin Owens
participants (2)
-
Diederik van Lierop
-
doctormo@gmail.com