in this scenario, who would end up implementing the feature & earning the bountythe same people that work on regular bounties.
once a bounty is funded through crowd-donations, the organization and the developers just treat it like a regular bounty.
effectively, what it comes down to is implementing a crowdfunding system.
i see three scenarios:
the current bounty means: we have money, but we don't have developers for this feature, so we'll put up a bounty.
then you have the case where: we have developers, but we don't have money, so we need crowdfunding.
and finally both together: we have neither developers nor funding for this feature, but if we can get this crowdfunded we can put up a bounty.
actually, crowdfunding would or could be independent from the bounty process because it is just a method to get funding. so it's even a question whether this is in scope of algora or should be something separate. i can see the advantage of having both in the same app because a crowdfunded feature could graduate into a bounty automatically: this bounty goes live as soon as the funding goal is reached,
but on the other hand this would also add complexity and maybe even confusion, because now you are dealing with three types of users: the organisation, the contributing developers and the financial supporters.