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.
Subject: | GSoC 2017: Payment Instructions for Stipends for GSoC 2017 |
---|---|
Date: | Mon, 12 Jun 2017 10:30:05 -0700 |
From: | Google Summer of Code <summerofco...@google.com> |
To: | ni...@boost.org |
|
|
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 <ni...@boost.org> on behalf of Niall Douglas <gsoc-...@boost.org>
Reply-To: Boost Steering Committee <boost-s...@googlegroups.com>
Date: Monday, June 12, 2017 at 4:10 PM
To: Boost Steering Committee <boost-s...@googlegroups.com>
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 <summerofco...@google.com> |
To: |
|
|
|
|
--
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 boost-steerin...@googlegroups.com.
To post to this group, send email to boost-s...@googlegroups.com.
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.
For more options, visit https://groups.google.com/d/optout.