Difference between revisions of "User talk:Dpatton"
Jump to navigation
Jump to search
Wiki-Dpatton (talk | contribs) (add suggested timetable) |
Wiki-Dpatton (talk | contribs) (add second suggestion for workshop review process) |
||
Line 27: | Line 27: | ||
#* final deadline for any 'tweaking' of the ranked lists of the half-day and 90-minute workshop submissions | #* 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 | #* 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 | ||
+ | |||
+ | |||
+ | |||
+ | == Second version of a possible method to review workshop submissions == | ||
+ | * workshop committee establishes a list of 'review criteria' | ||
+ | * the only criteria used when workshop committee members review workshop submissions are the 'review criteria' | ||
+ | * each committee member uses one of these two approaches to 'scoring' the workshop submissions | ||
+ | *# score each criteria, and total the scores | ||
+ | *## some criteria may be assigned a 'multiplier', if they should have more or less "weight" than the rest of the criteria | ||
+ | *## the range of scores used is 0 through 5: | ||
+ | *##* 0 = does not meet the criteria at all | ||
+ | *##* 1 = barely meets the criteria | ||
+ | *##* 3 = average | ||
+ | *##* 5 = meets the criteria exactly | ||
+ | *## the workshop submission is reviewed, and each criteria is assigned a score from 0 through 5 | ||
+ | *## if any multipliers are to be used, apply them to the scores | ||
+ | *## get the total score for the workshop submission | ||
+ | *## produce a 'ranked list' of the workshop submissions, based on their total scores | ||
+ | *## if there are any workshops that received a 0 on any of the criteria, note them for discussion, because they may not be a good fit for the conference | ||
+ | *# assign a single score | ||
+ | *## the range of scores 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 workshop submission is reviewed, and is assigned a score from 0 through 5 | ||
+ | *## produce a 'ranked list' of the workshop submissions, based on their scores | ||
+ | *## if there are any workshops that received a 0 score, note them for discussion, because they are not a good fit for the conference | ||
Line 58: | Line 86: | ||
− | == Half-Day workshops == | + | == first version of a possible method to review workshop submissions == |
+ | === Half-Day workshops === | ||
# based on the limiting factors, start with an assumption of 12 slots for half-day workshops | # based on the limiting factors, start with an assumption of 12 slots for half-day workshops | ||
# review the list of submissions for half-day workshops, and remove any that are not appropriate for the conference | # review the list of submissions for half-day workshops, and remove any that are not appropriate for the conference | ||
Line 76: | Line 105: | ||
## produce a 'ranked list' of the workshop submissions | ## produce a 'ranked list' of the workshop submissions | ||
## workshop committee reviews the 'ranked list', and may assign additional + or - 'committee points' to workshops | ## workshop committee reviews the 'ranked list', and may assign additional + or - 'committee points' to workshops | ||
− | + | === 90-minute workshops === | |
− | == 90-minute workshops == | ||
# based on the limiting factors, start with an assumption of 16 slots for 90-minute workshops | # based on the limiting factors, start with an assumption of 16 slots for 90-minute workshops | ||
# review the list of submissions for 90-minute workshops, and remove any that are not appropriate for the conference | # review the list of submissions for 90-minute workshops, and remove any that are not appropriate for the conference | ||
Line 96: | Line 124: | ||
## produce a 'ranked list' of the workshop submissions | ## produce a 'ranked list' of the workshop submissions | ||
## workshop committee reviews the 'ranked list', and may assign additional + or - 'committee points' to workshops | ## workshop committee reviews the 'ranked list', and may assign additional + or - 'committee points' to workshops | ||
− | + | === Final Steps === | |
− | == Final Steps == | ||
# 'flag' any workshops that appear on both the half-day and 90-minute 'ranked lists' | # 'flag' any workshops that appear on both the half-day and 90-minute 'ranked lists' | ||
# workshop committee provides the conference organizing committee with the 'ranked lists' | # workshop committee provides the conference organizing committee with the 'ranked lists' |
Revision as of 09:10, 12 March 2007
FOSS4G2007_Workshop_Submissions
- FOSS4G 2007 has a "workshops day" on Monday September 24th, that will have half-day (3 hour) workshops.
- FOSS4G 2007 will have 90-minute workshops that take place during the conference, September 25-27.
Suggested timetable for workshop submissions review process
A private mailing list ("the list") was setup March 7, 2007 for use by the workshop committee.
- March 7 to 11
- on the list, discussions about the review process
- all committee members review the documents and get familiar with the workshop submissions
- 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
Second version of a possible method to review workshop submissions
- workshop committee establishes a list of 'review criteria'
- the only criteria used when workshop committee members review workshop submissions are the 'review criteria'
- each committee member uses one of these two approaches to 'scoring' the workshop submissions
- score each criteria, and total the scores
- some criteria may be assigned a 'multiplier', if they should have more or less "weight" than the rest of the criteria
- the range of scores used is 0 through 5:
- 0 = does not meet the criteria at all
- 1 = barely meets the criteria
- 3 = average
- 5 = meets the criteria exactly
- the workshop submission is reviewed, and each criteria is assigned a score from 0 through 5
- if any multipliers are to be used, apply them to the scores
- get the total score for the workshop submission
- produce a 'ranked list' of the workshop submissions, based on their total scores
- if there are any workshops that received a 0 on any of the criteria, note them for discussion, because they may not be a good fit for the conference
- assign a single score
- the range of scores 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 workshop submission is reviewed, and is assigned a score from 0 through 5
- produce a 'ranked list' of the workshop submissions, based on their scores
- if there are any workshops that received a 0 score, note them for discussion, because they are not a good fit for the conference
- the range of scores used is 0 through 5:
- score each criteria, and total the scores
Factors that limit the number of Workshops
- technical limitations
- the entire Victoria Conference Center is booked for the conference
- on Monday, all rooms will be available for use for the half-day workshops
- Tuesday through Thursday 90-minute workshops will run concurrent with presentations
- for the 90-minute workshops, it would be preferred to have them run in rooms that remain setup throughout the conference
- the smallest room size is 24 feet by 15 feet, with a suggested maximum classroom seating size of 18
- some rooms can be used 'full size', or can be divided with a 'hard wall' to make two classrooms
- with all rooms used 'full size', there are 9 possible classrooms
- with all rooms used 'divided' there are 12 possible classrooms
- number of PCs
- the review and selection of the workshop submissions is being done before the number of available PCs is finalized
- seating two people per PC, with 10 PCs, means a minimum workshop size of 20 people, which can be accommodated in all rooms, with the possible exception of the two or three smallest rooms
- the entire Victoria Conference Center is booked for the conference
- number of workshop slots
- half-day workshops
- if we assume a minimum of 60 PCs, and 10 PCs per workshop, there can be 6 concurrent workshops
- morning + afternoon means a total of 12 workshops
- if more PCs are available, the size of workshops could be larger, and/or there could be more workshops
- 90-minute workshops
- if we assume a minimum of 60 PCs, and two people per PC, that allows for 120 people at a time in the 90-minute workshops
- the size of the rooms available to setup for the 90-minute workshops may limit the maximum capacity for 90-minute workshops
- the FOSS4G Program allows for 1-2 workshops to run concurrent with the presentations
- the number 90-minute workshops is limited by the number of slots available
- there are eight 90-minute time slots in the conference program
- assuming running two concurrent 90-minute workshops means a maximum of sixteen 90-minute workshops
- half-day workshops
first version of a possible method to review workshop submissions
Half-Day workshops
- based on the limiting factors, start with an assumption of 12 slots for half-day workshops
- review the list of submissions for half-day workshops, and remove any that are not appropriate for the conference
- if the number of submissions remaining is less than 12, panic!
- if the number of submissions is only slightly higher than 12, see if the limiting factors can be adjusted to accommodate all the submissions
- if the number of submissions is substantially higher than 12
- 'score' the workshop submissions
- assign each submission a starting 'score' of zero
- -3 for any submissions presented at FOSS4G 2006
- -2 for any submissions that were presented at FOSS4G conferences prior to 2006
- -1 if the workshop can be presented in a 90-minute format
- +1 if the workshop presenter is known for good presentations
- +1 if the workshop topic is expected to be of high interest
- +1 if the workshop topic is particularly relevant to conference themes
- +1 if the workshop topic is new/different/unique
- each workshop committee member must assign each submission either +1 or -1 'committee member points'
- produce a 'ranked list' of the workshop submissions
- workshop committee reviews the 'ranked list', and may assign additional + or - 'committee points' to workshops
- 'score' the workshop submissions
90-minute workshops
- based on the limiting factors, start with an assumption of 16 slots for 90-minute workshops
- review the list of submissions for 90-minute workshops, and remove any that are not appropriate for the conference
- add to the 90-minute list any half-day workshops that can be presented in a 90-minute format
- if the number of submissions remaining is less than 16, panic!
- if the number of submissions is only slightly higher than 16, see if the limiting factors can be adjusted to accommodate all the submissions
- if the number of submissions is substantially higher than 16
- 'score' the workshop submissions
- assign each submission a starting 'score' of zero
- -3 for any submissions presented at FOSS4G 2006
- -2 for any submissions that were presented at FOSS4G conferences prior to 2006
- -1 if the workshop can be presented in a half-day format
- +1 if the workshop presenter is known for good presentations
- +1 if the workshop topic is expected to be of high interest
- +1 if the workshop topic is particularly relevant to conference themes
- +1 if the workshop topic is new/different/unique
- each workshop committee member must assign each submission either +1 or -1 'committee member points'
- produce a 'ranked list' of the workshop submissions
- workshop committee reviews the 'ranked list', and may assign additional + or - 'committee points' to workshops
- 'score' the workshop submissions
Final Steps
- 'flag' any workshops that appear on both the half-day and 90-minute 'ranked lists'
- workshop committee provides the conference organizing committee with the 'ranked lists'