I’m in two minds about this.
I’m appreciative that @Lin-Buo-Ren has both snapped libxml2-utils and offering it to the upstream to maintain.
Ordinarily when rejected by the upstream, someone needs to maintain the snap. Typically in snapcrafters we’ve maintained snaps which are typically high profile, sometimes as a ‘holding pen’ until upstream are ready, or if the existing maintainer no longer wishes to maintain the snap.
I worry that if we take on every snap in snapcrafters, it won’t scale. We’re already keeping on top of the security updates for all the snaps in there, but everyone one we add is another to manage.
It’s certainly a shame that upstream aren’t interested in maintaining this snap. I’ll be honest, anything that starts “lib*” is not really high on the hit-list of ‘interesting things to snap’. So I’m not sure what compelling advantage there is for this snap.
Happy to hear other’s opinions on this.