On Thu, Sep 22, 2011 at 11:29 AM, Harri Porten <por...@froglogic.com> wrote: > Don Sanders, one of the former KMail maintainers, had such a system set up > many years ago btw. I couldn't find anything about it anymore online. But > iirc it didn't work out too well... > > Harri.
Just to clarify, I'm not strictly against bug bounties, I just remembered I read that article recently and wanted to bring it to the table. Now, here's an idea, I don't know if essentially different from previous ones but we could discuss: What about funding bug squashing parties and stabilization sprints? That's not exactly a "pay per fix" model, but a way to sustain these activities which are very time consuming. The main reason why I think this is a better approach than plain "pay per fix" is that any given developer in the KDE project, or any large FOSS project whatsoever, is not able to cope with the size of bug lists and individual bugs (that is: some bug lists are larger than life and some bugs are extremely hard to reproduce - and that all comes before the fix) so I truly believe that if we don't attack theses collaboratively, there's no way we can really try killing the backlog. So what I'd love to see (and that's just me) are lots of distributed bug squashing and stabilization sprints "Sponsored By SomeMediumSized Co.", where funds can probably be managed through KDE e.V. or something, but can ultimately be distributed by the organizer of the sprint in the way she finds more useful. Notice that this is probably already happening, so I'm just maybe pointing to an existing idea, because this seems to me like https://sprints.kde.org/ with sponsors logos in each sprint box. David E. Narváez >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
