- Should @dolan-peter use Github classroom instead of the UMN Github? What does @kklamberty think?
- Answer seems to be that Github classroom was easier to work with and did a better job of separating groups, so Peter's going to go with that.
- Do we want to at least start replacing the semi-deprecated use of backticks in shell scripts with the
$(…)syntax? Eventually yes, but it doesn't need to start happening now. - The "course resources" page is currently in the UMN Github, which isn't a good place for it and it should probably move to Github.com. Where, though? Should it be a page in a repo? A gist? A page or pages in a wiki somehwere?
I need to make sure that each repo has whatever changes were made last fall merged into the "master" repos. @dolan-peter – if I've checked one, then it should be good to go and you can set it up in Github classroom.
In general the pre-labs were individual exercises and the labs proper were done in pairs. Looking at the relevant assignments on the S17 Canvas web site will make it clear what was what, though. Canvas will also indicate start and due dates; most labs were one week, but some were longer and some had odd timelines because of things like Fall Break and Thanksgiving.
- https://github.com/UMM-CSci-Systems/Command-line-introduction-pre-lab
- https://github.com/UMM-CSci-Systems/Command-line-introduction
- I addressed the two outstanding issues on this project; hopefully that will help.
- Pre-lab 1
- This issue might want to be looked at/discussed since it could significantly affect (in a good way) the grading time for this pre-lab.
- Lab 1 (log processing)
- This was split across two weeks with two distinct assignments in Canvas to indicate how far people should be at the end of the first week.
- There are two issues on the repo that probably deserve at least a little thought. One suggests that they should probably create releases (or at least tags) in their Github repos at the end of the first part; without that it can be quite difficult to know where the first half "ends" and the second "begins", which complicates grading. The other suggests breaking the write-up into two parts so it doesn't look so intimidating.
- There's a (private) reference solution
- Pre-lab 2 (C and memory management)
- There are three issues on this repo that we might want to talk about. One suggests adding some tests to the pre-lab; I don't think that should be too hard? A second suggests that a link in the write-up has quasi-rotted and we should chase that and think about where we want to go with that. The third is a larger issue of where the course resources page should go; it's currently on UMN's Github, but I think we want it here on Github.com. Not sure if it should just be a MD page in a repo, or a gist, or part of a wiki.
- Lab 2 (Memory management and C strings)
- Lab 3 (Memory management and multi-domensional arrays in C)
- Pre-lab 4
- Lab 4 (C system calls)
- Lab 5 (circuits)
- Lab 6 (Echo client-server)
- Lab 6 (RPC web service)
- There probably should be a pre-lab for the socket/thread stuff, but no one's written one yet.
- This lab has two distinct, but related activities. I've chosen to keep them in separate repos to make it easier to move, change, replace, etc., components.
- Lab 7 (Threaded echo client-servers)
- Pre-lab 8 (threading for parallelism)
- Lab 8 (Minimum pairwise distance)
- Lab 9 (Segmented file server)
- Lab 10 (Java profiling)
- Lab 11 (Mapping the Internet)