I agree that estimates are weak, but I can think of two possibilities that might also work: one is the devs set a price, and the other that the users set a bounty. Each has pluses and minuses. The big plus is "all within the same environment, not a separate site".

@strypey @AbbieNormal @rysiek @sullybiker

@bhaugen @Wolf480pl@niu.moe @strypey @rysiek @sullybiker

Those are all interesting ideas but they are a bit more complicated than what I proposed

I proposed to sell the access to the issue tracker. That's all

@bhaugen @Wolf480pl@niu.moe @strypey @rysiek @sullybiker

Software production is craftsmanship

What's needed to achieve targets is not measurable.

And it's not a given that users know what they want, or that they share the vision with the devs

I wouldn't overcomplicate because then implementation gets more difficult and you run into overlaps with uman issues (differences in vision, motivation)

@bhaugen @Wolf480pl@niu.moe @strypey @rysiek @sullybiker

You risk this thing to fail and you couldn't even point precisely to a reason why

I'd keep it simple

The community needs to produce some more revenue right now without the need to implement new processes whose implementation would eat up the new revenue produced

I'd try to keep this more down to hearth

> The community needs to produce some more revenue right now

I agree, but nobody is going to pay to file bugs or help triage them. Also, the community would need even more revenue if it had to pay beta testers, which it would if paywalls on issue trackers blocked most users from doing it as volunteers.
@bhaugen @Wolf480pl @rysiek @sullybiker


@strypey @bhaugen @Wolf480pl@niu.moe @rysiek @sullybiker

If you're not ready to spend 10$ in a year, you won't be a great contributor anyway

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!