May 2019 - Budget-devel - Fedora Mailing-Lists

[fedora-budget] PR #54: APAC FY18 Entries

by P J P

pjp opened a new pull-request against the project: `fedora-budget` that you are following: `` APAC FY18 Entries `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-budget/pull-request/54

3 years, 8 months

3
3
0 / 0

[fedora-budget] PR #55: F28 release part Bengaluru entry

by P J P

pjp opened a new pull-request against the project: `fedora-budget` that you are following: `` F28 release part Bengaluru entry `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-budget/pull-request/55

3 years, 8 months

3
3
0 / 0

[fedora-budget] branch master updated: NA CC Reconcile

by pagure＠pagure.io

This is an automated email from the git hooks/post-receive script. bex pushed a commit to branch master in repository fedora-budget. The following commit(s) were added to refs/heads/master by this push: new 1035ee4 NA CC Reconcile 1035ee4 is described below commit 1035ee48ab7bc971dff6b95f1271fbc00fb8fb47 Author: Brian (bex) Exelbierd <bex(a)pobox.com> AuthorDate: Thu May 30 13:18:03 2019 +0200 NA CC Reconcile --- FY20/ledger/mindshare.ldg | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/FY20/ledger/mindshare.ldg b/FY20/ledger/mindshare.ldg index 8dcda31..95bae8c 100644 --- a/FY20/ledger/mindshare.ldg +++ b/FY20/ledger/mindshare.ldg @@ -18,7 +18,7 @@ Mindshare:Q1 $0 Mindshare:Q1:Chemintzer Linux Tage -$330 ; https://pagure.io/mindshare/issue/96 Mindshare:Q1:openSUSE -$222 ; https://pagure.io/mindshare/issue/88 (portion remaining in FY20) - Mindshare:Q1:LFNW -$60 ; https://pagure.io/mindshare/issue/84 (portion remaining in FY20) + Mindshare:Q1:LFNW -$60 ; https://pagure.io/mindshare/issue/84 (portion remaining in FY20) and #118 Mindshare:Q1:SCALE -$68.22 ; Shipping Mindshare:Q1:SCALE -$1955 ; https://pagure.io/mindshare/issue/82 Mindshare:Q1:Cambodia Translation Sprint -$100 ; https://pagure.io/mindshare/issue/120 @@ -75,3 +75,8 @@ Expense:Lodging $326.58 Expense:Airfare $359.80 Mindshare:Q1:SCALE -$686.38 + +2019-05-10 * UPS Shipping for event box + ; Payment: NA CC - May + Expense:Shipping $65.96 + Mindshare:Q1:LFNW -$65.96 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 years, 11 months

1
0
0 / 0

[fedora-budget] branch master updated: fix formatting errors

by pagure＠pagure.io

This is an automated email from the git hooks/post-receive script. bex pushed a commit to branch master in repository fedora-budget. The following commit(s) were added to refs/heads/master by this push: new f32638a fix formatting errors f32638a is described below commit f32638a161aa5c57ba51a253883df947a4ce2725 Author: Brian (bex) Exelbierd <bex(a)pobox.com> AuthorDate: Wed May 29 12:54:14 2019 +0200 fix formatting errors --- docs/reimbursement.adoc | 36 ++++++++++++++++++------------------ 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/reimbursement.adoc b/docs/reimbursement.adoc index e7b97a5..48778ff 100644 --- a/docs/reimbursement.adoc +++ b/docs/reimbursement.adoc @@ -20,28 +20,28 @@ Carefully review these and ensure you can make use of one of them **before** you See below for more details and for information about what to do if these ways don't work. * PayPal.com - Preferred method - - Paypal reimbursements require us to have your PayPal email address. - We try to send the money via "Send to a Friend" so that the Project pays any fees and penalties accessed by Paypal. - If we can't send it with the fees paid by Fedora we need you to tell us what the fees are for your country, with links, and we will gross up your reimbursement to cover them. - We will send the money in your currency of choice, if possible. - If not you will get USD. - Red Hat employeess may not use this option. ++ +Paypal reimbursements require us to have your PayPal email address. +We try to send the money via "Send to a Friend" so that the Project pays any fees and penalties accessed by Paypal. +If we can't send it with the fees paid by Fedora we need you to tell us what the fees are for your country, with links, and we will gross up your reimbursement to cover them. +We will send the money in your currency of choice, if possible. +If not you will get USD. +Red Hat employeess may not use this option. * Transferwise.com - - Transferwise reimbursements require us to have either the email address you have already registred with them or your account details. - See the ticket template for details - In some cases, even if you pre-register with Transferwise.com we are required to get additional details from you. - We send the money with all fees paid by the Project. - We will send the money in your currency of choice, if possible. - If not you will get USD. - Red Hat employeess may not use this option. ++ +Transferwise reimbursements require us to have either the email address you have already registred with them or your account details. +See the ticket template for details +In some cases, even if you pre-register with Transferwise.com we are required to get additional details from you. +We send the money with all fees paid by the Project. +We will send the money in your currency of choice, if possible. +If not you will get USD. +Red Hat employeess may not use this option. * Red Hat Internal Reimbursements - - Red Hat employees are required to use internal reimbursement procedures in almost all cases. - Please contact the FCAIC for details. ++ +Red Hat employees are required to use internal reimbursement procedures in almost all cases. +Please contact the FCAIC for details. === How long does it take to get paid? -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 years, 11 months

1
0
0 / 0

[fedora-budget] branch master updated: updating reimbursement rules

by pagure＠pagure.io

This is an automated email from the git hooks/post-receive script. bex pushed a commit to branch master in repository fedora-budget. The following commit(s) were added to refs/heads/master by this push: new ae2ebfe updating reimbursement rules ae2ebfe is described below commit ae2ebfec093701ebe987ed66c3f227076e58c144 Author: Brian (bex) Exelbierd <bex(a)pobox.com> AuthorDate: Wed May 29 12:41:37 2019 +0200 updating reimbursement rules --- docs/reimbursement.adoc | 65 +++++++++++++++++++++++++++++++++++-------------- 1 file changed, 47 insertions(+), 18 deletions(-) diff --git a/docs/reimbursement.adoc b/docs/reimbursement.adoc index da694cc..e7b97a5 100644 --- a/docs/reimbursement.adoc +++ b/docs/reimbursement.adoc @@ -1,26 +1,55 @@ -Reimbursement Policies -====================== += Reimbursement Policies + +== Requirements for Reimbursements **Note: Subgroups are free to add additional requirements that are more strict than the ones outlined below.** -Holding with our current policies, reimbursement will depend on submission of an Event Report to the appropriate channels (mail lists, community blog, and the planet/magazine when applicable. If you attend a FAD you should write your report relative to the FAD. In general every funded person is expected write a separate report unless it is demonstrated that they all contributed to the larger overall reporting. +Minimally, the following requirements must be met in order to be reimbursed by Fedora: + +* You must have permission from a part of Fedora that authorizes spending money. +The Budget Team does **not** authorize spending money, we only manage the reimbursement process. +Teams authorizing spending are groups such as the Fedora Council, Mindshare, and Diversity and Inclusion. +You should share your idea with them and get approval from them. +* You typically have to write an event/activity report of some form. +This will be detailed by the group that approves your funding, but this is something the budget team will typically look for. + +== Getting your Reimbursement + +Fedora processes almost all reimbursements in one of three ways. +Carefully review these and ensure you can make use of one of them **before** you spend money. +See below for more details and for information about what to do if these ways don't work. + +* PayPal.com - Preferred method + + Paypal reimbursements require us to have your PayPal email address. + We try to send the money via "Send to a Friend" so that the Project pays any fees and penalties accessed by Paypal. + If we can't send it with the fees paid by Fedora we need you to tell us what the fees are for your country, with links, and we will gross up your reimbursement to cover them. + We will send the money in your currency of choice, if possible. + If not you will get USD. + Red Hat employeess may not use this option. + +* Transferwise.com + + Transferwise reimbursements require us to have either the email address you have already registred with them or your account details. + See the ticket template for details + In some cases, even if you pre-register with Transferwise.com we are required to get additional details from you. + We send the money with all fees paid by the Project. + We will send the money in your currency of choice, if possible. + If not you will get USD. + Red Hat employeess may not use this option. + +* Red Hat Internal Reimbursements -Event reports include a very short list of bullet points. These bullet points are the necessary ammunition we need to reinforce our proposals to increase funding for regional programs in the future. These bullet points should cover two areas, *Action* and *Impact*. + Red Hat employees are required to use internal reimbursement procedures in almost all cases. + Please contact the FCAIC for details. -Action is any typical or special activity that ambassadors lead regionally such as: +=== How long does it take to get paid? -- Tabling at Conferences, Conventions, or other large events -- Presenting/Representing Fedora at Local Meetups -- Organizing FADS, Workshops, or other Fedora-specific Events +We try to pay all reimbursements within 2 weeks of the budget ticket getting opened and all information required received. -Impact includes the outcomes from the activities as above. This includes things like: +=== What about Currency Conversion? -- Attendees contacted or reached -- Fedora Badges issued at or as a result of the event -- Pull requests and patches submitted as a result of event -- Bugs reported/Tickets Filed -- Candidates sourced (i.e. Outreachy, GSoC, and/or other FOSS programs) -- Articles/Videos/Photos/Content published by or about regional team -- Social media mentions and interactions generated by event -- Other supporting evidence data that shows the results of your effort -- Links to and reach of posts on Fedora social media and publishing channels +We ask that you not convert currencies when you report your expenses. +We do our work in your local currency when calculating the reimbursement. +We try to pay all reimbursements in your preferred currency. +When this isn't possible we will work with you on currency conversion fees. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 years, 11 months

1
0
0 / 0

[fedora-budget] Issue #34: Enable translation via Zanata

by Brian Exelbierd (bex)

bex added a new comment to an issue you are following: `` working on conversion to antora so we can leverage the docs system here. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-budget/issue/34

4 years, 11 months

1
0
0 / 0

[fedora-budget] branch master updated: docs hack

by pagure＠pagure.io

This is an automated email from the git hooks/post-receive script. bex pushed a commit to branch master in repository fedora-budget. The following commit(s) were added to refs/heads/master by this push: new 066bc31 docs hack 066bc31 is described below commit 066bc317143e49e2856754393c52192506a27488 Author: Brian (bex) Exelbierd <bex(a)pobox.com> AuthorDate: Thu May 16 14:10:31 2019 +0200 docs hack --- FY20/ledger/council.ldg | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/FY20/ledger/council.ldg b/FY20/ledger/council.ldg index 24fcb90..c0a0d94 100644 --- a/FY20/ledger/council.ldg +++ b/FY20/ledger/council.ldg @@ -20,10 +20,18 @@ ; Budget:GSoC $5700 ; Mentored Projects:Unallocated -$5700 ; received on 11 Sept 2018 -;~ every 2 years +~ every 2 years + Council:Hack:Docs Internationalization -$650 ; https://pagure.io/Fedora-Council/tickets/issue/250 + Council:Unallocated ; Council:Other:Podcast -$1400 ; https://pagure.io/Fedora-Council/tickets/issue/195 ; Council:Other:Podcast -$183 ; https://pagure.io/Fedora-Council/tickets/issue/192 ; Council:Discourse -$3600 ; discussions instance ; Council:Discourse -$3600 ; ask instance -; Council:Unallocated +2019-04-25 * Adam Samalilk + ; Payment: IE4432050 - Samalik + Expense:Lodging $223.36 + Expense:Airfare $270.84 + Expense:Train $188.90 + Expense:Business Meals $292.53 + Council:Hack:Docs Internationalization -$975.63 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 years, 11 months

1
0
0 / 0

[fedora-budget] branch master updated: Mindshare reconcilliation

by pagure＠pagure.io

This is an automated email from the git hooks/post-receive script. bex pushed a commit to branch master in repository fedora-budget. The following commit(s) were added to refs/heads/master by this push: new 254eda2 Mindshare reconcilliation 254eda2 is described below commit 254eda223f72895e0abb4f2a489035a0defadb2d Author: Brian (bex) Exelbierd <bex(a)pobox.com> AuthorDate: Thu May 16 13:47:09 2019 +0200 Mindshare reconcilliation --- FY20/ledger/mindshare.ldg | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/FY20/ledger/mindshare.ldg b/FY20/ledger/mindshare.ldg index bdcc5f1..8dcda31 100644 --- a/FY20/ledger/mindshare.ldg +++ b/FY20/ledger/mindshare.ldg @@ -64,3 +64,14 @@ ; Payment: IE4379055 Expense:Lodging $268.43 Mindshare:Q1:Chemintzer Linux Tage + +2019-04-18 * Amita Sharma + ; Payment: RHIPL441239 - Amita Sharma + Expense:Airfare $1016.65 ; 71224 INR + Mindshare:Q1:OSCAL -$1016.65 + +2019-05-06 * Alex A Costa + ; Payment: IE4580768 + Expense:Lodging $326.58 + Expense:Airfare $359.80 + Mindshare:Q1:SCALE -$686.38 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 years, 11 months

1
0
0 / 0

[fedora-budget] branch master updated: add budget

by pagure＠pagure.io

This is an automated email from the git hooks/post-receive script. bex pushed a commit to branch master in repository fedora-budget. The following commit(s) were added to refs/heads/master by this push: new 79b8384 add budget 79b8384 is described below commit 79b838463153e096af772efb0a4b6e2ec687dab1 Author: Brian (bex) Exelbierd <bex(a)pobox.com> AuthorDate: Thu May 16 10:33:38 2019 +0200 add budget --- FY20/ledger/council.ldg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FY20/ledger/council.ldg b/FY20/ledger/council.ldg index 909a79a..24fcb90 100644 --- a/FY20/ledger/council.ldg +++ b/FY20/ledger/council.ldg @@ -2,7 +2,7 @@ ; Budgets and Movements ;---------------------------------------------------------------------------------- ~ every 2 years - Budget:Red Hat:Public $0 ; Budget for FY20 is not yet set + Budget:Red Hat:Public $196000 ; budget for FY20 Flock -$0 ; 95000 Mindshare:Unallocated -$0 ; 27637 ; Q2-4 + RP from Ambassadors Diversity-Inclusion:Unallocated -$0 ; 15500 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

Budget-devel May 2019