void

[ghost]

follow-up #219

[joe-p]

Thank you for the feedback. We're aware that our bounty process needs to be improved. Until we resolve our processes internally, we will close our bounties so someone doesn't end up in the same situation as yourself (don't worry, still working to payout you and any other pending bounties). Once we have everything ready on our end, we can open up the bounties with a more refined and transparent process. When we do so, your suggestions will certainly be taken into consideration.

For the PR bounty in particular, I think we need to be more transparent and objective when it comes to determining payout amount. I don't think how long a specific issue is open for is a great determination though because a bug could remain open for a long time because it's very minor. A general priority system would be nice, but it's ultimately up to the Inc for whether they want to adopt a new system or not.

[joe-p]

Yes there are two entities at play here. Algorand Inc is where the core engineers work. They own github.com/algorand and its repositories (including go-algorand). They are responsible for triaging the issues on the GitHub. You might see tags on issues such as "Team Lamprey". These teams are internal engineering teams at the Inc.

The Foundation is responsible for the bounties. We (I work for the Foundation) create the bounties and manage the processing of the bounties and their payments