<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>I'm definitely interested in a manual too Cameron.  It's not a new idea but is definitely a good one.  I'd check in with Jeff and Arnulf in case they have a start on it already (was on board agenda a few times, and there were some notes that were going into a wiki page, I just can't find them now though).
<br>
<br>Count me in to help, it's something I've wanted to do for a while, especially to help regional event planning and those new to FOSS4G.  The RFP has a ton of good info in it to draw from initially too.
<br>
<br>Peter, I like the idea of reusing and enhancing the website tools too. Having someone you can contract with will be a big help too.  The idea really needs a owner who can also have a budget or a body to oversee it.  Also bidders need to be aware whether they 'should' be expected to use it or not as conf manager companies often want to use their own.  We used a different system for 2008 but I was the only admin (and bottleneck!), so I hope you can get over that hurdle better than I did.
<br>
<br>Tyler
<br>
<br>Tyler
<br>
<br>----- Original message -----
<br>> Hi Cameron, I'm definitely interested in this, FOSS4G has got to a scale
<br>> where we really need this.
<br>>
<br>> One other semi-related item that has been on my mind is extending the web
<br>> site we put together this year, based on Drupal, for use in future
<br>> years. It uses an open source conference management module but we only
<br>> enabled some parts of that. It wouldn't be too much work to get
<br>> Jonathan, who did the site for us, to extend the functionality so it
<br>> could handle the whole abstract submission and selection process (but
<br>> enough work that we would have to pay him something, as we did for his
<br>> initial work).
<br>>
<br>> Managing abstracts was a real pain for us this year with a lot of manual
<br>> work to move them around through the process. They came in through one
<br>> system, we did initial sorting in one spreadsheet, they went to Paul
<br>> Ramsey's voting system then back into another spreadsheet which we
<br>> couldn't easily cross-reference to the previous one, we did some
<br>> duplicate checking in a separate database system, and ended up with two
<br>> spreadsheets for the academic and main tracks, then at the end it was a
<br>> lot of work to schedule the selected papers, notify people, and put the
<br>> info on the web site. And then you have to manage the process of people
<br>> dropping out and filling those slots. Having all these manual steps is
<br>> very error prone too. Finally we now have the question of getting slides
<br>> online, which would be much easier if people could upload their own,
<br>> which they could if we were using this module fully.
<br>>
<br>> This whole process would be massively streamlined if we used the
<br>> conference management module the whole way through.
<br>>
<br>> So anyway, I'm inclined to take a little money from the FOSS4G proceeds
<br>> and get this done for the benefit of future FOSS4Gs. I think this would
<br>> also be a tangible benefit that OSGeo could provide for people doing
<br>> FOSS4G events (global or local) that would help justify the event
<br>> contributing something back to OSGeo from the event proceeds (though
<br>> that's a separate topic).
<br>>
<br>> I'm not quite sure who (if anyone) I need to get permission from to do
<br>> this. I would certainly welcome thoughts from this group. I can check
<br>> with the board if the thought is that I need to do that. Or can just go
<br>> ahead - the amount of money involved is small compared to other budget
<br>> items I've been dealing with on FOSS4G. But obviously I only want to do
<br>> it if others think it's a good idea.
<br>>
<br>> Cheers,
<br>>  Peter.
<br>>
<br>> On Fri, Oct 14, 2011 at 4:52 AM, Cameron Shorter
<br>> <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>>wrote:
<br>>
<br>> > I suggest that we, the conference committee and interested people,
<br>> > should organically start building a FOSS4G Cookbook.
<br>> >
<br>> > The Cookbook should cover all the aspects of putting on a FOSS4G
<br>> > conference, including such things as:
<br>> >
<br>> > * Schedule coming up to the conference
<br>> > * Budget
<br>> > * Program
<br>> > * Web Site
<br>> > * Catering
<br>> > * Venue selection
<br>> >
<br>> > Initially much of the content for this cookbook can be drawn directly
<br>> > from Lessons Learned from previous years. As more events are run, I'd
<br>> > expect ideas to evolve and the Cookbook to grow with it.
<br>> >
<br>> > I see two key advantages of such a Cookbook:
<br>> >
<br>> > 1. Access to such information will make it much easier for someone to
<br>> > put on a FOSS4G conference
<br>> >
<br>> > 2. The Cookbook can be used as a baseline to guide deciding whether a
<br>> > conference may make use of the FOSS4G brand. This will help maintain
<br>> > the quality associated with the FOSS4G brand.
<br>> >
<br>> > Do others see value in building such a document?
<br>> > I'm assuming we should build the Cookbook as a wiki, but am happy to
<br>> > hear suggestions for other collaborative tools.
<br>> > If there is sufficient interest, I'll build a skeleton of the
<br>> > Cookbook, and invite others to contribute content.
<br>> >
<br>> > --
<br>> > Cameron Shorter
<br>> > Geospatial Solutions Manager
<br>> > Tel: +61 (0)2 8570 5050
<br>> > Mob: +61 (0)419 142 254
<br>> >
<br>> > Think Globally, Fix Locally
<br>> > Geospatial Solutions enhanced with Open Standards and Open Source
<br>> > <a href="http://www.lisasoft.com">http://www.lisasoft.com</a>
<br>> >
<br>> > ______________________________**_________________
<br>> > Conference_dev mailing list
<br>> > <a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<br>> > <a href="http://lists.osgeo.org/**mailman/listinfo/conference_**dev<http://lists.osgeo.org/mailman/listinfo/conference_dev>">http://lists.osgeo.org/**mailman/listinfo/conference_**dev<http://lists.osgeo.org/mailman/listinfo/conference_dev></a>;
<br>> >
<br><br></p>
</body>
</html>