Papercuts fund

[G-linx]

I second that

[terminills]

I'm merely starting a thread to discuss how to properly design a fund to handle paying for fixing small bugs in AROS.


Obviously we've used power2people for many years to handle bounties. 

I would like to point out that the fund cannot have a single point of contact due to the fact that people lose interest, get old or whatever may happen.

So suggestions.

It's also worth noting that fees will be deducted due to paypal's policy of charging merchant fees even for donations.


https://www.paypal.com/us/webapps/mpp/merchant-fees#ReceivingDonations


USD a $5 donation has a .49 + 2.89% so that's about $0.64 eaten from a $5 donation.   

[G-linx]

... I think we'd have to cover that, or half the fee at least, can't short change anyone

[terminills]

I'm merely starting a thread to discuss how to properly design a fund to handle paying for fixing small bugs in AROS.


Obviously we've used power2people for many years to handle bounties. 

I would like to point out that the fund cannot have a single point of contact due to the fact that people lose interest, get old or whatever may happen.

So suggestions.

Spoke to André and he suggested having the fund allow one time payments due to the fact that you have the ability to make a larger one time payment and less gets eaten by fees.

Example in USD based off of paypal's website

$60 single Donation after fees would be around 57.776
but 6, $10 donations after fees would be 52.21.

[deadwood]

Hmm, arent' there two fees?

I fee that gets extracted when donor pays to power2people. The second few when power2people pays out to developer?

[terminills]

Hmm, arent' there two fees?

I fee that gets extracted when donor pays to power2people. The second few when power2people pays out to developer?

Yes plus Paypal has a split fee schedule.    Percentage plus transaction.   In the US it's  2.89% +.49 per transaction.  the .49 doesn't seem like much until you add it across 100's of transactions.

[terminills]

Okay so here's where we sit.

• 2 Community members control the verification and payout system(mainly because we've had issues in the past of users not verifying bounties).
  Payout is twice a year or 10 fixes whichever comes first(Developer has the option of waiting).
• Donations can be either one time or subscription with preference to single larger donations due to fees but all are appreciated.
• Yearly nominations of the 2 community members(Assume nominate in December vote in January?).   Initial vote should be within the next month.
• Papercut/trivial tag needs to be in the issue/bug tracker.
• Outreach,  we need to reach outside of the Amiga/AROS community(maybe create a informational page?).

[G-linx]

Looks good. But obviously needs approval from those higher than me.

I would like to see permanent banners at the top of all aros related website's/forums advertising the paper cut initiative.

[terminills]

Looks good. But obviously needs approval from those higher than me.

I would like to see permanent banners at the top of all aros related website's/forums advertising the paper cut initiative.

There isn't really a higher up.   It's supposed to be community driven.

[G-linx]

There'll be a few more responses when everyone's back from the Sunday visits no doubt.

[terminills]

There'll be a few more responses when everyone's back from the Sunday visits no doubt.

I know I'm just trying to keep it on the front page.

[G-linx]

Any further comments ideas or suggestions from anyone?

[miker1264]

Well I'll start

I would suggest setting up 2 dates as to which the funds will be used maybe say in January and July.
Point of contact should be voted on at least once a year.
Point of contact IMHO should be one developer and one user.

Rules for papercut I would suggest at least 2 verification's that the bug is fixed.

Looks good, what I'd add is:
1) Contact people should decide on two topics: if issue is matching papercut criteria (is not too simple, not too hard, not designed to abuse the system)
2) Payout would be twice a year OR after reaching some threshold. If a developer fixes 10 issues in second week of January, he should not need to wait until 1st July to be paid out

This approach sounds very interesting and it would benefit AROS. That is very positive.

[aha]

Okay so here's where we sit.

• 2 Community members control the verification and payout system(mainly because we've had issues in the past of users not verifying bounties).
  Payout is twice a year or 10 fixes whichever comes first(Developer has the option of waiting).
• Donations can be either one time or subscription with preference to single larger donations due to fees but all are appreciated.
• Yearly nominations of the 2 community members(Assume nominate in December vote in January?).   Initial vote should be within the next month.
• Papercut/trivial tag needs to be in the issue/bug tracker.
• Outreach,  we need to reach outside of the Amiga/AROS community(maybe create a informational page?).

Thank you for the efforts on this! I appreciate it.

[Amiwell]

Okay so here's where we sit.

• 2 Community members control the verification and payout system(mainly because we've had issues in the past of users not verifying bounties).
  Payout is twice a year or 10 fixes whichever comes first(Developer has the option of waiting).
• Donations can be either one time or subscription with preference to single larger donations due to fees but all are appreciated.
• Yearly nominations of the 2 community members(Assume nominate in December vote in January?).   Initial vote should be within the next month.
• Papercut/trivial tag needs to be in the issue/bug tracker.
• Outreach,  we need to reach outside of the Amiga/AROS community(maybe create a informational page?).

[/quote

I agree thank you