1,885
edits
Changes
no edit summary
|-
|2||Jan 22||[[#Week 2 - Class I|Computer Architecture Overview - Binary representation, processor internals, instruction set architecture]]||[[#Week 2 - Class II|Compiled C Lab (Lab 2)]]<!-- Overview of Working with Code and Building Software - Toolchains, compiler stages, switches and flags, binary file contents (Lab 2)]] -->||[[#Week 2 Deliverables|Blog your conclusion to Labs 1 and 2.]]
|-
=== Week 1 - Class II ===
==== Course and Setup: Accounts, agreements, servers, and more ====
* [[SPO600 Communication Tools]]
* [[Winter 2018 SPO600 Participants]] page
* [[SPO600_Servers#Preparatory_Steps|Key generation]] for [[SSH]] to the [[SPO600 Servers]].
* Student Agreement
==== Discussion of how open source communities work ====
## Generate a [[SPO600_Servers#Preparatory_Steps|pair of keys]] for [[SSH]] and email the public key to your professor, so that he can set up your access to the [[SPO600_Servers class servers]].
## Sign and return the [[Open Source Professional Option Student Agreement]] (this will be done on paper in class).
# Optional (recommended): [[SPO600 Host Setup|Set up a personal Fedora system]].
# Optional: Purchase an AArch64 development board (such as a [http://96boards.org 96Boards] HiKey or Raspberry Pi 2/3).
* [[SPO600 Code Building Lab|Code Building Lab (Lab 2)]] as homework
* [[SPO600 Compiled C Lab|Compiled C Lab (Lab 2)]]
=== Week 2 Deliverables ===
* Blog about your selected function(s) and project plan
** Remember: You should be posting 1-2 times per week
#################################################################################
* Complete ALL your blogging for this course by Midnight on Thursday, April 21. Make sure that you have included all of the labs, your presentation, and your project work. Remember that there should be at least 1-2 posts per week. Your blogging from April 1-April 21 will be used for your April communication mark.
=== Tuesday (Sep 15) ===
