[kde] Pledging money for features



Hi all!

It is an issue I have been thinking about for some time, and I'm curious
if it has been discussed amongst the developers before.

So, there is a feature I really want, and I have filed a wishlist bug
for it and all (Bug #107302, specifically), but of course, I fully
recognize that every developer has ideas of his own that he wants to
pursuit, that there isn't enough time to hack up every idea that comes
by and that it is probably best in the long run that whoever writes the
code gets to decide what to work on.

So, if my ideas are to be implemented, I have to be prepared to pay for
it too. Now, I live off a normal salary too, so a contract to pay the
total costs for a given feature is beyond my reach, but say that I
say "I pledge to pay €100 to whoever gets the feature in Bug #107302
into KDE". That's not a lot of money, but if the right guy sees that he
could probably do it in a reasonable amount of time after several
people have made similar pledges, then perhaps it could work?

Now, this introduces a lot more complexity in the social fabric of a
free software project. All kinds of things could happen: I might not
feel that the feature fulfilled my intention behind the request and
decide not to follow up my pledge, and the guy who then had spent the
time might feel cheated. We might both be content with the new feature,
but then, it might not make to the official branch. All this would
probably call for regulations and bureaucracy, and lawyers... *shrug*.
It would be a long discussion.

OTOH, it could help a lot more people making a decent living from
writing free software, so it might be worth thinking about. Have you
people thought about it?

Cheers,

Kjetil
--
Kjetil Kjernsmo
Programmer / Astrophysicist / Ski-orienteer / Orienteer / Mountaineer
kjetil@xxxxxxxxxxxx
Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC

Attachment: pgpFOd71uhcGR.pgp
Description: PGP signature

___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Relevant Pages

  • Productivity: Quantity or Quality?
    ... produce software quantity or software quality? ... which "goal" should developers be aiming for? ... some "feature" may be taking its time for the programmer to produce, ... "science" (left hemisphere thinkers) people will find it simpler than "art" ...
    (alt.lang.asm)
  • Re: FC4 or FC5
    ... cost it is equivalent in Windows. ... you may have paid more for support of RHEL than XP. ... those who whine about this or that missing feature are losers. ... You seem to forget that not all users are developers. ...
    (Fedora)
  • Re: Some thoughts on VB9
    ... A Document Outline for code that displays #regions as well as groups members ... feature but that's pretty much the extent of refactoring in VB2005. ... is for good reason that VB developers have a bad rep.... ... VB developers who are serious about the language wrong. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Microsoft has utterly failed with Access 2007
    ... My thoughts on access 2007 form a developers point of view. ... feature for about 10 years and finally the folks in Redmond put this feature ... Anchoring of controls: ... remember looking at the forms designer and the report designer in access. ...
    (microsoft.public.access.modulesdaovba)
  • Re: RUP: Can I Implement a Use-Case Partially?
    ... However, once the developers agree that the requirements have been properly specified, they can only estimate that solution. ... If requirements change during the development, then one has to have a process for change management that will update the estimates. ... estimates for the current increment. ... An interesting feature is that it is time-boxed. ...
    (comp.object)