[OSGeo-Conf] R: [Board] Board Digest, Vol 128, Issue 5

Steven Feldman shfeldman at gmail.com
Sat May 6 09:56:38 PDT 2017


The problem is that for a global FOSS4G the travel grant programme has to be announced long before the LOC has a clear picture of the likely financial outcome of the event.

If OSGeo wants there to be a travel grant programme for the global event and possibly for other events then it needs to set aside a budget to cover this important outreach. After all, the surplus from the global event (if there is one) will be largely returned to OSGeo. 

You "prefer a collaborative approach with sponsors and partnerships." Who are you suggesting seeks these sponsors or partners? I would be concerned if CC were trying to raise sponsorship for travel grants at the same time (and potentially from the same targets) as the LOC are trying to raise sponsorship for their event. 

If the CC are going to run a travel grant programme for 2017, we need to get started soon and we will need a budget allocation from somewhere, there isn't time to start seeking a partner or sponsor. For 2018 and beyond we can make a budget submission to the board and could also explore the possibility of a partner or sponsor. 

Alternatively we could alter the RfP for future global events (2019 onwards) to make the funding of a travel grant programme mandatory for applicant teams. It's difficult to say whether the mandatory inclusion of travel grants would discourage bids, increase ticket prices or just reduce surpluses to OSGeo. Perhaps past chairs would like to express an opinion on this

I suggest that we start by only running a grant programme for the global event and leave the regional and local events to their organisers. 



Steven


> On 6 May 2017, at 07:47, Maria Antonia Brovelli <maria.brovelli at polimi.it> wrote:
> 
> Dear Jody and All
> I share the same thought:
> 
>   "I am not sure how comfortable I am with OSGeo taking on 100% of the funding for this activity - I prefer to a collaborative approach with sponsors and partnerships.
> Let us discuss it in the next Board meeting and then we'll vote in Loomio.
> Best,
> Maria 
> 
> 
> 
> 
> Inviato dal mio dispositivo Samsung
> 
> 
> -------- Messaggio originale --------
> Da: Jody Garnett <jody.garnett at gmail.com> 
> Data: 05/05/17 22:08 (GMT+01:00) 
> A: Steven Feldman <shfeldman at gmail.com> 
> Cc: OSGeo Board <board at lists.osgeo.org> 
> Oggetto: Re: [Board] Board Digest, Vol 128, Issue 5 
> 
> Translating - "terms of reference" --> I am going to guess you mean the updating the motion that created the conference committee and provided it a mandate to function. Checking online I can find "goals" but not a mandate, the wiki lists responsibilities which is an improvement. Does anyone have the initial motion that created the conference committee handy?
> 
> I am fine with the board handing over responsibility, conference committee is in a much better position (and has more appropriate experience) to run a travel grant program.
> 
> I will push back on the board determining "level of travel grant funding" as I would expect this to be included as part of conference committee budget request, or part of an initiative budget request if you choose to run in collaboration with sponsorship. I am not sure how comfortable I am with OSGeo taking on 100% of the funding for this activity - I prefer to a collaborative approach with sponsors and partnerships.
> --
> Jody Garnett
> 
>> On 5 May 2017 at 10:20, Steven Feldman <shfeldman at gmail.com> wrote:
>> I suggest that the Board extends ConfCom terms of reference and then leaves CC to work out how to implement a policy
>> 
>> Board will need to determine the level of travel grant funding for each budget year
>> ______
>> Steven
>> 
>> 
>>> On 5 May 2017, at 16:28, board-request at lists.osgeo.org wrote:
>>> 
>>> Send Board mailing list submissions to
>>> board at lists.osgeo.org
>>> 
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> https://lists.osgeo.org/mailman/listinfo/board
>>> or, via email, send a message with subject or body 'help' to
>>> board-request at lists.osgeo.org
>>> 
>>> You can reach the person managing the list at
>>> board-owner at lists.osgeo.org
>>> 
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Board digest..."
>>> 
>>> 
>>> Today's Topics:
>>> 
>>>   1. Re: [OSGeo-Conf] FOSS4G Boston Travel Grants ~ IMPORTANT
>>>      request (Jody Garnett)
>>>   2. Re: [OSGeo-Conf] FOSS4G Boston Travel Grants ~ IMPORTANT
>>>      request (Jody Garnett)
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> 
>>> Message: 1
>>> Date: Fri, 05 May 2017 06:31:00 +0000
>>> From: Jody Garnett <jody.garnett at gmail.com>
>>> To: Till Adams <till.adams at fossgis.de>, "board at lists.osgeo.org"
>>> <board at lists.osgeo.org>
>>> Subject: Re: [Board] [OSGeo-Conf] FOSS4G Boston Travel Grants ~
>>> IMPORTANT
>>> request
>>> Message-ID:
>>> <CAOhbgA=KQposibj23ZkTfrttLAyGa4p74BCF1vuyR7iAKsaTOA at mail.gmail.com>
>>> Content-Type: text/plain; charset="utf-8"
>>> 
>>> Excellent, so would the idea be to update the conference committee mandate
>>> then?
>>> 
>>> Or would the conference committee set this up as indicative (for program
>>> visibility and sponsorship)? ... similar to how the website/rebranding is
>>> being taken on as a one-off by the marketing committee.
>>> 
>>> That is a bit of a strategic question so it may require thought / planning.
>>> 
>>> 
>>> On Thu, May 4, 2017 at 11:19 PM Till Adams <till.adams at fossgis.de> wrote:
>>> 
>>>> Hi Jody,
>>>> 
>>>> I would propose to post this responsibility to the ConfCom. Some of the
>>>> past chairs already were involved in such kind of decisions.
>>>> 
>>>> Till
>>>> 
>>>> 
>> 
>> 
>> _______________________________________________
>> Board mailing list
>> Board at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/board
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20170506/900bba39/attachment.html>


More information about the Conference_dev mailing list