#gnomecalendar — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gnomecalendar, aggregated by home.social.
-
PSA to #infosec researchers reporting issues on desktop software: y'all, a simple CPU-hogging performance issue where we're showing too many widgets (instead of a summary when importing a large file) is not a "Denial of Service", come on :blobmiou:
Sometimes, a cigar is just a cigar.
https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1632
#MaintainerLife #QA #GNOMECalendar #Sysprof #performance #GNOME #security #Linux #OpenSource
-
All of this brings me to GNOME Calendar and @linuxmint. For years, we've been dealing with users reporting issues about Linux Mint's package of GNOME Calendar to us, that were either never present or addressed releases ago.
Just a couple of examples:
- https://pouet.chapril.org/@parrot_33/116374864921983890
- https://vmst.io/@doctroid/116542487573304110
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/300
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1562
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1535
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1526
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1429
- https://matrix.to/#/!koZzDOwNHEzEoeuNok:matrix.org/$174759788212004HiyFg:gnome.org?via=gnome.org&via=matrix.org&via=fedora.im
There were a couple of discussions regarding this in the past, in chat, but none of it ended up being productive. Eventually, we got fed up by it and I opened issue #1 on Mint's package of GNOME Calendar — the first issue ever in their package's repository — asking them to remove all links pointing to upstream GNOME Calendar and rebranding the app. This had no response for 6 months, all the while we were still getting bug reports about Mint's broken package. @nekohayo eventually got fed up (again!) and pinged the packager. The packager replied with something completely unrelated and asked which modifications we did not like, completely ignoring our actual request. So, I just told him bluntly that we don't have the time to look through the code just to pinpoint specific issues, so I'll just loosely say "everything", and the only way for us to be happy is if they could rebrand and we can move on.
Then, the packager responds with something unrelated once again, ignoring the essence of my comment, and follows with a whataboutism — "As i said, 46 and 48 are used by millions of people right now in Ubuntu LTS and Debian Stable. Are you going to request Debian and Ubuntu stop shipping GNOME apps?" — in other words, "what about Ubuntu LTS and Debian Stable?" — as a bonus, twisting my words and going from GNOME Calendar to "GNOME apps".
So, once again, I reminded that this is not what the issue is about.
As a side note: no, never would we go after Debian or Ubuntu over this. If the distribution in question is doing its job properly by simply not bothering the people writing the software that they package, then why should we go after them? They are not the ones misleading users into opening in the wrong place, so there is no reason for us to be upset about. In this case, Linux Mint is leeching off of Debian, and pushing their responsibility onto us.
The packager then explains what to do, and redirects us to Debian to take down the package, essentially roping Debian into Linux Mint's problem — all the while completely ignoring the premise of this post. Sure, both Linux Mint and Debian's packages share the same source; however, this is just a technical detail. The actual problem, one that regularly affects us, is that Linux Mint users report issues to us, whereas Debian users report them to Debian.
So, I remind him bluntly that this is not our responsibility as an upstream to fix his problems.
He then suggests to incorporate code upstream to check if the user is running an outdated version or not. In other words, either phoning home, somehow keeping track of releases every 6 months, or something unrealistic.
I lose my patience and hostily tell him that we upstreams don't care about how distributions operate, and reminded, once again, that all we want is for them to rebrand. To which he replied with "If you don't care, then neither do we." — confirming that Linux Mint doesn't care about Debian or even itself as a distribution. Then says "probably requires GNOME Calendar to move away from free licenses" and locks the issue — once again, completely ignoring the essence of this entire issue.
Now they know what the problem is, and have refused to act on it by shoving their responsibilities onto us, but this time intentionally, because that should show upstream for hurting my feelings, never mind the fact that we are the ones doing the hard work, and they are making us do more work. This is the length some distributors will go to abuse people's generosity.
#MaintainerLife #Linux #GNOME #GNOMECalendar #FOSS #OpenSource #FreeSoftware
-
PSA to GNOME Calendar contributors: we just merged a pair of refactoring branches that rearchitect tons of code to eliminate a whole class of problems in the backend and the views: https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1496
This unfortunately means many contributors with pending merge requests will have to manually rebase and deconflict their code on top of the latest main branch. It may feel like reloading a Patlabor's revolver, but should be worth it.
-
PSA: following the example from various other projects within GNOME (such as Loupe and libadwaita), GNOME Calendar now explicitly forbids AI-generated contributions, with the same policy: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/725
We honor the exquisite art of organic homegrown code made with care and a willingness to learn the craft, and want to protect the time of people who help review merge requests.
#MaintainerLife #FreeSoftware #FLOSS #OpenSource #GNOMECalendar #NoAI #aislop #genAI #LLM #GNOME #libadwaita
-
An example of a 10-years-old feature request in GNOME Calendar that has been superseded by the combination of 5 other UX improvements, to the point where I am comfortable putting the original ticket to rest until a new technological development comes up: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/46#note_2686910
Same with this 2.5-years-old feature request of mine (which has now been superseded by two of those UX enhancements): https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1072#note_2686968
-
To celebrate the new year, I, too, have decided to partake in the traditional GNOME bugfixing technique of… deleting code to make things work :blobmiou: (it turns out that some parts of calendaring standards specifications are pretty weird, and most other apps couldn't even render the alarm types we created)
https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/680
-
FLOSS #MaintainerLife public service advisory:
If you're filing a potential bug upstream in #GNOME, particularly on rapidly-improving apps like GNOME Calendar, please test the latest version, unmodified by third-parties. #Flatpak helps.Don't come at me with a 4-years-old version cowboy-patched against our will by #Linux distros like Mint; I will send you downstream, like this: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1526#note_2640160
#FreeSoftware #OpenSource #QA #bugreporting #LinuxMint #Debian #Ubuntu #LTS #GNOMECalendar
-
A six-years-old heisenbug in GNOME Calendar's week view, demonstrated in the picture below, just got fixed thanks to one oddly specific duplicate bug report's reproduction instructions and This One Weird Trick 1-character patch by @KekunPlazas … The Cause May Surprise You!™ :thinkerguns:
-
In the past few years of triaging issues for #GNOMECalendar, I noticed it's often the same three distros from which I keep hearing the weirdest things…
This is the 3rd time someone complains that dark mode is not working, and I don't know how that's even possible (elsewhere, it Just Works): https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1390
I don't know what y'all do with Endeavor OS and Nix OS, but it sure sounds like playing #Linux on "Ultra Violence" difficulty :blobcatcoffee: