I think for a usual
      crowdfunding campaign on Kickstarter or Indiegogo it would be
      helpful to already have a developer who is able to deliver a
      defined goal. One would also have to define some perks that
      supporters get. This could be something from supporter badges on
      cups or for websites to technical support hours or training for
      the really generous. Or having the say in which feature/bug is
      implemented/fixed first.
      
      
      There might be other crowdfunding forms with more flexibility,
      where people can also vote on features and/or apply for
      implementing the feature. But this might also become relatively
      complicated for the untrained user.
      
      
      When I googled for "crowdfunding software" I found this list on
      Wikipedia: 
http://en.wikipedia.org/wiki/Comparison_of_crowd_funding_services.
      And a list of open source crowdfunding platforms: 
http://seedingfactory.com/2013/04/list-of-open-source-crowdfunding-platforms/
      And many more links that looked quite interesting.
      
      
      Did you post this crowdfunding idea on the PhantomJS mailing list?
      If a project has been forked so often there might be a few people
      who are not really core developers but already fairly familiar
      with the code or at least part of it?
      
      
      Maybe one could start with a little survey on who would be a
      potential developer, who would be a potential donor, what they
      would like/feel able to work on and what they would like to have
      fixed first?
      
      
      Am 14.06.13 12:53, schrieb Darren Cook:
      
      
I've been
        following the subsequent discussion. I thought it might be
        
        interesting if I described the exact situation where I wanted to
        use
        
        Kickstarter (or whatever).
        
        
        We all know one of the ideas behind open source development is
        
        contributors are scratching an itch.
        
        
        I'm using PhantomJS, which allows programmatic control of a web
        browser,
        
        and it can be run headless. However it is based on an old
        version of
        
        WebKit. To test the things I need to test I need a newer version
        of
        
        WebKit. But to do this requires upgrading to Qt5. It is a big
        job.
        
        
        There are 627 open issues on the github project. At least half
        of these
        
        would just disappear with a new version of WebKit.
        
        
        The github project also has 6,456 stars, 856 forks. Over on
        Google Code,
        
        there have been 1 million downloads (390K for version 1.8, 245K
        for
        
        version 1.9 so far).
        
        
        So, we have a relatively large sub-project, reasonably clear
        
        deliverable, with a large demand (300+ open issues), and a large
        group
        
        of potential donors.
        
        
        However, the core developers are all overloaded. And have said a
        
        financial incentive will not help. They want the upgrade too,
        but it
        
        will take a few months to get there.
        
        
        What I have is an itch. I don't have the knowledge to scratch it
        myself.
        
        I don't have the time to devote to learning how to scratch it.
        (It is
        
        not that big an itch, I just want to automate some testing.)
        
        
        Do you think a Kickstarter campaign would help?
        
        
        I'm fairly sure a target of say $5000 would be reached. Would
        that
        
        change the minds of any of the current core developers? Would it
        be
        
        incentive enough to bring in a new core developer (*)? I.e.
        we're not
        
        employing them. We're sponsoring the first project that brings
        them
        
        up-to-speed. After that they are a volunteer just like the rest
        of the
        
        core team.
        
        
        Darren
        
        
        *: I just stopped and asked *myself*
        that question, and realized the
        
        answer is a cautious yes: if the timing fitted in with a quiet
        time on
        
        other work. But I also wonder if the time it took to get up to
        speed
        
        might mean the core developers get to the task before me!!