GeopJr

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io "why do maintainers keep burning out?" and other mysteries nobody can solve

@Kriptolix@ursal.zone Hi, yes it's native GTK on Android! GTK got an Android backend some time ago and there's Pixiewood which does a lot of the glue stuff for Android and then the rest is on you, especially on patching libraries (see some of the patches I had to do https://codeberg.org/GeopJr/Tuba/pulls/1659) Eventually I'll write a blog post / guide, but it still needs a lot of work (for non-C/Vala, for gstreamer, for difficult libraries etc)

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io what exactly is the shitty behavior here? asking a downstream to change branding so upstreams stop dealing with a huge wave of bug reports that have already been solved? help me understand the end goal here. If the upstream gets burned out and gives up, how does that benefit the downstream who thinks something as simple as changing the name of the project is too much work that needs endless discussions? Do you think mint will start maintaining gnome calendar? great deal of funding behind them the financial reports are public, please tell me how much of it is allocated to gnome calendar? Speaking of funding, according to Mint's blog, they received $20,977 in funding last month. Surely that's enough to maintain your own calendar fork, isn't it?

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io My entitlement for demanding development upstream development is showing. /s But here's the thing, upstream has kept their end of the deal. They fixed the bugs, they fixed the issues and are asking downstreams to either keep up or stop pointing to them. Bullying??? That's kinda nuts. Don't try and play victim here. This is supposed to be collaborative cooperation. Not something combative. Calling things "nuts" won't make them any less real. You do realize that everyone can see all your posts in the last hours, right? As for "collaborative cooperation", talk is cheap, show me the "cooperation". Show me Mint's commits to Calendar. Show me XFCE's commits to GTK. It's only "collaborative cooperation" when it's not you who has to do all the work.

@liaizon@social.wake.st For Tuba, in its matrix room until I set up the CI!

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io You're more than a little wound up. Get some rest. I just don't think this behavior is anything collaborative, but it appears that you know better than everyone here who's "nuts". You could have put all this effort into forking and maintaining this instead.

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io "you are nuts", "you are angry" or you just inserted yourself in a conversation you can't handle.

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io Or the downstream projects contribute nothing to upstreams and just expect free work forever that exclusively benefits them and nobody else and when they get told no they come to social media trying to bully them into submission instead of, you know, forking and maintaining it themselves. You yourself have been complaining about GTK and whatnot this whole thread, claiming it's nothing new, so I'm asking you, why haven't you/xfce/mint forked GTK and everything else already? Instead of this whole "GTK and GNOME should do what WE want and NEVER what THEY want"

@zoeyTheWitch the fingerprints are just part of my life now

@andrewblasco@masto.es I'll make the CI build and upload it on every commit, but I'll refrain from adding it to fdroid yet, it's really not ready for prime time or anything other than a tech demo :p I have uploaded an apk on Tuba's matrix room

@kevinbowen@hachyderm.io "don't play the victim", meanwhile this is your feed over getting pushback

@kevinbowen@hachyderm.io @nekohayo@mastodon.social @jorge@hachyderm.io reminding you once again that your posts are public