Winter 2012 SBR600 Participants

From CDOT Wiki
Revision as of 11:15, 2 February 2012 by Asalwi (talk | contribs)
Jump to: navigation, search

Participant and Project Table

Idea.png
Sortable Table
Click on the arrow icon in any column to sort by that column.
# Name IRC Nick (Learn ID) Role Project Alternate Projects Notes Regarding Project Project Approval SBR700/OSD700
0 Chris Tyler ctyler (chris.tyler) Professor Fedora ARM Secondary Architecture
1 Kavishankar Srivamathevan kavis (ksrivamathevan) CTY Student Package KidsRuby Create the raspi-logos and raspi-fedora-remix-release-notes packages, Package the Raspberry Pi firmware
2 Chris Choo cchoo2 (cchoo2) CTYC Student Package the Raspberry Pi firmware Create the raspi-logos and raspi-fedora-remix-release-notes packages
3 Eugene Torre n/a CTY Student
4 Jesse Fulton jfulton CTYC Student
5 Dong Sun dsun20 CTY Student
6 Gang Li bory CTY Student
7 Nam Nguyen nhnguyen CTY Student
8 Kun Liu kliu39 CTY Student Raspberry Pi firmware Scratch I have no solid background of testing or scripting.
9 Alan Lau alanlau CTY Student
10 Chi hsun Lai chlai2 CTYC Student Create a SD Card Installation Tool Create the raspi-logos and raspi-fedora-remix-release-notes packages
11 Aries Alwi asalwi CTYC Student Package the Raspberry Pi kernel Utility
12 Craig Cain ccain1 CTYC Student Package Scratch
13 Maria Bustos-Roman mbustosroman CTY Student
14 Daniel Segree dsegree CTY Student
15 Jayaditya Mulwani jmulwani CTY Student
16 Celeste Allahar challahar CTYC Student Firstboot Package KidsRuby or Modify Grubby to work with the Raspberry Pi Kernel
17 Andrew Greene agreene CTY Student
Important.png
Don't Break the Table
Use the preview capability to ensure that your wiki markup is correct before saving. If you break the table or page, please fix it!

Column definitions

  • Name - Your full name, linked to your wiki user profile page (please place contact information there).
  • IRC Nick(s) - Your nicks (nicknames) as used on IRC. Leave this blank if you're not using IRC yet.
  • Role - Professor, CTY Student, CTYC Student, CDOT Researcher.
  • Project - Link to your main SBR600 project wiki page. Leave blank if you have not selected an SBR600 project yet.
  • Alternate Projects - Projects you are interested in doing if your selected project is not approved.
  • Notes Regarding Project - Any comments you have about your project selection.
  • Project Approval - Initialed by your professor when your project selection is approved; may also contain a note about comments on the Talk page.
  • SBR700/OSD700 - Place a Y here if you're interested in taking the SBR700/OSD700 continuation course. This will be a course offered in a subsequent semester where you can continue work on the project you started in SBR600 (or another project, if your SBR600 project is concluded). Place an N here if you are not interested in taking SBR700/OSD700. Leave this blank if you're unsure.

Instructions - Participant Information

Please add your name, IRC nick, and Learn ID as soon as possible. Link your name to your Wiki user page.

Instructions - Project Selection

Select one of the SBR600 Potential Projects and add an entry to this table. Project assignment is not final until approved by your professor but is generally assigned on a first-come, first-served basis.

Edit your row on this page:

  • In the Project column, please place a project title exactly as written on the potential projects page.
  • In the Alternate Projects column, please name one or two other projects that you are also interested in, if your first choice is oversubscribed or not available.
  • In the Notes Regarding Project column, comment on why you chose the project you did.
  • Add a link from the project name in the Project column to your Project page. For the Project page, use the Sample Project as a template.
  • Fill in the Project page with your initial project plans. See the comments in each section of that page for instructions.
    • Research the scope of your project
    • Identify some initial resources (people, information) and links.
    • Decide on your goals for your 0.1 release (proof of concept), 0.2 release (initial implementation), and 0.3 release (good implementation). Note that some projects have a much bigger scope than others, and some will be largely completed by the first release date (in which case you may want to take on a second small project for the later release dates).