swcarpentry / deprecated-website Goto Github PK

In conjunction with Mike Mineter who attended the PRACE Edinburgh boot camp in December 2012. Mike said he'd be in touch with mikej888 in due course.

• @synesthesiam and Jeff Shelton to lead (?)

The FAQ needs to be updated and enlarged. Should answer questions from:

• workshop attendees
• workshop instructors/hosts
• potential funders
• other scientists

Remix material that people have already created to produce a 90-minute introduction to Git and GitHub. Length and depth should be similar to existing Subversion material.

Right now, we are using:

• '[email protected]' and '[email protected]' on Google itself
• '[email protected]' on EventBrite
• '[email protected]' on YouTube
• '[email protected]' for the CafePress store, Doodle, and SurveyMonkey
• 'softwarecarpentry' at Disqus

There should be a single '[email protected]' account that owns/runs everything.

Should work on tablets as well as full-screen devices (and the blog should look good on cellphones, at least).

• R rather than Python
• Friday and Saturday in February or March 2013, excluding the first Friday of each month

Organize a second boot camp for the University of Washington using local talent to teach.

Use Popcorn.js and some kind of text-record-and-playback tool to create a replay-in-the-browser plugin for the IPython Notebook.

Create material for a half-day or full-day introduction to programming using R to parallel existing material using Python.

http://www.evolutionmeeting.org/

Borrow from the PyCon Code of Conduct to create one for Software Carpentry workshops.

• Is this opt-in or mandatory?

Create instruments for determining how well workshops went. This should include:

• learner enjoyment/satisfiaction
• actual learner achievement
• ideas for improving setup/execution next time

• May 30-31, 2013
• @gvwilson is lead instructor

Try running online office hours (open-ended help sessions) for learners after workshops.

• Where: Manchester
• Host: Michel Drescher
• Audience: EGI Forum attendees
• Instructors: Mike
• Helpers: Björn Hagemeier and SSI folks.
• Web site: http://software-carpentry.org/bootcamps/2013-04-egi-forum.html
• Registration: http://cf2013.egi.eu/registration/. Can check a forum registration box to express interest or drop-in on the day.
• Mailing list: N/A
• Repository: https://github.com/swcarpentry/boot-camps/tree/2013-04-egi-forum
• Syllabus: see repository README.md.

Early publicity:

http://www.egi.eu/news-and-media/newsfeed/news_0178_software_carpentry_workshop.html
http://www.egi.eu/blog/2012/11/08/software_carpentry_or_the_art_of_software_artisanship.html

Notes: Will set up VM at EPCC with temporary accounts so attendees can drop in if desired.

index.html has "./blog/" as a link, but that 404's on http://dev.software-carpentry.org --- rewrite issue?

Write an alternative introduction to programming in Python that uses image manipulation for examples.

• Build on top of Michael Hansen's simple media library

1. Build a command-line script for issuing open badges using 5.0/bin/*.py as a starting point.
2. Use this to issue badges to instructors, creators, and organizers. (We won't issue to learners until we figure out what that means.)

• Where: Beacons Satellite Symposium, Bath
• Host: Alex Chartier
• Audience: attendees at the above
• Instructors: Mike Jackson, Chris Woods (@chryswoods)
• Helpers: Eliot Marsden, Fergus Cullen, Jeremy Metz, David Martin?,
• Web site: http://software-carpentry.org/bootcamps/2013-07-bath.html
• Registration: Restricted
• Mailing list: http://lists.software-carpentry.org/listinfo.cgi/bath-software-carpentry.org
• Repository: https://github.com/swcarpentry/boot-camps/tree/2013-07-bath

• @arokem, @BernhardKonrad and @ivanov will instruct.

Create and field-test a short questionnaire that will help potential workshop attendees figure out if the workshop is right for them (and tell instructors something about who they're going to be teaching). Some requirements:

1. Must take 10 minutes or less to complete.
2. Must not frighten away the people we're trying most to help (but it's OK if the conclusion is "You're not ready for this").
3. Must be useful as a baseline for the post-assessment questionnaire.

• Where: TODO
• Host: Norman Gray
• Audience: SUPA Scottish Physics Consortium
• Instructors: TODO
• Helpers: TODO
• Web site: TODO
• Registration: TODO
• Mailing list: TODO
• Repository: TODO
• Syllabus: TODO

Notes: Norman attended the PRACE Edinburgh boot camp in December 2012.

Write a small script that people can download from our web site and run on their machine that will tell them if everything they need for a boot camp has been installed correctly --- see swcarpentry/website#38 for starting points.

Create material to fill a half day or a full day to cover:

• basic HTML authoring
• parsing and creating HTML programmatically
• reading and writing web data
• how to think like the web
• security issues

Existing material is in book/web.html.

The current Subversion repository tracks PDF and PNG versions of some ODP slides. Rather than bloat the repository with a bunch of binary blobs, we should automatically generate them using LibreOffice and Imagemagick.

Potential issues with autogeneration:

1. The SWC server doesn't have the new build tools installed. Fix: build a tarball locally, push the tarball to the server, and unpack there:

   $ make swc-website.tar.gz
   $ scp swc-website.tar.gz server:/downloads/dir/
   $ ssh server tar -xzf /downloads/dir/swc-website.tar.gz -C /target/dir

2. Contributing devs may not have the new build tools installed. Fix: have them grab the tarball from the SWC server and use it to seed their local build.

   $ wget http://server/downloads/swc-website.tar.gz
   $ tar -xzf swc-website.tar.gz -C /tmp/swc/
   $ git clone git://github.com/swcarpentry/website.git
   $ cd website
   $ make PDF_DST= PNG_DST= site

We have a lot of requests from biologists, geographers, and others for an entry-level version of this course.

Write a small script that people can download from our web site and run on their machine that will tell them if everything they need for a boot camp has been installed correctly --- see swcarpentry/website#38 for starting points.

• @adina is interested in teaching.
• See also #366.

• Where: Manchester
• Host: Casey Bergman (local organiser) and Carole Goble
• Audience: Internal
• Instructors: Mike Jackson (@mikej888), Aleksandra Pawlik (@apawlik), David Jones (@drj11)
• Helpers: Shoaib Sufi (@shoaibsufi), Michael Croucher
• Web site: http://software-carpentry.org/bootcamps/2013-04-manchester.html
• Registration: http://www.eventbrite.com/event/5397207192
• Mailing list: http://lists.software-carpentry.org/listinfo.cgi/manchester-software-carpentry.org
• Repository: https://github.com/swcarpentry/boot-camps/tree/2013-04-manchester
• Syllabus: See https://github.com/swcarpentry/boot-camps/blob/2013-04-manchester/README.md

We're currently using Mozilla's Etherpad installation; we should set one up on software-carpentry.org so that we can easily create one 'pad per workshop.

Reorganize and reformat setup & installation instructions for workshop participants. These should be organized as a grid (platform vs. tool), but also include a path (step 1, step 2, ...) for each platform. They should not assume more information about things like environment variables than our participants have before taking our workshops.

• @gvwilson + 1 other to teach March 4-5, 2013
• to be followed by #247

Get rid of WordPress and start using the compiled web site.

Create a 60-second video explaining why someone would want to organize or deliver a Software Carpentry workshop.

Create some sort of sign-off for content contributors so that it's clear we have the right to use stuff.

@gvwilson currently stores information on past workshops (e.g., participants names and email addresses, instructors t-shirt sizes, etc.) in an SQLite database stored in a private Subversion repository. We need something better that:

• supports versioned sharing
• is secure
• doesn't violate any privacy protection laws

There is no clear way on the web site right now for people to contact us to request a boot camp. This could be as simple as a mailto:, or a real web form.

While every case will be a little different, it would be useful to develop/share best practices for planning a workshop. In particular, what is a the recommended/preferred number of days/weeks/months prior to the event to have finalized detail x/y/z....

Write an instructors' guide for workshops. Existing material is in book/teach.html, and scattered through book/*.html in 'keypoints' and 'understand' sections.

Move everything from http://svn.software-carpentry.org/swc/5.0/website into GitHub.

• @jkitzes will co-teach.

• April 29-30, 2013
• @stephenmcgough will instruct

Write, record, and post a 60-second video explaining what we do and why potential learners should come to one of our workshops. This can use the existing 90-second pitch as a starting point.