https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #42 from Flossy Cat <flossy-...@online.de> --- Hi Bernhard, (In reply to Bernhard E. Reiter from comment #37) > … > > F5: In both bug reports I offered my help and support for implementation > > as a seasoned computer engineer if I'm pointed to introductory material > > or are guided. > > > No reaction to this offer … > > CONCLUSION: Active support is either not wanted or needed. > > KDE welcomes people, needs and wants active support! Then, I wonder why nobody pointed me to some kind of primer, guidance, an onboarding process or anything like this – because I explicitely asked … If KDE needs and wants active support this kind of things should be available, know to the bug triage theme and promoted on request. > The problem often is that if someone offers this on a specific defect is > that > (because of Moore's law) you often put more effort into the mentoring > or guidance than to fix it yourself. Especially if the defect is > a chain of technical decision and dependencies. Thus mentoring someone > makes sense if there is high chance that this person wills stay within KDE > at least for a while. I'd provided in several bugs the code segments, commits or discussions, where the root cause lies. I provided code snippets. Some capability can be plausibly assumed. This should be sufficient to at least explicitly ASK if I will provide lasting support (instead of silently assuming I wont – which BTW is a wrong assumption …) > Another aspect is that getting a development setup and putting contributions > forward is already documented in general for KDE products. So anyone could > (in principle) do it without guidance. You could just set this up, come up > with patches for a code variant into mobile and desktop and contribute them > without much specific interaction. (Yes I am fully aware that this is a > suboptimal decision process when looking at it from a greater scale.) I explicitly stated with my support offers that I want guidance because I'm aware of the complexity of the KDE products and want to avoid acting against plans or carelessly introduce detrimental side-effects. > You could also propose a backport patch to OpenSuse LTS. As explained in my answer to Martin: This multiplies the effort and wastes the scarce resources of several downstream distribution teams (if other users replicate the request to their distribution support teams) More important: F6: The first bug reports arrived 6 month after the regression was coded – more than 2 years ago! There is no "official reaction" of the KDEPIM team on any of these. Further there is no KDEPIM team reaction on similarly fatal bug 483545. Meanwhile I know for sure: this is no matter of potentially old, incorrect mail formats: It happens in my productive system to! (If you use Kontact, you should dig into it) AFAIR Kontact (more exactly the whole Kolab suite) was once officially funded, supported and used for public authorities (as a substitute for Outlook). For that reason I actually expected a backport by SLE. This not happening I conclude the use by public authorities has ceased … 2 years of silence by the KDEPIM team and no reaction to the fatal bug 483545 let's me conclude: there is no proper maintenance of Kontact anymore … Bug 481069 tells a similar story on KDE level itself: ill advised functional regressions biting a lot of users. Bug 491130 is about a fatal regression on KDE level, breaking very old, very fundamental desktop functionality – with no "official" maintainer reactions so far. KDE maintenance level perhaps is also already questionable?!? > To be more specfic: What kind of help would you need to come up with > improvements on aspects? > > Getting to back on some other aspects, though it somehow gets beyond this > issue. I think the proper place for this discussion would be discuss.kde.org and this discussion would need some supporters because it will require IMHO fundamental changes in the way KDE is curated, if the decline is to be stopped … -- You are receiving this mail because: You are watching all bug changes.
