Re: [eclipsecon-na-program-committee] raising the bar etc. for tutorial

[Anne Jacko <anne.jacko@xxxxxxxxxxx>]

We've talked about requiring tutorial presenters to submit their outlines by a certain date. We could also require that their outlines include certain info. We'd have to allow for some time for a mentor or PC member to review the submitted outline and the presenter to make any requested changes. But I like this idea, so I'll come up with a timeline to see if we can make this work.

Anne Jacko

Eclipse Foundation

503-784-3788 (cell)

On Jan 25, 2012, at 8:29 AM, Doug Schaefer wrote:

Do we want to set up deadlines/checkpoints so we can make sure these
requirements are in the presenter's minds? That way we could get an
early indication of tutorials that are in trouble.

:D

On Wed, Jan 25, 2012 at 3:11 AM, Gunnar Wagenknecht
<gunnar@xxxxxxxxxxxxxxx> wrote:

Am 24.01.2012 21:27, schrieb John Arthorne:

- Having a way for people to skip steps, or "catch up" if they missed a

step is critical. Otherwise if someone gets behind near the beginning

they may waste the next three hours because they can't catch up.  Gunnar

had an excellent plugin for managing this that he used in his server

side tutorial. Maybe he can share a link to that code or put the plugin

up somewhere that all presenters can find it.

Kudos go to the RCP book authors because they initially created it.

http://sourceforge.net/projects/samplings/

- Don't assume wireless will work quickly or reliably - have a

contingency plan for when wireless fails or is too slow to download

builds, etc.

Yeah, that's always a surprise. Especially when your setup plan includes

installing things into Eclipse. I highly recommend preparing packages

for Linux+Mac+Windows for 64bit +32bit in advance. However, that's quite

an effort.

Also, there are some other gotchas we run into over the years:

- We prepared our tutorials on Windows. Ports <1024 typically don't work

on Linux+Mac because the users don't work as root. Thus, make sure to

make a dry run on other platforms as well.

- Some guy actually complained about my OS/Desktop using a non-English

setup. You should likely create a second user/profile just for

demos/tutorials that has a default setup with no distraction (no

background image, etc.).

- As a presenter, I'm too fast when doing the exercises. For example,

quite a lot people don't know shortcuts. Thus, whenever you type and use

a shortcut, explain the shortcut. Don't expect attendees to know every

available quick fix and shortcut of the Eclipse Java editor.

-Gunnar

_______________________________________________

eclipsecon-na-program-committee mailing list

eclipsecon-na-program-committee@xxxxxxxxxxx

http://dev.eclipse.org/mailman/listinfo/eclipsecon-na-program-committee

_______________________________________________
eclipsecon-na-program-committee mailing list
eclipsecon-na-program-committee@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipsecon-na-program-committee