[OSGeo-Conf] [Foss4g2013] Should we write a FOSS4G Cookbook?

Jo Cook jocook at astuntechnology.com
Fri Sep 7 05:58:19 PDT 2012

Dear All,

I think there's something to be said for trying to fill in some of the
cookbook as we go along rather than hoping we'll have the time and energy
to do it afterwards. Also, there are several discussion threads about this,
and several people seemingly happy/keen to take responsibility for doing
this, so we're at risk of duplicating effort. It seems as if the best
approach might be to put a basic structure up on the wiki, then we can all
add to it as we think of something appropriate. How does that sound?


On Fri, Sep 7, 2012 at 1:18 PM, Steven Feldman <shfeldman at gmail.com> wrote:

> The Nottingham team are very keen to capture as many of the lessons learnt
> from planning and delivering FOSS4G 2013 as possible.
> We wil be doing the following over the next year
>    - The majority of our internal communications are being logged in
>    Basecamp and will be exported for archiving after we shut down the team
>    - We will be capturing experiences, challenges and lessons learnt as
>    we go along and sharing them via the blog section of
>    http://2013.foss4g.org/ (nothing there yet but will be soon)
>    - Minutes of meetings etc will be available at
>    http://wiki.osgeo.org/wiki/FOSS4G_2013 along with a summary log of
>    lessons learnt
> When we are wrapping up after the event a couple of us (me plus ??) will
> commit time to transferring any useful content from these resources to the
> Cookbook.
> If anyone thinks of better approaches to capturing our experiences chip in
> with suggestions
> Cheers
> Steven
> _____________________
> *
> Steven Feldman*
> _____________________
> On 5 Sep 2012, at 23:34, Cameron Shorter wrote:
> In analysing the downfall of FOSS4G 2012 [1] one of the key lessons that
> became apparent to me is that we are not very efficient at passing on
> Lessons Learned from one conference to the next.
> Could we do a better job of knowledge transfer by building an OSGeo
> Conference Body of Knowledge? Something like a FOSS4G Cookbook [2]?
> If so, what should be the scope of the cookbook? Should it only be for the
> international FOSS4G event? Should it cover regional conferences too?
> Should it also cover FOSS4G steams in other conferences?
> Who thinks this idea is important enough that you would like to help write
> sections of the Cookbook, or help with editing?
> What format should we use to write the Cookbook? Maybe a wiki?
> I'm interested to help push this idea forward if we as a community think
> that there will be value in such a collaboratively edited document.
> If you have an interest, please respond on the OSGeo conference_dev email
> list (rather than OSGeo Discuss)
> [1]
> http://cameronshorter.blogspot.com.au/2012/08/analysing-downfall-of-foss4g-2012.html
> [2] http://wiki.osgeo.org/wiki/FOSS4G_Cookbook
> [3] http://lists.osgeo.org/mailman/listinfo/conference_dev
> --
> Cameron Shorter
> Geospatial Solutions Manager
> Tel: +61 (0)2 8570 5050
> Mob: +61 (0)419 142 254
> Think Globally, Fix Locally
> Geospatial Solutions enhanced with Open Standards and Open Source
> http://www.lisasoft.com
> _______________________________________________
> Conference_dev mailing list
> Conference_dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/conference_dev
> _______________________________________________
> Foss4g2013 mailing list
> Foss4g2013 at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/foss4g2013

***Jo Cook*
Astun Technology Ltd, The Coach House, 17 West Street, Epsom, Surrey, KT18
t:+44 750 095 8167
iShare - Data integration and publishing platform<http://www.isharemaps.com/>


 Company registration no. 5410695. Registered in England and Wales.
Registered office: 120 Manor Green Road, Epsom, Surrey, KT19 8LN VAT no.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20120907/44354f30/attachment.html>

More information about the Conference_dev mailing list