Project owners can now choose the amount donated to each commit.
They have a new button “Change project settings” on the project page along the project name.
In this screen they can change 2 things (for now):
a text describing their tipping policies that will be displayed on the project page on peer4commit
a checkbox that will put all new tips on hold when commits are found
When the checkbox is active, each new commits generates an “undecided” tip and the authors are not notified.
The project owners can then click on a new button on the project page to decide the tip amounts. They have these choices:
Leave undecided (to decide later)
Free (the commit won’t get any tip and the author won’t be notified)
Tiny: 0.1% of the project balance
Small: 0.5% of the project balance
The authors are notified when the tip amount is decided (unless they have recently been notified already, or if they said they don’t want any more notification, or if they have configured their peercoin address).
The 2 buttons are only available to project collaborators (those who can push changes to the supported repository).
There should be more options in the future. Your ideas are welcome.
Great, just had a quick look and posted the tipping policies against my experimental Github project. Good work.
Hope this gives the project owners a bit of leverage and get spammy commits out of the way by putting them in the free or tiny category.
Now we just need more trusted project owners who can support the project owner(s) to categorise commits appropriately.
Yes. Someone tried to exploit a bug. But since project balances are isolated, it didn’t work or rather he he was only able to withdraw the funds he sent to his own fake project. Actually I knew the bug existed but it was not a priority because I knew this isolation existed.
[quote=“sigmike, post:6, topic:2089”]Yes. Someone tried to exploit a bug. But since project balances are isolated, it didn’t work or rather he he was only able to withdraw the funds he sent to his own fake project. Actually I knew the bug existed but it was not a priority because I knew this isolation existed.
I’m glad we have people who help to crowd-source a tool’s QA! Presumably, now that the (apparent) vulnerability has been closed, they can retrieve their “test” donated funds with new commits to the repo, and then self-approve it until they deplete the balance?
No because he generated tips that failed to be sent. They exist so they empty the project balance, but they were not actually sent. To avoid duplication of tips in such abnormal situation, they stay in that state until manual intervention. I’m not sure what I should do with them. There’s about 500 PPC.