Summary: | Quality Assurance should supersede short-term temporary and local advantages | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Uwe Dippel <udippel> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | cfeck |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Uwe Dippel
2014-04-25 21:05:45 UTC
Please take discussion to a forum or mailing list, not this bug tracker. If you have specific bugs to report for Baloo, please file one ticket per issue. So I *was* right in the end! - Instead of pointing out any quality assurance; any quality control in the KDE project, Christoph Feck suggests to continue this discussion on "a forum or mailing list". Meaning, none such exists! So I may discuss this on Slashdot, or Wordpress, according to him, but there is no resource within KDE that oversees project development. And this would not be a bug? Is this term - and the horizon of people like Christoph - limited to actual bugs in source code? I don't think so. Organisational setups can be just as buggy, and the KDE project of recent is buggy as such, when dysfunctional code is permitted to be replaced by other dysfunctional code. I started to call this the Heartbleed-Sympton in FOSS: Anyone can plug her half-witted code into the core of any project of choice. This is nothing but insanity; and it doesn't need a Theo de Raadt to point this out. If you question my horizon, please step up as the head of our quality control team. We will be happy to see someone as energetic as you. And yes, this is a bug tracker, which is used to track bugs in code, documentation, translations, and artwork. To get you started, I suggest you subscribe to https://mail.kde.org/mailman/listinfo/kde-bugs-dist mailing list. This way, you will get notified about issues our users see with KDE software, and can act accordingly. Once you get more familiar with our workflow, you could also subscribe to https://mail.kde.org/mailman/listinfo/kde-commits mailing list. This way, you will see all changes, and can review them for possible quality or security issues. (In reply to comment #3) > If you question my horizon, please step up as the head of our quality > control team. We will be happy to see someone as energetic as you. And yes, > this is a bug tracker, which is used to track bugs in code, documentation, > translations, and artwork. Thanks for the invite! - If the conditions are right, I will gladly do so. Your subsequent comment clearly shows that I must have been unable to express my concerns; since you once again stress the actual code quality. However, the actual code quality of KDE is AFAICS quite okay. I (and others, cf http://vhanda.in/blog/2014/04/desktop-search-configuration/) question the layer above the code. Some policy decisions were seemingly buggy; and that's why I filed my report on this as a 'general' component. Policy decisions are not discussed in this bug tracker. Please start a thread in the KDE forum at https://forum.kde.org/ or on a mailing list at http://www.kde.org/support/mailinglists/ If you want to address KDE developers instead of users, I would suggest to use the kde-core-devel list. There you could explain what issues you see, how you would solve them and under which conditions, and what questions you have before you can start. If you get no reply, it usually means "go ahead". |