From Fedora Project Wiki
| Line 16: | Line 16: | ||
=== Payment Regulation === | === Payment Regulation === | ||
There are 3 scenarios which provide the necessary peer-review and | There are 3 scenarios | ||
transparency. | |||
# initial Request goes to FAmSCo | |||
# initial Request goes to CommArch | |||
# initial Request goes to the Card Holder | |||
for each scenario there are 3 stages which provide the necessary peer-review and transparency. | |||
# the initial Community-/Contributor-Request - like from a individual person or the fudcon-planning group etc. ... | # the initial Community-/Contributor-Request - like from a individual person or the fudcon-planning group etc. ... | ||
Revision as of 05:30, 10 June 2011
These is a subsection draft of the larger Process around Reimbursements and Sponsoring_event_attendees
Process for Payment with the community credit cards
Let Community Card Holders pay for you
In NA, EMEA, and LATAM, we have community credit cards that can be used for expenses. The receipts are collected by the card's main point of contact, and Red Hat pays the credit card bill from the Community Architecture budget. The points of contact are John Rose (NA), Joerg Simon (EMEA), and Neville Cross (LATAM).
In NA, EMEA, and LATAM, we have community credit cards that can be used for expenses. The receipts are collected by the card's main point of contact, and Red Hat pays the credit card bill from the Community Architecture budget. The points of contact are John Rose (NA), Joerg Simon (EMEA), and Neville Cross (LATAM).
Where are the Community Credit Cards most usable?
- buy things online on trusted online platforms!
- SWAG Vendors who accept card payments
- Vendors for Booth decoration who accept card payments
- pre-pay for hotel accomodation
- pre-pay travel tickets
- buy dinners ;)
- pay for SWAG shipment
- ... feel free to add more what could make sence
Payment Regulation
There are 3 scenarios
- initial Request goes to FAmSCo
- initial Request goes to CommArch
- initial Request goes to the Card Holder
for each scenario there are 3 stages which provide the necessary peer-review and transparency.
- the initial Community-/Contributor-Request - like from a individual person or the fudcon-planning group etc. ...
- PeerReview and approval if necessary
- direct handling of the payment by Card Holder with vendor, group or contributor
Communication/Decission-Making/Process-Reporting
goes all into the FAmSCo Tracking-System - do not forget to cc the responsible CardHolders in Trac! For Credit Card Payments, there must be a relation to a FAmSCo-Tracking-Ticket about a Fedora-Community-Decission or an event. This is also for the case that a larger stock of SWAG or a more expensive item like a Projector, Roll-up-Banner, TablesClothes etc. ... should be ordered for a number of multiple Events and also for Shipping expenses. FAmSCo Trac Admin keeps sure that card holders have full access to the FAmSCo-Trac!
goes all into the FAmSCo Tracking-System - do not forget to cc the responsible CardHolders in Trac! For Credit Card Payments, there must be a relation to a FAmSCo-Tracking-Ticket about a Fedora-Community-Decission or an event. This is also for the case that a larger stock of SWAG or a more expensive item like a Projector, Roll-up-Banner, TablesClothes etc. ... should be ordered for a number of multiple Events and also for Shipping expenses. FAmSCo Trac Admin keeps sure that card holders have full access to the FAmSCo-Trac!
Special Cases
- Shipping expenses for SWAG <50$ do not need approval from CommArch or FAmSCo
- If a Card Holder has to make a urgent decission - (of course based on sanity and reason and with a limit of ???$) - for a payment and can not create a ticket first, he is in charge to report the use of budget in the tracking system as soon as possible (48 hours?) to provide a predictable budget. This should always be an exception!