Hi Anne, I agree with aht the others said in this thread. Just one more thing:
2012/12/9 Anne Wilson: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 09/12/12 13:50, Frank Reininghaus wrote: >> Hi, >> >> 2012/12/8 Dion Moult: >>> Hello all, >>> >>> On occasion (less actively nowadays) I prune the KDE brainstorm >>> section. For those who don't know, the KDE forums have a section >>> called Brainstorm, where the users can submit ideas and vote on >>> them. >> >> first of all, thanks for your work! I think that the brainstorm >> section of the forums is a very useful tool for the discussion of >> possible new features. >> >>> One of the things I rarely get to do is move submitted ideas into >>> the "In progress" or "Done" sections. This makes me feel that >>> developers simply aren't looking at the Brainstorm and >>> essentially, users are ignored through this medium. >>> >>> As I care very much about the success of the brainstorm and that >>> users actually see that they are being acted upon, and since I >>> have been moderating the section for a long time (I've somewhat >>> become a walking search tool for duplicate ideas!), I want to try >>> and make it work better. >>> >>> Because I cannot force developers to try and integrate it into >>> their workflow if they haven't already, here is my proposal: >>> >>> If you are the lead developer on a certain section of KDE, such >>> as plasma, activites, kontact, etc, please send me an appropriate >>> way to contact you. >> >> I think that unless any maintainer tells you something else, ideas >> from KDE brainstorm that are discussed in the forum and considered >> useful should be reported as wishlist items at bugs.kde.org. >> >>> Every so often, I will pick the users top choices that seem >>> plausible and will bring them to _you_, and discuss how to evolve >>> the idea into something that could be implemented. Then we can >>> open up an enhancement bug report in BKO, and start getting some >>> brainstorm ideas along the Submitted->In progress->Done chain. >> >> Of course it would be nice to see more ideas in the 'Done' >> section. But please note that discussing ideas in the forum and >> then reporting them at bugs.kde.org is by no means a guarantee that >> the idea will really be implemented, even if everyone (including >> the maintainer) agrees that the idea is good. Writing the code, >> testing it and merging it into master usually takes a considerable >> amount of time. If you only have a bit of spare time to work on >> KDE, and your inbox is always packed with mails from bugs.kde.org, >> then you cannot implement many ideas :-( >> > There is a perception that devs don't listen. This is not a > complaint, on my part, but a statement of fact. Well, I can't speak for all developers, but on my side, there is a perception that some people believe "If I have a good idea, it will either be implemented by the maintainer of the application, or it will not be implemented at all, and then the maintainer has to provide an explanation why he/she won't implement it". This is confirmed by... > I'm wondering if it > is not impossible to set up a semi-automated service that would > respond to such wishes, perhaps with the dev selecting from > > a) sounds good, but frankly it's too complicated for the time available > b) sounds good. I'll put it on my to-do list, but bug-fixing takes > priority > c) I will discuss this idea with my co-developers ...the lack of an option d) Sounds good. Patches welcome! In your list. But then I also have to agree with what Martin says: a large number of the wishes reported on bugs.kde.org does not make much sense, and I already spend quite a bit of time explaining to at least some of the reporters why their particular wish will not be implemented. If I provided that kind of response for every Dolphin wish report on bugs.kde.org, then there wouldn't be much time left for the more important things (like patch review and bug fixes). Best regards, Frank >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
