GNOME Calendar 51 will be able to recognize Microsoft Teams meetings links in events, surfacing them with a convenient "Join" button (instead of gibberish) like other videoconferencing systems known to us: https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1312

Daily-drive the nightly flatpak like all the cool kids and you'll be able to immediately hop onto calls to circle back and synergize with your clients or colleagues who use this… thing 

#GNOMECalendar #GNOME #productivity #meetings #Teams #MicrosoftTeams

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

Parrot (@[email protected])

Attached: 1 image @[email protected] @[email protected] @[email protected] @[email protected] Alors nous n'avons pas la même version, moi j'ai la 41.2 de Linux Mint

Mastodon Chapril
#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)

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.

#GNOME #GNOMECalendar #OpenSource #MaintainerLife #Patlabor

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: https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/views/38
* All open bugs: https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/views/40
* Requests by designers: https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/views/41

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

#GitLab #UX #usability #GNOME

Sign in · GitLab

Welcome to GNOME GitLab

GNOME Live Coding | Calendar (EN)

YouTube

@wook
GNOME Calendar's list view is currently the same as implemented in 2022… It may become available as a switchable view even on desktop, but needs to be refactored and rewritten to go with the new designs and infinite timeline.

* https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1403
* https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1069
* https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1070

As part of https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/965 and https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1332 and https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1353

We have plans within plans…

#GNOMECalendar #GNOME #UX #linuxmobile #mobilelinux

Port the "sidebar" agenda view to ListView with groupings (instead of ListBox) and AdwClampScrollable (#1403) · Issues · GNOME / gnome-calendar · GitLab

The following discussions from

GitLab

@parrot_33
Point du tout… j'utilise l'application presque exclusivement au clavier quotidiennement, et ça marche, incluant passer d'un champ à l'autre au clavier avec Tab (ou même d'un événement à l'autre avec les touches directionnelles, dans la dernière version), tel que démontré dans la vidéo ci-jointe.

#GNOMECalendar met énormément d'efforts pour rendre l'application accessible autant que possible, majoritairement grâce aux contributions de code de @TheEvilSkeleton

@sebsauvage @Natouille

@auinobackonlinux @zoeyTheWitch
The "export" feature has been gracefully implemented by @FineFindus in #GNOMECalendar versions 49 and 50.

As for the "file attachments" idea, this is https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/942, which sounds a bit like a synchronization + UI + security nightmare to me.

Support file attachments (RFC 5545 section 3.8.1.1) (#942) · Issues · GNOME / gnome-calendar · GitLab

Dear developers, Thanks for your great work on gnome-calendar ;-) It would be nice to add file attachment feature, which is a very standard feature on...

GitLab
Also, why isn’t it possible to share an event or attach files to it? #GnomeCalendar