home.social

#gnomecalendar — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gnomecalendar, aggregated by home.social.

  1. 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:

    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

  2. #TechIsShitDispatch
    I receive via email an invitation to an event. I attempt to accept the invitation and import it into my #Google calendar in #Thunderbird. I get two error pop-ups, one on top of the other:
    #Mozilla #GNOME #GNOMECalendar #Bugzilla #GoogleCalendar (1/5)

  3. 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: gitlab.gnome.org/GNOME/gnome-c

    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.

    #GNOME #GNOMECalendar #OpenSource #MaintainerLife #Patlabor

  4. Making the most out of GitLab's "Work Items" SNAFU that doesn't let you easily filter between Open and Closed issues without doing search filters manually, in #GNOMECalendar I have created three shared custom search filtering views for your convenience:

    * Newcomer items: gitlab.gnome.org/GNOME/gnome-c
    * All open bugs: gitlab.gnome.org/GNOME/gnome-c
    * Requests by designers: gitlab.gnome.org/GNOME/gnome-c

    If you are logged in, you can "add" those to the top of the "work items" list UI.

    #GitLab #UX #usability #GNOME

  5. 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: gitlab.gnome.org/GNOME/gnome-c

    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

  6. Finally realized what has been bugging me for years with the GNOME "Document Scanner" (Simple Scan) app's cropping feature: it doesn't set the mouse cursors to indicate where and how you can interact to adjust the cropping rectangle.

    I filed this issue with some hints, so that any newcomer can contribute a fix for it: gitlab.gnome.org/GNOME/simple-

    (BTW, there's a similar papercut in GNOME Calendar: gitlab.gnome.org/GNOME/gnome-c)

    #UX #usability #GNOME #SimpleScan #SANE #scanning #paperwork #GNOMECalendar

  7. 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: gitlab.gnome.org/GNOME/gnome-c

    Same with this 2.5-years-old feature request of mine (which has now been superseded by two of those UX enhancements): gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #MaintainerLife #GNOME #UX #QA #productivity

  8. Huge thanks to @maximiliano and @TheEvilSkeleton for reviewing & merging this very long-awaited UX improvement in GNOME Calendar's infinitely scrolling month view: the previous/next buttons (and corresponding keyboard shortcuts) now properly clamp to the beginning of months when switching months! :blobmiou:

    See the "before" vs "after" demonstration videos in the merge request: gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #GNOME #UX #productivity #calendaring #planning #OpenSource #FLOSS

  9. 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)

    gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #GNOME #MaintainerLife #iCalendar

  10. 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: gitlab.gnome.org/GNOME/gnome-c

    #FreeSoftware #OpenSource #QA #bugreporting #LinuxMint #Debian #Ubuntu #LTS #GNOMECalendar

  11. @fabio
    For those it may interest: let it be known that we also have a #GNOME application (called "Passes") for handling #PKPass or #esPass tickets, for #LinuxMobile travelers and partygoers in abandoned warehouses kitted up for a rave.

    I would be happy to see someone contribute some sort of inter-app integration between "Passes" and GNOME Calendar someday: gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #travelling #travel

  12. 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:

    gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #QA #MaintainerLife #GNOME

  13. Another notable feature merged in the GNOME Calendar live coding session today: the ability to export an entire calendar as an .ics file.

    This was originally added to the wishlist 10 years ago: gitlab.gnome.org/GNOME/gnome-c

    Thanks to @FineFindus's dedication towards implementing this (alongside the individual event .ics export feature) this year, you will be able to use this feature in #GNOME 50 (or the nightly flatpak version of Calendar today): gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #calendaring

  14. Is #Thunderbird really the only standalone #Linux desktop calendar app that can just subscribe to #CalDAV calendars? 🤨

    #GnomeCalendar needs a ton of dependencies and #GNOME stuff running.
    #KOrganizer the same for #KDE.
    #Evolution apparently just hooks into GNOME online accounts.

    There are some terminal calendar apps, but yeah... If one has #vim keybindings and is configurable via config files, I am open to suggestions.

  15. Is really the only standalone desktop calendar app that can just subscribe to calendars? 🤨

    needs a ton of dependencies and stuff running.
    the same for .
    apparently just hooks into GNOME online accounts.

    There are some terminal calendar apps, but yeah... If one has keybindings and is configurable via config files, I am open to suggestions.

  16. Is #Thunderbird really the only standalone #Linux desktop calendar app that can just subscribe to #CalDAV calendars? 🤨

    #GnomeCalendar needs a ton of dependencies and #GNOME stuff running.
    #KOrganizer the same for #KDE.
    #Evolution apparently just hooks into GNOME online accounts.

    There are some terminal calendar apps, but yeah... If one has #vim keybindings and is configurable via config files, I am open to suggestions.

  17. Is #Thunderbird really the only standalone #Linux desktop calendar app that can just subscribe to #CalDAV calendars? 🤨

    #GnomeCalendar needs a ton of dependencies and #GNOME stuff running.
    #KOrganizer the same for #KDE.
    #Evolution apparently just hooks into GNOME online accounts.

    There are some terminal calendar apps, but yeah... If one has #vim keybindings and is configurable via config files, I am open to suggestions.

  18. Is #Thunderbird really the only standalone #Linux desktop calendar app that can just subscribe to #CalDAV calendars? 🤨

    #GnomeCalendar needs a ton of dependencies and #GNOME stuff running.
    #KOrganizer the same for #KDE.
    #Evolution apparently just hooks into GNOME online accounts.

    There are some terminal calendar apps, but yeah... If one has #vim keybindings and is configurable via config files, I am open to suggestions.

  19. After two weeks of writing, revising, and trying to make everything as digestible as possible, I finally published "GNOME Calendar: A New Era of Accessibility Achieved in 90 Days", where I explain in detail the steps we took to turn GNOME Calendar from an app that was literally unusable with a keyboard and screen reader to an app that is (finally) accessible to keyboard and screen reader users as of GNOME 49!

    tesk.page/2025/07/25/gnome-cal

    #GNOMECalendar #GNOME #Accessibility #a11y #DisabilityPrideMonth #Linux #FOSS #OSS #OpenSource #FreeSoftware #GTK #libadwaita

  20. 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): gitlab.gnome.org/GNOME/gnome-c

    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:

    #MaintainerLife #QA #higgsbugson #GNOME

  21. Great news for @EvolutionGnome users: in Evolution 3.58 (expected to ship alongside GNOME 49 in Q4 2025), the calendar events conflict checks in meeting invitations received via email will now respect the user preferences; this will boost performance quite a bit: gitlab.gnome.org/GNOME/evoluti

    We will need someone to implement the corresponding per-calendar property in #GNOMECalendar's calendars management GUI, see gitlab.gnome.org/GNOME/gnome-c

    #performance #GNOME #email #calendaring

  22. Does anyone out here have days where they have more than 7 to 10 (or more) all-day events in their #calendaring app, instead of time-based events, and if so, why?
    My default assumption is "surely nobody does that?": gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar

  23. In case anyone feels up for a feature implementation challenge in GNOME Calendar: it would be cool to at least have a read-only implementation of meeting attendees, as a stepping stone to full-fledged meeting invitations management someday. See this limited-scope actionable ticket for details: gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #GNOME #calendaring

  24. I always saw "floating time" events as an "accidental" undefined timezone state for #calendaring events.
    I cannot believe it took me twenty years to finally understand the true usecase for this weird format feature: routines/habits that you want to do at the same time of the day no matter where you happen to be in the world. I am mind-blown :psyduck:

    Here's my feature specification for #GNOMECalendar's timezones picker GUI that I hope to see happen in time for #GNOME 48: gitlab.gnome.org/GNOME/gnome-c

  25. New #calendaring #UX design nightmare: timeless time-based events!

    How would you expect to manage and visually represent, in #GNOMECalendar, events with a start time but without a defined end time? :psyduck:
    gitlab.gnome.org/GNOME/gnome-c

    #GNOME

  26. Some additional details to take into account for whoever wants to do meeting events invitations handling in their standalone #email client (like #Geary and Envelope) for integration with #calendaring apps in #GNOME: gitlab.gnome.org/GNOME/geary/-

    Related: a newcomers-friendly bite-sized feature request in #GNOMECalendar to ensure we don't wreck mail clients' performance with large amounts of online calendars: gitlab.gnome.org/GNOME/gnome-c

  27. Fans de #logicielslibres de la francophonie, connaissez-vous l'Agenda du Libre, une plateforme de calendriers en ligne de @aprilorg répertoriant les événements de la communauté du libre?

    Je connais 2 instances:
    * agendadulibre.org
    * agendadulibre.qc.ca

    Ça offre des flux webcal!
    Eh bien… maintenant les heures/fuseaux vont fonctionner correctement dans votre logiciel de calendrier (comme #GNOMECalendar ou #Thunderbird): framagit.org/agenda-libre/agen

    #calendriers #opensource #Québec #France

  28. Fans de #logicielslibres de la francophonie, connaissez-vous l'Agenda du Libre, une plateforme de calendriers en ligne de @aprilorg répertoriant les événements de la communauté du libre?

    Je connais 2 instances:
    * agendadulibre.org
    * agendadulibre.qc.ca

    Ça offre des flux webcal!
    Eh bien… maintenant les heures/fuseaux vont fonctionner correctement dans votre logiciel de calendrier (comme #GNOMECalendar ou #Thunderbird): framagit.org/agenda-libre/agen

    #calendriers #opensource #Québec #France

  29. Fans de #logicielslibres de la francophonie, connaissez-vous l'Agenda du Libre, une plateforme de calendriers en ligne de @aprilorg répertoriant les événements de la communauté du libre?

    Je connais 2 instances:
    * agendadulibre.org
    * agendadulibre.qc.ca

    Ça offre des flux webcal!
    Eh bien… maintenant les heures/fuseaux vont fonctionner correctement dans votre logiciel de calendrier (comme #GNOMECalendar ou #Thunderbird): framagit.org/agenda-libre/agen

    #calendriers #opensource #Québec #France

  30. Fans de #logicielslibres de la francophonie, connaissez-vous l'Agenda du Libre, une plateforme de calendriers en ligne de @aprilorg répertoriant les événements de la communauté du libre?

    Je connais 2 instances:
    * agendadulibre.org
    * agendadulibre.qc.ca

    Ça offre des flux webcal!
    Eh bien… maintenant les heures/fuseaux vont fonctionner correctement dans votre logiciel de calendrier (comme #GNOMECalendar ou #Thunderbird): framagit.org/agenda-libre/agen

    #calendriers #opensource #Québec #France

  31. Fans de #logicielslibres de la francophonie, connaissez-vous l'Agenda du Libre, une plateforme de calendriers en ligne de @aprilorg répertoriant les événements de la communauté du libre?

    Je connais 2 instances:
    * agendadulibre.org
    * agendadulibre.qc.ca

    Ça offre des flux webcal!
    Eh bien… maintenant les heures/fuseaux vont fonctionner correctement dans votre logiciel de calendrier (comme #GNOMECalendar ou #Thunderbird): framagit.org/agenda-libre/agen

    #calendriers #opensource #Québec #France

  32. I spent some time assessing all the old, stale branches in #GNOMECalendar's main #git repository, and deleting any branches that were already merged or "so obsolete they'd never get merged" (we're talking 9-years-old branches there).

    If you do `git remote update --prune`, 23 stale branches get pruned out as a result, and you get a much clearer view in #gitg ☺️

    #GNOME contributors who had forked the Calendar repo a long time ago: don't forget to prune those branches from your fork on gitlab! 😉

  33. Part 1 of my #GNOMECalendar #webcal subscriptions #UX bugfixing trilogy has been merged today! No more duplicate calendars created by accident when adding a web calendar URL 🥳 gitlab.gnome.org/GNOME/gnome-c

    #GNOME #opensource

  34. New #calendaring specs compliance nightmare fuel for #GNOMECalendar developers and designers: the fact that events can reference completely made up "virtual" timezones 😵

    In which a university campus platform declares to be its own timezone (with #DST, of course!): gitlab.gnome.org/GNOME/gnome-c

  35. It is wild that I'm potentially solving a higgs-bugson in #GNOMECalendar's handling of some broken #CalDAV / #Webcal calendar providers (for servers using hardcore firewalling rules), a 6-years mystery… with a 1-liner fix that just sets a User-Agent string for #GNOME Calendar's #libsoup to identify itself when doing the initial URL validity check 🤨️

    Thanks to @s3phy's ingenious network/HTTP troubleshooting!

    gitlab.gnome.org/GNOME/gnome-c

  36. Online Accounts sync is strange : does it sync only once a day?
    That's the impression I have when I use , on Fedora

    @gnome 💗