Community credit card process

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Created page with "For now, see our draft page for this topic.")
 
(cleanup)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
For now, see our [[User:Jsimon/draft_community_credit_card_process|draft page]] for this topic.
+
{{admon/important | This page is part of the larger process around [[Reimbursements]] and [[Sponsoring event attendees]].}}
 +
 
 +
{{admon/note | Let community card holders pay bills 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 [[User:Inode0|John Rose]] (NA), [[User:Jsimon|Joerg Simon]] (EMEA), and [[User:Yn1v|Neville Cross]] (LATAM).}}
 +
 
 +
=== What can the cards be used for? ===
 +
 
 +
Assuming that '''the expense has been approved''', the cards can be used for:
 +
 
 +
* Purchasing materials needed for Fedora from trusted online sellers.
 +
* Linking the card to PayPal for reimbursing Fedora expenses.
 +
* Vendors for swag, media, etc. who accept credit card payments.
 +
* Sponsorship of booths/events that accept credit card payments.
 +
* Paying for hotel accomodations.
 +
* Paying for travel tickets (air, train, etc.)
 +
* Meals
 +
* Shipping
 +
* etc.
 +
 
 +
=== Approval of expenses ===
 +
 
 +
There are several parts of Fedora that can approve an expense on the community credit cards:
 +
 
 +
# Initial request goes to [[FAMSCO]] and is routed to the appropriate card holder.
 +
# Initial request goes to a member of [[Community Architecture]] or to the [[FPL]].
 +
# Initial request goes directly to one of the card holders.
 +
# One of the cardholders makes a judgement decision to have an expense, or if something urgent comes up.
 +
 
 +
What does this mean?  It means that for each scenario above, there are several ways that transparency is maintained:
 +
 
 +
# The initial requestor, which is an individual contributor, an event owner, a FUDCon or FAD organizer, a regional ambassador leader, etc.
 +
# Peer review and approval.
 +
## Regional ambassador meeting.
 +
## FAMSCo makes a decision.
 +
## Community team or FPL makes a decision.
 +
# Direct handling of the payment by card holder.
 +
 
 +
[[File:fedora_comm_card_process.png]]
 +
 
 +
{{admon/note | Opening tickets and tracking requests | We are currently using the [https://fedorahosted.org/famsco/ FAmSCo trac instance].  Cc the responsible card holders in trac and choose your region, so we know which region needs the money.  If you have questions, contact the [[User:Jsimon|FAmSCo trac admin]].}}

Latest revision as of 03:46, 27 July 2011

Important.png
This page is part of the larger process around Reimbursements and Sponsoring event attendees.
Note.png
Let community card holders pay bills 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).

[edit] What can the cards be used for?

Assuming that the expense has been approved, the cards can be used for:

  • Purchasing materials needed for Fedora from trusted online sellers.
  • Linking the card to PayPal for reimbursing Fedora expenses.
  • Vendors for swag, media, etc. who accept credit card payments.
  • Sponsorship of booths/events that accept credit card payments.
  • Paying for hotel accomodations.
  • Paying for travel tickets (air, train, etc.)
  • Meals
  • Shipping
  • etc.

[edit] Approval of expenses

There are several parts of Fedora that can approve an expense on the community credit cards:

  1. Initial request goes to FAMSCO and is routed to the appropriate card holder.
  2. Initial request goes to a member of Community Architecture or to the FPL.
  3. Initial request goes directly to one of the card holders.
  4. One of the cardholders makes a judgement decision to have an expense, or if something urgent comes up.

What does this mean? It means that for each scenario above, there are several ways that transparency is maintained:

  1. The initial requestor, which is an individual contributor, an event owner, a FUDCon or FAD organizer, a regional ambassador leader, etc.
  2. Peer review and approval.
    1. Regional ambassador meeting.
    2. FAMSCo makes a decision.
    3. Community team or FPL makes a decision.
  3. Direct handling of the payment by card holder.

Fedora comm card process.png

Note.png
Opening tickets and tracking requests
We are currently using the FAmSCo trac instance. Cc the responsible card holders in trac and choose your region, so we know which region needs the money. If you have questions, contact the FAmSCo trac admin.