Miniconf Wrangler initial #2
Conversation
There was a problem hiding this comment.
Generally this looks pretty good. I've added a whole bunch of small suggestions (and pointed out a few typos), but they're all localised changes.
I think the only overall thing I'd suggest doing is adding some sub-headings with the dates in them, eg
September
October/November
December
January
and the like.
Ewen
|
|
||
| * Miniconf organisers (and co-organisers) should be added mailings lists. There should be 2 mailing lists: an "announce" list to send things to all miniconfs, probably called "miniconf-announce" and moderated, and a "discussion amongst Miniconf organisers" one, perhaps called "miniconf-discuss" | ||
| * Access the registration system should be setup to allow Miniconfs to run their own CFPs | ||
| * This process should be well documented and checklists in place for setting people up |
There was a problem hiding this comment.
Suggestion: "... and have checklists in place for the steps required to enable a Miniconf CFP"
| * Miniconf organisers (and co-organisers) should be added mailings lists. There should be 2 mailing lists: an "announce" list to send things to all miniconfs, probably called "miniconf-announce" and moderated, and a "discussion amongst Miniconf organisers" one, perhaps called "miniconf-discuss" | ||
| * Access the registration system should be setup to allow Miniconfs to run their own CFPs | ||
| * This process should be well documented and checklists in place for setting people up | ||
| * Some Miniconfs have multiple organisers than need to be setup |
There was a problem hiding this comment.
Typos: "... organisers that need to be set up"
| * Access the registration system should be setup to allow Miniconfs to run their own CFPs | ||
| * This process should be well documented and checklists in place for setting people up | ||
| * Some Miniconfs have multiple organisers than need to be setup | ||
| * Which Miniconfs are on which should be confirmed with the Organisers (to head off potential clashes) |
There was a problem hiding this comment.
Missing word: ".... are on which days should be confirmed..."
| * This process should be well documented and checklists in place for setting people up | ||
| * Some Miniconfs have multiple organisers than need to be setup | ||
| * Which Miniconfs are on which should be confirmed with the Organisers (to head off potential clashes) | ||
| * The schedule of each Miniconf day should be finalised. |
There was a problem hiding this comment.
Suggestion: "The schedule of each day that has Miniconfs should be finalised."
Reasoning: It makes it clearer this is the overall conference schedule that needs finalising, not the Miniconf schedule internally.
| * Which Miniconfs are on which should be confirmed with the Organisers (to head off potential clashes) | ||
| * The schedule of each Miniconf day should be finalised. | ||
| * Times of each sessions, including required finish time | ||
| * Time of 5 minute break mini-session to allow switches between Miniconfs |
There was a problem hiding this comment.
Suggestion: 'Time of common 10 minute "room change" breaks to allow....'
Rationale: 5 minutes is pretty tight at most venues. 10 minutes works well both on the main conference days and also at other conferences run by LA, like PyconAU.
(If not adopting this suggestion I think "mini-session" is probably meant to be "mid-session".)
| * Schedules for all Miniconfs should be up on the website | ||
| * All Miniconf organisers should be registered | ||
| * If possible check if Miniconf speakers are also registered | ||
| * Hardware-based Miniconfs should have have everything shipped and in place. |
There was a problem hiding this comment.
FWIW, hardware based Miniconfs will never have shipped everything in December. It's never happened, as project dev is always ongoing until at least a month out. Maybe change that to "... should have everything ordered ..."?
| * All Miniconf organisers should be registered | ||
| * If possible check if Miniconf speakers are also registered | ||
| * Hardware-based Miniconfs should have have everything shipped and in place. | ||
| * If possible Miniconfs should have contingencies in case of speaker cancellations. |
There was a problem hiding this comment.
Suggestion: "Encourage Miniconf organisers to have contingencies ..."?
| * If possible Miniconfs should have contingencies in case of speaker cancellations. | ||
|
|
||
| In the Week beforehand | ||
| * Some Miniconf organisers may be interested in a tour of the rooms on the Sunday before LCA |
There was a problem hiding this comment.
Suggestion: change "may" to "will".
And maybe the Miniconf Wrangler should encourage that? Perhaps as part of the Speakers orientation tour?
|
|
||
| In the Week beforehand | ||
| * Some Miniconf organisers may be interested in a tour of the rooms on the Sunday before LCA | ||
| * If a Main-conference speaker cancels or is delayed then they will sometimes forget to also tell any Miniconfs they are speaking at. Relay this in case. |
There was a problem hiding this comment.
Suggestion: "Relay this on if you aware of any such issues".
| * Let the organisers know about the room arrangements above. | ||
|
|
||
| During the Conference | ||
| * Be available |
There was a problem hiding this comment.
Suggestion: "Be available to assist with issues as they come up".
Possibly it's worth suggesting they notify Miniconf Organisers of the best form of real time contact?
Added duties of the Miniconf Wrangler