On Friday, 2 February 2024 00:38:56 CET Kevin Kofler via devel wrote:
> To make it clear about the situation of that particular package: The KDE SIG
> never notifies me in advance about kdepim bumps.

To make it clear about this particular package:

- we have _forgotten_ indeed to notify the maintainers on occasions.
- why did we forget? because the KDE collection is close to 400 packages and 
despite our automation, we are humans and this kind of thing happens.
- to make it clear that we *bother* (using your own words), I even submitted 
tickets upstream to help out on the situation: https://invent.kde.org/pim/
pimcommon/-/issues/2
- worth mentioning that despite the kdepim libraries being released as 
packages, they are *NOT* intended to be consumed externally but as a whole KDE 
PIM ecosystem
- this approach worked for blogilo in the past because it was part ot the KDE 
PIM ecosystem
- worth mentioning that Blogilo has been unmaintained for many years

I personally used blogilo in the past and loved the app myself.

However, sometimes we need to be pragmatic in life. I will quote one of the 
main developers of the KDE PIM:

" I don't understand why you still continue to release a dead apps from long 
time..."

Link to the *unmaintained* blogilo (not _legacy_): https://invent.kde.org/
unmaintained/blogilo

--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to