Fall 2011 SBR600 Participants

Participant and Project Table

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	Applied for FUDCon Blacksburg	Attending FUDCon Blacksburg 2012
0	Chris Tyler	ctyler (chris.tyler)	Professor	Fedora ARM Secondary Architecture				Y	Y
1	David Liscio	dliscio (dliscio)	CTY Student	iSCSI-AoE Support	Test Thumb2 with ARMv7hl			N	Y
2	Jason Marciniak	jmmarciniak (jmmarciniak)	CTY Student	Test Thumb2 with ARMv7h1	YUM Documentation			N	N
3	Sangjin (Eric) Lee	simson703 (slee142)	CTY Student	Compare armv5tel and armv7h1 Performance	Test Thumb2 with ARMv7h1			N	N
4	Elon Li	heavymetal (efli1)	CTY Student	Test Thumb2 with ARMv7hl	Compare armv5tel and armv7hl Performance			N	N
5	Nicholas Lambert	nlambert (nlambert)	CTY Student	Tuning the Kernel(GPIO Pins)	Test Thumb2 with ARMv7h1			N	N	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. Applied for FUDCon Blacksburg - Place a Y here if you're interested in attending FUDCon Blacksburg 2012; place an N here if you do not want to attend. Note: The final decision on who will be invited to attend is at the professor's discretion based on available funding, and project and course work. Attending FUDCon Blacksburg - Filled in by Chris Tyler - Y here indicates students attending FUDCon Blacksburg; N here indicates that registration forms were not received by 2011-01-11; Waitlist indicates students who will be eligible to substitute for any students who cancel. Students were selected based on the order in which students replied to the request for passport names and birthdate information. 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). 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!