Thanks for the guidance. I'll wait a few days, if I hear nothing then I'll start the ball rolling with the mentors regarding payment and mentor summit.
As this summer ends my time administrating GSoC @ Boost, it would be fitting if I attended the mentor summit this year, but it depends heavily on which date Google choose as my wife begins her training to become a chartered accountant at almost the same time, so my childcare duties would rise very significantly thereafter. Niall On 13/06/2017 04:21, Jon Kalb wrote: > Google Summer of Code > > Niall, > > > > Thanks for bring this to attention. I received a copy, but didn’t read > it. It looked to me like it was just a change in the method of > payment. I didn’t realize they were also changing payment policy. > > > > Our agreement with Conservancy is that they take 10% of our revenue, > but there are no terms that require any particular dollar amount, nor > are we bound to any terms that dictate that we do business in such a > way that precludes someone (Google) from making payments to anyone in > the organization (mentors). Conservancy would receive no part of that > exchange, nor would they be entitled to it. > > > > I like this system better because it always annoyed me that whenever a > mentor requested their stipend (which they’ve every right to) the end > result was that Boost gave $50 to Conservancy. It is fair that we give > a portion of our revenue, because we can set up our terms of business > (conference rates for example) with the knowledge that we need to > cover that portion. But for anything that is a pass-through, like the > mentor stipends, it bothers me that we have no control over the > transaction. (I understand that, ultimately, we do have control, we > could insist that Boost retain all or part of the stipends, but that > doesn’t fit very well.) > > > > Of course, the mentor summit stipend and the travel stipends will go > to Conservancy and they’ll be entitled to their portion of that. > > > > The only thing that isn’t clear to me is if Google will identity funds > that are given to Conservancy through this program as due to the Boost > project, but my guess is that Bradley will correctly identify all the > funds received and allocate them appropriately. > > > > I don’t see any other issues. Is there something I’m missing? > > > > I just sent a copy of this to Bradley, Brett, and Tony for their comments. > > > > Thanks again for everything. > > > > Jon > > > > *From: *Niall Douglas <[email protected]> on behalf of Niall Douglas > <[email protected]> > *Reply-To: *Boost Steering Committee <[email protected]> > *Date: *Monday, June 12, 2017 at 4:10 PM > *To: *Boost Steering Committee <[email protected]> > *Subject: *[boost-steering] Fwd: GSoC 2017: Payment Instructions for > Stipends for GSoC 2017 > > > > Can I ask for the steering committee's opinion on the below? > > In short, Google now pay the mentors directly, but I appreciate that > this would cause issue for the SFC to claim its 10%. > > It would also appear that they now wish to give us $2,500 irrespective > of whether we send mentors to the summit or not, and $500 towards any > of our students attending any C++ conference. Which is very generous > of them. > > Should we still upcall this to Bradley, or take care of it ourselves > individually as the below instructions indicate we should? > > Niall > > -------- Forwarded Message -------- > > *Subject: * > > > > GSoC 2017: Payment Instructions for Stipends for GSoC 2017 > > *Date: * > > > > Mon, 12 Jun 2017 10:30:05 -0700 > > *From: * > > > > Google Summer of Code <[email protected]> > <mailto:[email protected]> > > *To: * > > > > [email protected] <mailto:[email protected]> > > > > > > > > oogle Summer of Code > > > > Hi Niall Douglas-1, > > You are receiving this email because you are an Organization > Administrator for your org for GSoC 2017. If you are not the correct > person to complete the payment request form as described below please > be sure this information is passed along to the correct person. Please > be sure only one person from your org completes the form. Thanks. > > If you have any questions please email us [email protected] > <mailto:[email protected]> > > GSoC team > > *Payment Instructions for GSoC 2017 Organizations* > > ------------------------------------------------------------------------ > > Starting this year we are using Payoneer, a financial services > company, to pay Google Summer of Code Organizations. We are confident > that Payoneer is faster, more intuitive and convenient than the old > payment process. No PO's, no invoices, no waiting for your money. > Thousands of GSoC students have been using Payoneer for years and > we're excited to bring it to you! > > *I. Included in your payment:* > > * $500 per student developer for your organization (often called the > mentor stipend) > * $2200 mentor summit stipend** > * $500 for each organization to send a student(s) or mentor(s) to > your conference or meeting (or a related conference)*** > > *II. How to claim your payment:* > > 1. Fill out the payment request form > > <https://docs.google.com/forms/d/e/1FAIpQLSevQ32PUU73Pvb953WrqoLWQyHWFQC6nqiFJzFsAyeND3SHDg/viewform?usp=sf_link> > by Friday, June 23 - you must include the email address for the > *person responsible for accepting payment* at your organization. > 2. By June 30th Google Program Admins will send a registration token > link via email to the person responsible for accepting payment. > *Important: only register with the link that is sent by Payoneer. > Do not sign up directly on the Payoneer website *as this will > cause all kinds of problems and delays for you and us. > > 3. Once the registration link is received, the designated person > responsible for accepting payment will follow the one-time > registration instructions on the Payoneer website. > > a. Once the account has been approved by Payoneer (usually takes 305 > business days), the designee will receive an email with a link to > complete their tax form. This must be completed by August 1. > > b. Organizations may choose to be paid via direct wire transfer to a > bank account or via a pre-paid card. > > 4. Payoneer will transfer all funds by September 30. No invoices, > etc. are necessary anymore. > > *III. Important Dates* > > * *June 23 - *Complete the payment request form > > <https://docs.google.com/forms/d/e/1FAIpQLSevQ32PUU73Pvb953WrqoLWQyHWFQC6nqiFJzFsAyeND3SHDg/viewform?usp=sf_link> > * *By June 30 - *Google Program Admins will send out all > registration tokens > * *August 1 - *Complete**Registration with Payoneer (including tax form) > * *September 30 - *All organizations paid > > *IV. Frequently Asked Questions* > > *I already have a Payoneer account - can I use that?* > > Yes. If you have an active account and have received funds via > Payoneer in the past, just click on "/Already Have a Payoneer > Account/" after clicking on the registration link we send you. > This will link the two accounts. > > *It says my Payoneer account is not linked to the Google Summer of > Code program. How do I fix that?* > > This means you did not register via the link sent to you from > Payoneer. Please contact Payoneer directly and let them know you > are part of the GSoC 2017 org distribution - it can take several > weeks to get sorted out. > > *What tax form am I required to complete?* > > We cannot provide any tax advice. As you go through the tax form > widget on the Payoneer website it asks questions which will help > you determine which form you need to complete. > > *I need to change or update my bank account in Payoneer. How do I do > this?* > > You can go to your Payoneer dashboard and update your account as > needed. > > *My organization is based in India and I am not able to choose the > prepaid card option on the Payoneer website. What's going on?* > > At this time, the pre-paid card option is not available in India. > You must choose a direct bank transfer instead. > > *I am having problems setting up my account. Where can I go for help?* > > If you have any questions regarding your Payoneer account, please > be sure to contact Payoneer directly via their contact page > > <https://payouts.payoneer.com/Partners/Default/ContactUs.aspx?pid=100049490>. > You can also use the link in your Payoneer "/My Account"/ page. > Payoneer offers multilingual customer support for all payment > related issues via e-mail, telephone and live chat. > If your card is lost or stolen, please contact Payoneer > immediately so it can be disabled and and a new card will be sent > to you. > > *I'm an individual claiming money on my organization's behalf. Can I > still be paid by Payoneer?* > > Yes, you can be paid by Payoneer and set up the account in your > name to receive the funds on behalf of the organization. Accepting > such a payment will likely affect the receiver's taxation status > and you should consult with a tax professional for any questions > about how accepting these payments will affect you/your organization. > > You may also want to consider joining the Software Freedom > Conservancy <https://sfconservancy.org/> (or a similar > organization) that can provide infrastructure for FLOSS projects > and can help you manage the payment process. > > *What if my organization doesn't want to accept funds?* > > Please complete the payment request form > > <https://docs.google.com/forms/d/e/1FAIpQLSevQ32PUU73Pvb953WrqoLWQyHWFQC6nqiFJzFsAyeND3SHDg/viewform?usp=sf_link> > even if you do not plan to accept any money from Google. There you > will have the option of declining funds, so you will not receive a > link from Payoneer. We ask that you consider donating your funds > to Software Freedom Conservancy <https://sfconservancy.org/> and > we can do so on your behalf. > > *What if my organization would like to donate these funds? * > > We are happy to donate your funds directly to Software Freedom > Conservancy <https://sfconservancy.org/>, but we can not issue > payment to another charity/non-profit for you. You are welcome to > accept the funds and then distribute them yourself. > > *What if we need to change the email address associated with our > initial registration?* > > Google will submit payments based on the email address provided in > the payment request form (which becomes the identifier for your > org). If you decide to change that email address after > registration you must contact [email protected] > <mailto:[email protected]> so we can update it on our end. > If you are the person in charge of receiving payments for two or > more orgs then you should notify Google Admins so we can make > special accommodations for your multiple payments. > > *Can we only accept the travel funds and not the mentor stipends, or > vice versa? * > Yes, you can only accept partial payment. You just need to note in the > last field on the Payment Request form "Anything else we need to know > about your payment?" which funds you want to accept and which you wish > to decline. > > ** The mentor summit stipend is paid regardless of whether you plan to > send 0, 1 or 2 mentors to our annual summit. The stipend will be > reduced by half if any evaluations are missed during the program. The > stipend will be reduced to $0 if 2 or more evaluations are missed. > > *** New for 2017. We realize many of you have meetings and other > events that you would like to invite your students to - we hope this > will help you get some of the students to these events and to > integrate them even more with your community. > > > > > > > > > This email was sent to [email protected]. > > You are receiving this email because of your participation in Google > Summer of Code 2017. > https://summerofcode.withgoogle.com > > To leave the program and stop receiving all emails, you can go to your > profile <https://summerofcode.withgoogle.com/dashboard/profile/> and > request deletion of your program profile. > > For any questions, please contact [email protected] > <mailto:[email protected]>. Replies to this message go to an > unmonitored mailbox. > > © 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA > 94043, USA > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google > Groups "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/boost-steering. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/e0bd0500-0261-785a-dcfa-15e33e269921%40boost.org > <https://groups.google.com/d/msgid/boost-steering/e0bd0500-0261-785a-dcfa-15e33e269921%40boost.org?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout. > -- The Boost Steering Committee webpage: https://sites.google.com/a/boost.org/steering/ --- You received this message because you are subscribed to the Google Groups "Boost Steering Committee" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/boost-steering. To view this discussion on the web visit https://groups.google.com/d/msgid/boost-steering/b80968f4-3f6c-a453-6643-e91acfc7ebde%40boost.org. For more options, visit https://groups.google.com/d/optout.
