Adding hands-on

[ChristinaLK]

Here's a first draft of the hands-on section of the proposal. Questions for everyone:

• Do we need more example exercises? Or more specifics about the exercises?
• What do people think of the two examples I wrote up? If you have alternatives/suggestions, please share!
• @dbrunson, is the information I included about OK State + XSEDE resources accurate?
• Anything else missing?

[dbrunson]

Looks great! You could put "education allocation" to be more specific, but I doubt that level of detail is terribly important.

[shwina]

There is room for "visuals" of demos, that we can provide as an attachment, or as a link to a web page, etc. Do we want to add visuals of what the code boxes ("input", "output" and "error") look like in our lesson material? Or do you think this is too fine a detail?

[ChristinaLK]

The most appropriate "visual" to include would be a link to the actual lesson material, which hasn't been developed yet and/or some diagrams of topics we'll be teaching on (which also don't exist :P).

If appropriate, we could link to another Software Carpentry lesson page and say that "the lesson will look like this" (with exercises, and so on).

[shwina]

I think it's appropriate to do that, just so reviewers have some idea about what exactly the "lesson material" refers to.

[shwina]

Fantastic! Thanks @ChristinaLK