[OSGeo-Conf] Announcements about FOSS4G bid schedule and bid schedule preparation?

Steven Feldman shfeldman at gmail.com
Tue Jun 30 04:45:09 PDT 2015

Some thoughts on the 2017 bid process

Would it help if the Letters of Intent were a bit more detailed? 
We may want to do more early LoI questioning before going to full proposals
If we start process soon, I suggest we allow a longer period for LoI’s - given summer vacations till say mid/end August? Then 2 weeks for questions. Then vote
Letters of Intent - is 2 votes sufficient? Should we consider changing criteria to 25% of votes (round down to whole number)?
Full bids submitted by mid October, then 2-3 weeks for questions and decision by mid November 2015 (approx 21/22 months before event)


> On 24 Jun 2015, at 06:13, Eli Adam <eadam at co.lincoln.or.us> wrote:
> Hi all,
> I've prepared a rough draft for a process outline and new schedule
> [6].  Please review and revise. Otherwise, express some positive
> support.
> I have a few thoughts about the schedule: Do we really want to be
> asking questions and making the decision during FOSS4G 2015?  Should
> we ensure that the decision is *after* FOSS4G 2015 (future FOSS4G
> focus at 2015 should be 2016 not 2017)?
> I've also started a cursory 2017 RFP process in SVN [7].  Please
> update as needed.
> I've prepared a draft for a press release [8], please revise.
> Should we make an OSGeo email alias, rfp at osgeo.org for any private
> communications (likely sponsors)?
> The website RFP page [9] needs to be edited too.  I think that I have
> rights to do this once we decide on details.
> Thanks and best regards, Eli
> [6] http://wiki.osgeo.org/wiki/FOSS4G_2017_Bid_Process
> [7] https://trac.osgeo.org/osgeo/browser/foss4g/rfp/2017
> [8] http://wiki.osgeo.org/wiki/FOSS4G_2017_RFP_Release_Text
> [9] http://www.osgeo.org/conference/rfp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20150630/ea0bc01e/attachment.html>

More information about the Conference_dev mailing list