Showcase: Google Docs for Group Project Coordination, Redux

A year ago I reflected on how I used Google Docs to coordinate year-end group projects for my 10th grade World History students. They used a spreadsheet to keep track of their work and typed up their notes and created their presentation in Moodle. It was a substitution, or perhaps an augmentation, of what they would have been able to do without Google Docs (now Drive). This year I thought about how I could make the experience not just easier in terms of workflow, but also in terms of learning. I accomplished this by focusing on feedback and motivation.

20130609-185249.jpg
Better use of comments helped students get feedback and validation of their work.

Working from the premise that the quality of work improves when 1) students get prompt feedback and 2) feel they are creating something for an audience other than their peers, I changed the structure of project to incorporate additional components:

  • A research skills component that required students to evaluate the credibility of the sources in another group’s bibliography and share their feedback with that group (next time I’ll have the kids leave this feedback as comments within the bibliography rather than a separate document so that it’s immediately apparent)
  • More rigorous feedback on my part, using comments within Google Drive to give praise and constructive criticism promptly and regularly
  • Regular showcase demonstrations of exemplary work to the class as we passed each checkpoint, which I could do since each group kept their work in a folder that was shared with me.

These three components required students to create for a peer audience and also gave them numerous opportunities, along with concrete examples, of how they could improve their work. Kids also appreciated being showcased and it created a real sense of camaraderie. There’s something really cool about having an entire class applaud someone’s work.

I felt I got closer to a redefinition this time around – not because leaving feedback is novel, but because giving intra-class peer feedback between 20+ students at a time is impractical to the point of impossibility. It’s just another way that Google Docs helps streamline the process of learning: it helps you get away from getting kids to DO things and lets you focus on getting them to LEARN things.

Repurposing Old Hardware via Chrome OS (aka Chromium OS)

A recent post on Google+ asked:

Has Google ever thought of releasing the Chrome OS as a stand alone product for purchase? I know Google would like us to buy Chromebooks, but for many schools, we have to use existing hardware until it dies, and who knows if and or when we may get $$$ for new.

I would love to be able to convert my existing netbooks to Chromebooks, and then when they die, be able to show my board and principal a proof of concept for purchasing only Chromebooks in the future.

Here’s the answer:

  • Google has kind of released ChromeOS, as the Chromium OS. This is an open-source implementation of ChromeOS that includes core functionality but lacks a) drivers for most types of hardware, b) flash, c) pdf, and d) Google Talk. It’s hasn’t released it in a way you can install on your computer.
  • You can install Chromium OS on your computer via programs created by third-party (read: random, but talented) individuals. These are called “builds” and THE guys is hexxeh, who was at one point a 17-year-old UK programmer who just took it on as a hobby. He has taken the raw code (“source code”) of Chromium and turned it into a package you can install on some – but not all – computers.
  • If you get it installed, functionality may be missing for some components, or it may be reduced in future builds – Google tries to keep ChromeOS as streamlined as possible, which makes it fast but also makes it compatible with only a narrow range of hardware.

If you want to try it out, though, you do the following:

  1. Download a build of Chromium from http://chromeos.hexxeh.net/
  2. Follow the instructions for Win, Mac, or Linux from that page to get the build copied to a USB stick.
  3. Boot your laptop from the drive (F12 at startup – choose the USB stick)

At this point, your laptop will either load Chromium or not – if it doesn’t, you probably have hardware compatibility issues. For example, Chromium loads up just fine on my Toshiba, but the trackpad isn’t recognized, so I have to plug in a USB mouse.

If you’re able to log in, you’ll want to copy it to your hard drive so you don’t need to leave the USB stick plugged in all the time:

  1. Log in to the Chromebook with your Google Account.
  2. Ctrl – Alt- F2 to bring up a command line
  3. Log in with chronos / facepunch
  4. chrosh + enter brings you to the ChromeOS developer shell
  5. type “install” (this will format your hard drive)
  6. Reboot when the process is done and remove the USB stick.

That’s it. Once again, if these instructions don’t work, your hardware is probably incompatible. If you get this far, though, you probably want to add Flash, PDF, and mp3/mp4 support. There are sites out there that purport to get them working, but they don’t seem to work on all builds. This means that you’ll have to go without the ability to use sites like Prezi or WeVideo, read PDFs, and listen to music. Not terribly useful.

If you’re wanting to repurpose old hardware, then you should go with Xubuntu Linux for your OS and install Chrome as the default browser. It won’t have the streamlined (simple) interface and lightning performance of ChromeOS, but there will be much better hardware and software support.

References