https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #12 from Flossy Cat <flossy-...@online.de> --- (In reply to Nate Graham from comment #9) > From the perspective of Bugzilla, this isn't a bug; the removal of the > feature was intentional. The request being made here is to reconsider that > removal and bring it back. Note that the "regression" keyword is already > applied. Yes – because I applied it … > Since you've identified the commit that removed the feature, and you know > C++, submitting a merge request to re-add it (including your proposed code > improvements so that it doesn't get removed again) hopefully should be > feasible! The important words were "support" and "if guided", meaning: "I do not know my way around the KDE development eco-system and need introduction and help!" Knowing C++ alone is not sufficient to successfully navigating the re-introduction … I also do not like the sound of "hopefully … feasible". I'm not in dire need of opportunities to waste my time. I'm an IT professional with a definitely non-empty schedule. I'm willing to carve out the necessary time from my schedule only when 1. there is a commitment by KDE to re-introduce and keep this IMHO important feature, if I do a proper implementation. 2. there is introduction/help to find my way around and to quickly set up an adequate working environment – hopefully you have some kind of onboarding process for new volunteers and a mentoring system? 3. crucial technical information is provided, like 3.1 what is the time-frame for re-introducing the feature 3.2 have I identified the correct GIT (you affirmed this, thank you – but with KAlarm I identified an obsolete one …) 3.3 which library and function is to be used to retrieve specific data from the D-Bus, akonadi, or the notifier window – in the cases where I can't derive this from the code around the removed feature (i.e. I need somebody in the know, willing to answer similar questions) 4. the same support request applies to the documentation part – if the function is not properly documented, it essentially does not exist and is not used -> back to square one … -- You are receiving this mail because: You are watching all bug changes.
