Difference between revisions of "FOSS4G2008 Workshops"

From OSGeo
Jump to navigation Jump to search
 
(36 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Back to [[FOSS4G2007]]...
 
 
 
== Introduction ==
 
== Introduction ==
 
The FOSS4G2008 Workshop Committee is responsible for the organization of both Workshops and Labs. Workshops are 3-hour classroom sessions, and Labs are 90-minute classes. The committee reports to the FOSS4G2008 Conference Committee.
 
The FOSS4G2008 Workshop Committee is responsible for the organization of both Workshops and Labs. Workshops are 3-hour classroom sessions, and Labs are 90-minute classes. The committee reports to the FOSS4G2008 Conference Committee.
  
 
== FOSS4G Workshop Committee Members ==
 
== FOSS4G Workshop Committee Members ==
* [[User:Racicot | Aaron Racicot]]
+
* [[User:burnie | Burnie Nawn (Coordinator)]]
* [[User:Dpatton | Dave Patton (chair)]]
+
* [[User:Gfleming| Gavin Fleming]]
* [[User:percyd | David Percy]]
+
* [[User:Gmcferren | Graeme McFerren]]
* [[User:Jasonbirch | Jason Birch]]
 
 
* [[User:Jmckenna | Jeff McKenna]]
 
* [[User:Jmckenna | Jeff McKenna]]
* [[User:jive | Jody Garnett ]]
 
* [[User:Pnaciona | Perry Nacionales]]
 
  
 
== Next Committee Meeting ==
 
== Next Committee Meeting ==
 
The date/time for the next meeting is tentative
 
The date/time for the next meeting is tentative
* date: 2007/09/05<br>
+
* date:  
* time: [http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=9&year=2008&hour=12&min=0&sec=0&p1=269 PDT]<br>
+
* time: To be confirmed[]
 
* meeting will be via [[]]
 
* meeting will be via [[]]
 
* Agenda:
 
* Agenda:
Line 22: Line 17:
 
== Previous Committee Meetings ==
 
== Previous Committee Meetings ==
  
== List of workshop submissions ==
+
== List of workshop and lab submissions ==
[[http://wiki.osgeo.org/wiki/FOSS4G2008_Workshop_Submissions#NOTE]]
+
[[FOSS4G2008_Workshop_Submissions#NOTE]]
 +
 
 +
== Final list of workshops and labs ==
 +
[[FOSS4G2008_Workshops_and_Labs]]
  
 
== Criteria used by the workshop committee to review workshop submissions ==
 
== Criteria used by the workshop committee to review workshop submissions ==
Line 30: Line 28:
 
## makes use of software that is both "free" and "open source"  
 
## makes use of software that is both "free" and "open source"  
 
# submission's technical requirements can be met by the conference facilities
 
# submission's technical requirements can be met by the conference facilities
# likelyhood of a quality workshop:
+
# likelihood of a quality workshop:
 
## successful workshop presented at prior FOSS4G conference  
 
## successful workshop presented at prior FOSS4G conference  
 
## expertise of the workshop presenter in the workshop subject matter
 
## expertise of the workshop presenter in the workshop subject matter
## any relevant input from workshop evaluations collected by FOSS4G2006, or personal experience of workshops presented by the presenter(s) at other conferences
+
## any relevant input from workshop evaluations collected by FOSS4G2007, or personal experience of workshops presented by the presenter(s) at other conferences
 
## demonstrates practical applications
 
## demonstrates practical applications
 
# expected level of interest in the workshop topic
 
# expected level of interest in the workshop topic
Line 49: Line 47:
  
 
== Timetable for workshop submissions review process ==
 
== Timetable for workshop submissions review process ==
A private mailing list ("the list") was setup March 7, 2007 for use by the workshop committee.
+
6-9 June; assessent to be completed and workshop presenters notified.
# March 7 to 11
+
immediately thereafter, workshops and other activities are to be put 'on offer' to registrants.
#* on the list, discussions about the review process
+
 
#* all committee members review the documents and get familiar with the workshop submissions
+
== Workshops Notes ==
# March 12
 
#* IRC meeting to finalize review criteria and the 'scoring' system
 
#* committee members start 'scoring' the workshops listed in the "FOSS4G2007 Workshop Submissions-Half Day" spreadsheet
 
# March 15, midnight PDT
 
#* deadline for committee members to provide their 'score' for each of the half-day workshops
 
# March 16
 
#* committee chair creates a summary spreadsheet of the half-day workshop submissions showing each committee member's score for each workshop, and a cumulative 'total score', with the worksheet sorted by 'total score', and make that spreadsheet available to the committee members via Google Docs
 
#* committee members start 'scoring' the workshops in the "FOSS4G2007 Workshop Submissions-90-Minute" spreadsheet
 
#* start discussions, if needed, to adjust the ranked list of half-day workshops
 
# March 18, midnight PDT
 
#* deadline for committee members to provide their 'score' for each of the 90-minute workshops
 
# March 19
 
#* committee chair creates a summary spreadsheet of the 90-minute workshop submissions showing each committee member's score for each workshop, and a cumulative 'total score', with the worksheet sorted by 'total score', and make that spreadsheet available to the committee members via Google Docs
 
#* start discussions, if needed, to adjust the ranked list of 90-minute workshops
 
# March 20, noon PDT
 
#* final deadline for any 'tweaking' of the ranked lists of the half-day and 90-minute workshop submissions
 
#* committee chair prepares the final versions of the relevant documents/spreadsheets, which will be forwarded to the conference organizing committee so they have time to review before their meeting on March 22nd
 
  
 +
=== Workshop Duration and Scheduling ===
  
== Workshops Notes ==
+
Refer to the master programme at [[FOSS4G_2008_Programme]].
 +
The table below is only an indication for placement of labs and workshops.
 +
 
 +
Workshop and Lab Venues:
 +
* '''Venue1''' = CTICC Rooftop Terrace
 +
** 100 Seats
 +
** 50 Computers
 +
** Hired For: 29/30/1/2/3
 +
* '''Venue2''' = CTICC Room 1.40
 +
** 96 Seats
 +
** 48 Computers
 +
** Hired For: 29/30/1/2/3
 +
* '''Venue3''' = CTICC Auditorium
 +
** hundreds of seats, but need to limit to say 40; CTICC will provide tables on top of seats + power supply
 +
** no computers, bring own
 +
** Hired For: 29/2
 +
* '''Venue4''' = University of Cape Town Geomatics Lab
 +
** 44 Seats
 +
** 22 Computers
 +
** Available 29/3
  
'''Note:''' Some of the information below is out of date.
 
  
=== Workshop Duration and Scheduling ===
+
{| border="1"
 +
|+ Workshop and Lab Slots as currently proposed.
 +
!TIME SLOT !!MON Venue1 !! MON Venue2 !! MON Venue3 !! MON Venue4 !! TUE Venue1 !! TUE Venue2 !! WED Venue1 !! WED Venue2 !! THU Venue1 !! THU Venue2 !! FRI Venue1 !! FRI Venue2 !! FRI Venue4
 +
|-
 +
|bgcolor="lightgray"|8am - 10am || bgcolor="#1E90FF"|ws1 || bgcolor="#1E90FF"|ws2 || bgcolor="#1E90FF"|ws3 || bgcolor="#1E90FF"|ws4 || bgcolor="#ABCDEF"|lab1 || bgcolor="#ABCDEF"|lab2 ||  bgcolor="#ABCDEF"|lab9 || bgcolor="#ABCDEF"|lab10 ||  bgcolor="#ABCDEF"|lab17 || bgcolor="#ABCDEF"|lab18 || bgcolor="#1E90FF"|ws5 || bgcolor="#1E90FF"|ws6 || bgcolor="#1E90FF"|ws7
 +
|-
 +
|bgcolor="lightgray"|10:30am - 12pm || bgcolor="#1E90FF"|ws1 || bgcolor="#1E90FF"|ws2 || bgcolor="#1E90FF"|ws3 || bgcolor="#1E90FF"|ws4 || bgcolor="#ABCDEF"|lab3 || bgcolor="#ABCDEF"|lab4 || bgcolor="#ABCDEF"|lab11 || bgcolor="#ABCDEF"|lab12 || bgcolor="#ABCDEF"|lab19 || bgcolor="#ABCDEF"|lab20 || bgcolor="#1E90FF"|ws5 || bgcolor="#1E90FF"|ws6 || bgcolor="#1E90FF"|ws7
 +
|-
 +
|bgcolor="lightgray"|1pm - 2:30pm || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#ABCDEF"|lab5 || bgcolor="#ABCDEF"|lab5 || bgcolor="#ABCDEF"|lab13 || bgcolor="#ABCDEF"|lab14 || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#1E90FF"|ws8 || bgcolor="#1E90FF"|ws9 || bgcolor="#1E90FF"|ws10
 +
|-
 +
|bgcolor="lightgray"|3pm - 4:30pm || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary || bgcolor="#ABCDEF"|lab7 || bgcolor="#ABCDEF"|lab8 || bgcolor="#ABCDEF"|lab15 || bgcolor="#ABCDEF"|lab16 || bgcolor="#FF4500"|Plenary || bgcolor="#FF4500"|Plenary ||bgcolor="#1E90FF"| ws8 || bgcolor="#1E90FF"|ws9 || bgcolor="#1E90FF"|ws10
 +
|-
 +
|bgcolor="lightgray"|5:30pm - 8:30pm || bgcolor="#FF4500"|Cocktail || bgcolor="#FF4500"|Cocktail || bgcolor="#FF4500"|Cocktail ||  bgcolor="#FF4500"|Cocktail || bgcolor="#FFBF00"|maybe || bgcolor="#FFBF00"|maybe || bgcolor="#FF4500"|Gala || bgcolor="#FF4500"|Gala || bgcolor="#FFBF00"|maybe || bgcolor="#FFBF00"|maybe || bgcolor="#FF4500"|OSGEO? || bgcolor="#FF4500"|OSGEO? || bgcolor="#FF4500"|OSGEO?
 +
|}
  
http://www.foss4g2007.org/program_overview.html
+
So, 6 workshops (3-4 hours) and 20 labs (1.5 hours) are planned for. Most submitted proposals are for workshops as opposed to labs (27:16). FOSS4G2007 had 12 workshops and 16 labs. That seems more sensible. So, what are the options?
 +
* We can up the workshops to 8 (Thurs) or 10 (Tues and Thurs) by holding evening sessions from, say, 6-9pm (will attendees come? will presenters want to present then? would it be unfair to make these slots for deeply technical content, e.g. coding?), but that may still not be enough. We have the venues with computers, let's use them if we can in otherwise dead time...
 +
**Gavin: I think Thurs night is good option as main conference is over, Tues is still open for socialising. Full conference package still includes just three 'slots' so if someone now wants to do four (Mon morning, Thurs eve, and two on Fri) they'll need to pay for an extra activity.
 +
* We can break up Venue2 into 2 smaller venues and run a workshop parallel to the 2 lab threads. This means that 25% less people can attend. With evening slots, this would bring workshops up to 13 (Gavin: not a good option - complicates registration packages)
 +
* We can try for offsite venues (maybe without even having to pay for them, though bussing participants would still cost)
 +
**Gavin: we can cover bussing. We can offer free attendance by some staff or students in lieu of payment..
 +
** Centre for High Performance Computing (backup - can only handle a small workshop of max 18 people)
 +
** City of Cape Town GIS Lab
 +
** UCT Geomatics Lab
 +
** University of the Western Cape Computer Lab
 +
* We can try to a secure slightly bigger second venue at the CTICC to be split up - no, it is booked out
 +
* We will use the Auditorium on Monday morning prior to Plenary - can hold a "bring your own computer" workshop.
  
 
=== Hardware ===
 
=== Hardware ===
 
* 40 computers in the rental budget
 
* another 20 slated as loaners from Nanaimo
 
* other options? (bring-your-own etc.)
 
  
 
=== Room Availability ===
 
=== Room Availability ===
?
 
  
 
=== Software Installation ===
 
=== Software Installation ===
* LiveCD for Linux
 
* MS4W installer for Windows
 
* other?
 
* attendees come with laptops and software installed?
 
  
 
=== Other ===
 
=== Other ===
* local person to deal with venue's tech staff?
 
 
  
 
=== Questions for Organising Committee ===
 
=== Questions for Organising Committee ===
 
* Number and dimension of rooms, tables (how many PCs /people can we fit in a room)
 
* Number and dimension of rooms, tables (how many PCs /people can we fit in a room)
 +
** Venue 1 is Roof Terrace and can hold 100 people (50 PCs)
 +
** Venue 2 is Room 1.40 and can hold 96 people (48 PCs)
 +
** Venue 2 can be split into two rooms holding 24 people each (reduced config apparently due to strict fire and building regulations).
 +
***Gavin: how high can we push this by reconfiguring rooms and desks?
 +
****Graeme: cannot be done - these are the allowed sizes - PeopleSA has fought this battle already. Also, there are no bigger venues available for workshops at the CTICC.
 +
** Venue 3 is the main Auditorium. Desks can be fitted for a small cost and power supplied. WiFi access to internet is available. This would be a workshop where attendess supplied own notebook computers, for it would have to be rapidly disassembled afterwards in prep for Opening Plenary.
 +
* Can the Workshops and labs be themed?
 +
** With only two (maybe three venues) it is tricky - perhaps into 1) Desktop GIS and Analysis, 2) Internet GIS
  
 
=== Feedback from Past Conferences (things to note) ===
 
=== Feedback from Past Conferences (things to note) ===
Line 107: Line 128:
 
* LiveCD for linux workshops very successful
 
* LiveCD for linux workshops very successful
 
* grouping workshops by room "theme" successful (MapServer room, GRASS room, ...)
 
* grouping workshops by room "theme" successful (MapServer room, GRASS room, ...)
* foss4g2006 workshops wiki : http://wiki.osgeo.org/index.php/Foss4g2006_wks
+
 
* foss4g2006 workshops rooms : http://wiki.osgeo.org/index.php/FOSS4G2006#Rooms
 
* foss4g2006 number of attendees per workshop : http://www.foss4g2006.org/site/pdf/WksNbOfAttendees.pdf
 
[[Category:FOSS4G2008]]
 
 
[[Category:FOSS4G_Workshops]]
 
[[Category:FOSS4G_Workshops]]

Latest revision as of 04:01, 20 July 2008

Introduction

The FOSS4G2008 Workshop Committee is responsible for the organization of both Workshops and Labs. Workshops are 3-hour classroom sessions, and Labs are 90-minute classes. The committee reports to the FOSS4G2008 Conference Committee.

FOSS4G Workshop Committee Members

Next Committee Meeting

The date/time for the next meeting is tentative

  • date:
  • time: To be confirmed[]
  • meeting will be via [[]]
  • Agenda:

Previous Committee Meetings

List of workshop and lab submissions

FOSS4G2008_Workshop_Submissions#NOTE

Final list of workshops and labs

FOSS4G2008_Workshops_and_Labs

Criteria used by the workshop committee to review workshop submissions

  1. meets conference mandate:
    1. matches with the themes of the conference
    2. makes use of software that is both "free" and "open source"
  2. submission's technical requirements can be met by the conference facilities
  3. likelihood of a quality workshop:
    1. successful workshop presented at prior FOSS4G conference
    2. expertise of the workshop presenter in the workshop subject matter
    3. any relevant input from workshop evaluations collected by FOSS4G2007, or personal experience of workshops presented by the presenter(s) at other conferences
    4. demonstrates practical applications
  4. expected level of interest in the workshop topic

Scoring

The range of scores to be used is 0 through 5:

 0 = does not meet any of the criteria
 1 = barely meets some of the criteria, and doesn't meet some of the criteria
 3 = average
 5 = meets or exceeds all of the criteria

The goal is to end up with a score in the range of 0-5 for the workshop. Two ways to do the scoring:

  1. Use the provided spreadsheet, which allows for a score for each criterion. Divide the "Total Score" by 4 to get the 'score for the workshop'. Doing it this way makes it easy to see any workshops that received a zero for any criterion. Despite the 'total score', workshops that have a zero score for any criterion deserve further examination as to their suitability for the conference.
  2. Use the provided spreadsheet, but just assign an overall score of 0-5 for the workshop. If, as part of doing this, you think a workshop would score zero on any criterion, make a note, and bring it up in the discussions, because workshops that have a zero score for any criterion deserve further examination as to their suitability for the conference.

Timetable for workshop submissions review process

6-9 June; assessent to be completed and workshop presenters notified. immediately thereafter, workshops and other activities are to be put 'on offer' to registrants.

Workshops Notes

Workshop Duration and Scheduling

Refer to the master programme at FOSS4G_2008_Programme. The table below is only an indication for placement of labs and workshops.

Workshop and Lab Venues:

  • Venue1 = CTICC Rooftop Terrace
    • 100 Seats
    • 50 Computers
    • Hired For: 29/30/1/2/3
  • Venue2 = CTICC Room 1.40
    • 96 Seats
    • 48 Computers
    • Hired For: 29/30/1/2/3
  • Venue3 = CTICC Auditorium
    • hundreds of seats, but need to limit to say 40; CTICC will provide tables on top of seats + power supply
    • no computers, bring own
    • Hired For: 29/2
  • Venue4 = University of Cape Town Geomatics Lab
    • 44 Seats
    • 22 Computers
    • Available 29/3


Workshop and Lab Slots as currently proposed.
TIME SLOT MON Venue1 MON Venue2 MON Venue3 MON Venue4 TUE Venue1 TUE Venue2 WED Venue1 WED Venue2 THU Venue1 THU Venue2 FRI Venue1 FRI Venue2 FRI Venue4
8am - 10am ws1 ws2 ws3 ws4 lab1 lab2 lab9 lab10 lab17 lab18 ws5 ws6 ws7
10:30am - 12pm ws1 ws2 ws3 ws4 lab3 lab4 lab11 lab12 lab19 lab20 ws5 ws6 ws7
1pm - 2:30pm Plenary Plenary Plenary Plenary lab5 lab5 lab13 lab14 Plenary Plenary ws8 ws9 ws10
3pm - 4:30pm Plenary Plenary Plenary Plenary lab7 lab8 lab15 lab16 Plenary Plenary ws8 ws9 ws10
5:30pm - 8:30pm Cocktail Cocktail Cocktail Cocktail maybe maybe Gala Gala maybe maybe OSGEO? OSGEO? OSGEO?

So, 6 workshops (3-4 hours) and 20 labs (1.5 hours) are planned for. Most submitted proposals are for workshops as opposed to labs (27:16). FOSS4G2007 had 12 workshops and 16 labs. That seems more sensible. So, what are the options?

  • We can up the workshops to 8 (Thurs) or 10 (Tues and Thurs) by holding evening sessions from, say, 6-9pm (will attendees come? will presenters want to present then? would it be unfair to make these slots for deeply technical content, e.g. coding?), but that may still not be enough. We have the venues with computers, let's use them if we can in otherwise dead time...
    • Gavin: I think Thurs night is good option as main conference is over, Tues is still open for socialising. Full conference package still includes just three 'slots' so if someone now wants to do four (Mon morning, Thurs eve, and two on Fri) they'll need to pay for an extra activity.
  • We can break up Venue2 into 2 smaller venues and run a workshop parallel to the 2 lab threads. This means that 25% less people can attend. With evening slots, this would bring workshops up to 13 (Gavin: not a good option - complicates registration packages)
  • We can try for offsite venues (maybe without even having to pay for them, though bussing participants would still cost)
    • Gavin: we can cover bussing. We can offer free attendance by some staff or students in lieu of payment..
    • Centre for High Performance Computing (backup - can only handle a small workshop of max 18 people)
    • City of Cape Town GIS Lab
    • UCT Geomatics Lab
    • University of the Western Cape Computer Lab
  • We can try to a secure slightly bigger second venue at the CTICC to be split up - no, it is booked out
  • We will use the Auditorium on Monday morning prior to Plenary - can hold a "bring your own computer" workshop.

Hardware

Room Availability

Software Installation

Other

Questions for Organising Committee

  • Number and dimension of rooms, tables (how many PCs /people can we fit in a room)
    • Venue 1 is Roof Terrace and can hold 100 people (50 PCs)
    • Venue 2 is Room 1.40 and can hold 96 people (48 PCs)
    • Venue 2 can be split into two rooms holding 24 people each (reduced config apparently due to strict fire and building regulations).
      • Gavin: how high can we push this by reconfiguring rooms and desks?
        • Graeme: cannot be done - these are the allowed sizes - PeopleSA has fought this battle already. Also, there are no bigger venues available for workshops at the CTICC.
    • Venue 3 is the main Auditorium. Desks can be fitted for a small cost and power supplied. WiFi access to internet is available. This would be a workshop where attendess supplied own notebook computers, for it would have to be rapidly disassembled afterwards in prep for Opening Plenary.
  • Can the Workshops and labs be themed?
    • With only two (maybe three venues) it is tricky - perhaps into 1) Desktop GIS and Analysis, 2) Internet GIS

Feedback from Past Conferences (things to note)

  • overcrowded workshops are bad
  • registrants could possibly list their "top 4" workshop selections
  • LiveCD for linux workshops very successful
  • grouping workshops by room "theme" successful (MapServer room, GRASS room, ...)