[Board] [OSGeo-Discuss] Funding code Sprints

[Venkatesh Raghavan]

Hi Patrick,

On 2/22/2016 9:32 AM, Hogan, Patrick (ARC-PX) wrote:
> Venka,
>
> Howdy! Any reason why the Paris Code Sprint couldn’t include the Europa Challenge criteria?

I am not sure that I understand what you mean by "include the Europa 
Challenge criteria".
Since the Europa Challenge is open to all [1], I do not see any reason 
why the project
team or individuals participating in the code sprint cannot send in 
their entries  for
the Europa Challenge.

I would encourage you (or Maria) to send the info about the Europa 
Challenge to the
Code Sprint ML [2] (I am not subscribed to the list). You request the 
organizers to
print the Europa Challenge brochure [3] and leave copies at the registration
desk of the Code Sprint venue to increase visibility amongst the Paris Code
Sprinters.

Best

Venka

[1] http://eurochallenge.como.polimi.it/
[2] https://lists.osgeo.org/mailman/listinfo/tosprint
[3] 
http://eurochallenge.como.polimi.it/sites/default/files/Europa_Challenge-Flyer.pdf
>
> They would simply use the Europa Challenge criteria submit their results there in addition to the Paris Code Sprint!
>
> Then that code sprint would be getting *double exposure* and have a shot at the NASA Crystal Bull, http://eurochallenge.como.polimi.it/
>
> That’s two finish lines for the price of one sprint!
>
> We will treat Code Sprinters as grad students or SME, no mentor required.
>
> -Patrick
> (650) 604-5656 (office)
> (650) 269-2788 (cell)
>
> From: Discuss [mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Venkatesh Raghavan
> Sent: Sunday, February 21, 2016 3:35 PM
> To: OSGeo Discussions; OSGeo Board
> Subject: Re: [OSGeo-Discuss] [Board] Funding code Sprints
>
> Dear All,
>
> Considering OSGeo budget for 2016, I think, it could be
> possible to support 3 or 4 Code Sprints at similar
> sponsorship levels for each sprint as in the past.
>
> I would like to propose to have code spread across three or four
> periods across the year e.g Jan-March, April-June, July-Sept, Oct-Dec
> and have RFP's for code sprints just like we have for our annual
> conference.
>
> OSGeo Code Sprint in Paris starting from today (22 Feb., 2016),
> fits very well for the  first quarter of 2016. I see a great lineup
> of projects and participants for the Paris Code Sprint [1].
>
> Code sprints are an integral part of FOSS4G Conferences which is our
> largest gathering of users and developers. It will be appropriate that
> OSGeo Foundation supports Code Sprints at FOSS4G conferences as
> an official event for the July-September period.
>
> Best
>
> Venka
>
> [1] https://wiki.osgeo.org/wiki/Paris_Code_Sprint_2016
>
>
> On 2016/02/20 18:07, Massimiliano Cannata wrote:
>
> Dear All,
>
> this is to acknowledge that there is a topic on discussion within the board
>
> directors on assigning funds to sprint code requests.
>
>
>
> Up to now a request-voting-fund approach has been followed without any
>
> specific plan.
>
> Since the board f2f meeting (thank you community for supporting that as i
>
> believe it was an enormous opportunity for OSGeo to speed up advances and
>
> was so fruitful) a budget has been draft and resources has been allocated.
>
>
>
> With this mail I would personally like to ask a few questions the different
>
> communities:
>
>
>
> - who is intended to present a fund request for sprint code in 2016. This
>
> will give an idea of the number of expected requests.
>
>
>
> - do you have preferences on criteria for assign resources and eventually
>
> what is your choice motivation?
>
>
>
>
>
> Thank you,
>
>
>
> Maxi
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> Board mailing list
>
> Board at lists.osgeo.org<mailto:Board at lists.osgeo.org>
>
> http://lists.osgeo.org/mailman/listinfo/board
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20160222/c52caf31/attachment.htm>