> Hello y'all, Hi again Artyom,
> I've noticed that Surf had no commits for the last year and my patch > was left unanswered by the maintainer(s?) Not that I complain—my > patch was a controversial PDF support one. My bad, I didn't even chime directly into the conversation, although we exchanged internally a bit on IRC, but I agreed mostly with what Hiltjo said and and forgot about it. > Still, I'm worried that Surf is becoming unmaintained. There are many > cool features in newer versions of WebKitGTK, and Surf'd benefit from > those. Anyone knows of maintenance status and reasons for inactivity > in the face of these new features? I agree, I'm a bit worried too! I have a lot of nice (I think) ideas, for isolation mostly (between domains). Also several local patches not pushed yet. Also as webkitgtk made the switch to GTK4, the whole main process needs refactoring for interfacing with current GTK main loop handling. This is quite an intrusive change as it requires reviewing the main structure, but it also put intrusive dependencies into the user system, forcing to have full dbus integration and several other isolation libraries that it inconditionally relies upon. Try running epiphany without those, it'll just respawn crashing webprocess in a loop. So, reason on my part is time and motivation (a bit reluctant to impose those dependency changes). > I'm not coming empty-handed, though. I'm ready to step up as Surf > (co-)maintainer and move it forward! Anyone willing to accept a former > Nyxt maintainer for this role? Well, switching maintainership like that is a bit of a stertch, but help on the transition would definitely be welcome. I admit that your first patch-submission experience wasn't necessarily the fastest one, but if you're willing to put some work there, I'll definitely take the time to properly review and discuss! > Best of love, Same, come by IRC if you can and want, it might be easier for discussing ideas. > Artyom Bologov > https://aartaka.me >
