CS 4970: daily-announcements slide set

Felsius

xkcd # 1923

## Monday, December 4th
- Office hours are in the [syllabus](syllabus.html); they end as of tomorrow
- STS prospectus
  - Please upload a PDF version of it to the course management system
  - We can sign your cover pages today (and throughout this week)
- We are in the middle of iteration 6
  - Leads: your weekly TPS are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- With the end of iteration 6 (next week), there will be another phase change survey
  - It will be made available tomorrow, and is strictly due by the end of iteration 6 (midnight on Monday, December 11th)
  - URL for your survey will be in the PostEm tab
- Mid-semester individual evaluation regrades will be done soon
  - Note that we aren't updating the PostEm entry, but will update our individual spread sheets
- Iteration 4 and 5 evals are out: you have until Monday, Dec 11 to request a re-eval
- Grading: all homework regrades have been handled
  - You can see the updated result in the course management system
  - Still have concners?  Come speak to us in person right away
- Your journaling entry for iteration 6 is due tomorrow by noon
- Remember you have to report hours at least once each iteration
- Today is a group work day, and our final day this semester

## Goals for Iteration 6
- Complete 4 story points worth of work per group member
- Submit an 'other' report that contains credentials to log in (possibly multiple credentials for various user levels)
- Get customer feedback on the preliminary system (from the last iteration), and iterate on that design
- Complete the final system that implements the minimum requirements, and have it working on the course server
- Ensure that your requirements document is fully updated!
- Have the customer start using and testing the system via an email, CC'ed to us, that requests that they start testing the sytsem over break
  - Also mention that you'll likely be out of contact until mid-January
- Complete a preliminary *deployment plan*: a Markdown document in your repo as docs/deployment-plan.md that has all the known deployment info
- Complete 5 more unit tests per person (total now is 15+ per person)
- Meet with the grad TA and demo your final system
  - If the meeting time is doing to cause scheduling issues (during a final, after you've left grounds, etc.), you can request a different time to meet
  - If you meeting is early in the iteration, it's fine if some functionality is not yet finished; we can check that when it's all done
- Three individual tasks: complete the individual project, upload your STS prospectus, and (at the end) phase-change survey

## Final project notes
- We have a (small) individual project in lieu of a final exam
- Full project details [here](../docs/project-nonprofit-data-collection.html), although those details will be updated later today
- You will be assigned 10 (or so) nonprofits to find the information about
  - Those nonprofits will be in a PostEm posting in the course management system
  - That will also appear later today
- You may find it hard to get information on some nonprofits
  - If so, then fill out the form as best you can with whatever information you do have
  - If information is not available, fill out "none" in that field, and explain in detail in the Notes field at the bottom
  - This includes nonprofits that do not seem to exist, as well as nonprofits without an email address (only phone contact info)
- This is due by the end of the iteration (noon on Tuesday, December 12th)

## Sample Grading Metric
- This is a reminder from the [course introduction slide set](course-introduction-fall.html#/grades)
- Base metric
  - 50%: iteration evaluations
  - 30%: final project evaluation
  - 10%: homeworks
  - 10%: project in lieu of the final exam
- Modifications
  - Group work is multiplied by a *factor*, which is an estimate of how much work you did for the group
  - You saw a preliminary estimate of the factor in the individual mid-semester evaluations
  - Penalties for missing class or not completing your reported times
  - Massive penalties for not completing the surveys
- As promised, you will get an A in the course if ALL of the following are true:
  - All 'good' group evaluations (or evals that average to 'good')
  - Doing an 'average' amount of work
  - Getting 93% in the homeworks and the final project
  - No penalties for missed attendance, missed reported hours, or missed surveys

## Remaining schedule
- Monday, 12/4: group meeting in lecture (today)
  - Make sure the lead submits the weekly report
  - Tonight: the final project details released
- Tuesday, 12/5: phase-change survey released
- Monday, 12/11: iteration 6 ends:
  - Make sure the lead submits the TPS report
  - Make sure you complete the [iteration 6 goals](iteration-goals.html#/it6goals)
  - Phase change survey due by midnight
- Tuesday, 12/12
  - [Final project](../docs/project-nonprofit-data-collection.html) due by noon
- Wednesday, 12/13: grading metrics released
  - This may be delayed if it ends up taking us more time...
  - Once released, you will receive an email, and you will have only 24 hours to submit a regrade
- Thrusday, 12/14: final grades released

## Holiday Break
- We will do our best not to bother you until we return. But...
- If something goes wrong with the system, or the customer can't use it, then we'll start sending emails
- The customer may (or may not) email you
- Our hope is that we don't have to contact anybody (we want a break from course work too...)

## Instructor change
- For the spring 2018 semester...
  - Professor Bloomfield will be on sabbatical, and will not be teaching any classes in the spring
  - Professor Ibrahim will be solo teaching all of CS 4971, and will see the projects to completion

## Preview of next semester
- This isn't really the end; we are only half-way through our capstone
- Next semester we will pick up right where we left off ...
  - ... with a group meeting on Wed, Jan 17th
  - Class meets on M/W from 10:00-10:50; group meetings on Mondays, lectures on Wednesdays
  - We generally won't have lectures on Fridays (but we will at the very end of the semester)
- Grades for both semesters will be completely independent
- There will be 8 iterations instead of 6
  - The first 5 will be development; the last 3 deployment
  - Different group sizes will have a different phase schedule as a result
  - Desired requirements will need to be completed by late March -- specifically, at the end of iteration 11
- Iterations will have specific deliverables
  - Deployment plan, test plan, transition plan, etc.
- Some documentation during the last 3 iterations
  - Technical report, user manual, installation instructions, programming reference
  - We will guide you through all of these
- Professor Ibrahim will give you more details when the Spring semester starts
- And, of course, lots of progress on your projects!

## Checklist to get outta here
- As a group:
  - Ensure that your build is working
  - Complete all the [goals for iteration 6](iteration-goals.html#/it6goals); including:
    - Do a mini "hand-off" to the customer, and CC us; details in the iteration 6 goals
    - Ensure that your requirements document is updated
    - Have the final group meeting with the grad TA, where you will demo your system
	- Ensure you have your deployment plan document
	- Submit an 'other' report for iteration 6 with the credentials for the system
  - Leads: submit the weekly and TPS reports at the appropriate time
    - We won't be able to remind you, since there won't be classes then!
    - And the rest of the group should check to make sure they are submitted
- Individually:
  - Complete your [final project](../docs/project-nonprofit-data-collection.html) by noon on Tuesday, December 12th
  - Complete the end-of-phase survey (released tomorrow, Tuesday, December 5th) (part of the iteration 6 goals)
  - Make sure you have registered for CS 4971 for the spring
  - Once the grading metrics are released (likely Wednesday, Dec 13), review them and respond, if necessary, within 24 hours
  - Continue to report your hours

<h2>The Moon and the Great Wall</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/the_moon_and_the_great_wall.png" title="And arguably sunspots, on rare occasions. But even if they count, it takes ideal conditions and you might hurt your eyes." alt="The Moon and the Great Wall" srcset="http://imgs.xkcd.com/comics/the_moon_and_the_great_wall_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1921/">xkcd # 1921</a></p>
</section>

## Wednesday, November 29th
- Office hours are in the [syllabus](syllabus.html)
  - They end as of next Tuesday
- STS prospectus
  - Please upload a PDF version of it to the course management system
  - We can sign your cover pages today (and next Monday)
- We are at the start of iteration 6
  - Leads: your weekly TPS were due yesterday by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- Mid-semester individual evaluation regrades: we'll be getting to them soon
  - Note that we aren't updating the PostEm entry, but will update our individual spread sheets (and the data elsewhere in the system)
- Iteration 4 evaluations are out
  - You have 2 weeks from their release (until Dec 11) to request a re-eval
- We hope to have iteration 5 evals out later this week
- Grading: all homework regrades have been handled
  - You can see the updated result in the course management system
  - Still have concners?  Come speak to us in person right away
- Details about the final "project" in lieu of a final will be ready next Monday
- Remember you have to report hours at least once each iteration
- Today is a group work day

<h2>Emoji Sports</h2>
<img class="stretch" src="http://xkcd.com/imgs.xkcd.com/comics/emoji_sports.png" title="No horse has yet managed the elusive Quadruple Crown—winning the Kentucky Derby, the Preakness, the Belmont Stakes, and the Missouri Horse Hole." alt="Emoji Sports" srcset="http://xkcd.com/imgs.xkcd.com/comics/emoji_sports_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1920/">xkcd # 1920</a></p>
</section>

## Monday, November 27th
- Office hours are in the [syllabus](syllabus.html)
- We are at the end of iteration 5
  - Leads: your weekly TPS are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- Mid-semester individual evaluation regrades: we'll be getting to them soon
  - Note that we aren't updating the PostEm entry, but will update our individual spread sheets (and the data elsewhere in the system)
- Iteration 4 evaluations are out
  - You have 2 weeks from their release (until Dec 11) to request a re-eval
- We hope to have iteration 5 evals out later this week
- Grading: all homework regrades have been handled
  - You can see the updated result in the course management system
  - Still have concners?  Come speak to us in person right away
- Remember you have to report hours at least once each iteration
- Today is a group work day

## Goals for Iteration 5
- Complete 4 story points worth of work per group member
- In the first week, complete the end-of-phase survey
- Have a preliminary system that implements the minimum requirements working on the course server
  - Recall that the final system to implement the minimum requirements is due by the end of iteration 6
- Ask the customer about where the system will be deployed
  - When you get a response (even if that response is "I don't know yet"), please fill out an 'other' report
  - The intent here is to get the customer to start thinking about it; you don't need them to have any or all of the details at this point
- No more unit tests this iteration (but there will be more required next iteration)

<h2>How To Make Friends</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/how_to_make_friends.png" title="No, wait, come back! I want to be friends at you!" alt="How to Make Friends" srcset="http://imgs.xkcd.com/comics/how_to_make_friends_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1917/">xkcd # 1917</a></p>

## Monday, November 20th
- Office hours are in the [syllabus](syllabus.html)
- We are in the middle of iteration 5
  - Leads: your weekly reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
  - And the *phase change survey*, which you can access now (URL is in PostEm)
  - This is due today!  Why don't you do it now?
- Mid-semester individual evaluations are out
  - See the daily announcments from November 13th for details
  - If you disagree with anything, fill out a regrade for the "Fall 2017 mid-semester individual evaluations" assignment by ***TODAY***
- Iteration 3 evaluations are out -- you have 2 weeks from their release (until today, Nov 20) to request a re-eval
- We hope to have iteration 4 evaluations out tonight
  - You will have "two weeks" (modified a bit by Thanksgiving) to request a re-eval
- Grading: all homework regrades have been handled
  - You can see the updated result in the course management system
  - Still have concners?  Come speak to us in person
- Remember you have to report hours at least once each iteration
- Today is a group work day

## Github and commits
- From your repo's main page, click on 'contributions'
  - For each user, it states how many commits s/he made (it does not count merge commits); click on the "x commits" link ti see them
- For many of you, it is not properly counting your commits because your email address is not set right
  - The reason: github authenticates via github username and password, but git only stores the email
- The following command:
```
git config user.email
```
	- should print out the same email that github knows you as (or a github alternate email)
	- If it's set to something else, then it needs to be fixed
- To set it, run:
```
git config --global user.email "mst3k@virginia.edu"
```
	- This needs to be done on *each* computer you commit from
	- if you don't change the userid from `mst3k`, we won't consdier those commits...
- This may be, for some of you, why we didn't see the work that you did
  - We have a different system that we'll use moving forward
  - But this may necessitate a regrade for those of you

<h2>Temperature Preferences</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/temperature_preferences.png" title="There's a supposed Mark Twain quote, "The coldest winter I ever spent was a summer in San Francisco." It isn't really by Mark Twain, but I don't know who said it—I just know they've never been to McMurdo Station." alt="Temperature Preferences" srcset="http://imgs.xkcd.com/comics/temperature_preferences_2x.png 2x"/>
<p class="center"><a href="http://xkcd.com/1915/">xkcd # 1915</a></p>

## Wednesday, November 15th
- Office hours are in the [syllabus](syllabus.html)
- We are at the start of iteration 5
  - Leads: your TPS reports were due yesterday by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
  - With the end of iteration 4, we will have another *phase change*: new leads and new secretaries
  - And the *phase change survey*, which you can access now (URL is in PostEm)
    - That's due by the end of next Monday
- Mid-semester individual evaluations are out
  - See the daily announcments from November 13th for details
  - If you disagree with anything, fill out a regrade for the "Fall 2017 mid-semester individual evaluations" assignment
- Iteration 3 evaluations are out -- you have 2 weeks from their release (until Nov 20) to request a re-eval
- We hope to have iteration 4 evaluations out later this week
- We will be accepting all of you into CS 4971 shortly
- Remember you have to report hours at least once each iteration
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day

<h2>Twitter Verification</h2>
<img src="http://imgs.xkcd.com/comics/twitter_verification.png" title="When we started distributing special status tokens that signify which people are important enough to join an elite group, we never could have imagined we might be creating some problems down the line." alt="Twitter Verification" srcset="http://imgs.xkcd.com/comics/twitter_verification_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1914/">xkcd # 1914</a></p>

## Monday, November 13th
- Office hours are in the [syllabus](syllabus.html)
- We are at the end of iteration 4
  - Leads: your TPS reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
  - With the end of iteration 4, we will have another *phase change*: new leads and new secretaries
  - And the *phase change survey*, which you can access now (URL is in PostEm)
    - That's due by the end of next Monday
- Mid-semester individual evaluations are ready -- more on this in a bit
- Iteration 3 evaluations are out -- you have 2 weeks from their release (until Nov 20) to request a re-eval
  - The unit test counts have just been updated, so please check those as well
- We hope to have iteration 4 evaluations out later this week
- We will be accepting all of you into CS 4971 shortly
- Remember you have to report hours at least once each iteration
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day

## Individual evaluations
- You can view these in the PostEm tab of the course management system
- These are not used *directly* in determining the final course grade
  - We will re-determine things at the end of the semester; that updated one will count in your final grade
  - But it provides a good idea of what we are thinking at this point
- Many of the fields are information stored elsewhere
  - Reported hours, content from the evaluations, etc.
- Other fields can't be determined until the end of the semester
- The most important fields are:
  - unexcused absences
  - iterations without any reported times
  - surveys not completed (although everybody currently has zero here)
  - <font color='red'>mid-semester individual rating of the work you are doing (the "work-done" rating)</font>
  - mid-semester individual rating comments
  - notes, resposnes, and special cases -- this is all 1 field and generally blank at this point
- Everything other than the two individual rating fields can be found elsewhere
- I'll pause while you all go look it up...

## Individual evaluation notes
- This was through the end of iteration 3
  - That means a strict cut-off at noon on October 31st; any work since then was not considered for this evaluation
- We will recompute these at the end of the semester
  - So there is time for this to change in either direction, but not a lot of time...
- We did not count unit tests and fixtures when considering your work-done rating
  - Since those were individual, and more like a homework assignment
- As this is a *software engineering capstone* course, you have to actually engineer some software!
  - That means actual contributions to the code base!
  - There were a number of people who did not do so
  - We definitely did look at other work done, but one cannot avoid programming in this course

## Grading Metric
- This was presented on the first day in the course introduction (specifically [here](course-introduction-fall.html#/factor))
- Base metric
  - 45%: iteration evaluations
  - 25%: final project evaluation
  - 10%: homeworks
  - 10%: final exam, project, or presentation
  - 10%: journal entries
  - Leadership will count in here somewhere also...
- Modifications
  - Group work is multiplied by a *factor*, which is an estimate of how much work you did for the group
- Penalties are assessed for various things; these are a percentage of of your final course grade:
  - -3% for each class missed without a valid reason
  - -3% for each iteration with no reported hours
    - We're fine if they are submitted late every now and then
  - -10% for each survey not completed
    - We send you reminders, so no need to worry...

## More individual evaluation notes
- Possible work-done ratings:
  - 1: well below average
  - 1.5: a bit worse than below average
  - 2: below average
  - 2.5: slightly below average
  - 2.75: ever so slightly below average
  - 3: average
  - 3.25: ever so slightly above average
  - 3.5: slightly above average
  - 4: above average
  - 4.5: a bit more than above average
  - 5: well above average

## More individual evaluation notes
- The factor (mentioned on the last slide) is based on your work-done rating
- If you get a 1 ("well below average") for the work-done rating you basically will not pass the course
  - You will have to switch over to the independent capstone track in the spring in order to graduate on time
- Recall that if you get an average of "good" ratings on the group iteration evaluations, and your work-done rating is "average" you are on track to get an A in the course
  - Assuming your other grades are in the A range, and that you don't have penalties
- 45% of the grade is the "iteration evaluations"
  - We scale the ratings of your group so that an average rating score of 3.0 (which means you average as "good") will scale to 93% for this (since 93% is an A grade)
- Why students have typically failed in the past:
  - Low work-done ratings combined with penalties (for not submit times, for not attending class, etc.)
  - A really low work-done rating *or* never showing up to class

## Did we get your evaluation wrong?
- This always happens!
- We do not see everything that goes on in the group, nor all the work that was done
- If you feel we did not properly judge anything in your individual evaluation...
  - Such as attendances, work-done ratings, reported times, etc...
  - Or if you had some special case that we didn't note in the 'comments' field...
- ... then fill out a regrade for the "Fall 2017 mid-semester individual evaluations" assignment
  - You need to include specifics about what we got wrong, what you did, etc.
- You only get one shot at submitting this, so think it over carefully before you submit it!
- We'll keep that regrade open for one week
  - Thus, we'll close it at the end of the day on Monday, November 20th
- We will look it over, and get back to you

## Goals for Iteration 4
- Complete 4 story points worth of work per group member
- Everybody should complete 5 more unit tests
  - You don't need to also do a fixture, as long as you did one in the last iteration
  - This means you should have at least 10 unit tests per team member
  - You must commit your *own* unit tests!
- The wireframes should be (presumably) finalized, and likely implemented, by the end of this iteration
  - Please still keep copies in the docs/wireframes directory in your repo!
- As the iterations continue, there will be fewer specific requirements (other than things like "do work" and "write tests")
- Keep in mind that at the end of iteration 5, you will have to have a preliminary version of the final system running on the course server
  - Here, "the final system" means the system that impelements the minimum requirements
- Are you keeping your reqirements document updated?  You should be!
  - Please put the requirements document in your repo as docs/requirements.md

<h2>Thermostat</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/thermostat.png" title="Your problem is so terrible, I worry that, if I help you, I risk drawing the attention of whatever god of technology inflicted it on you." alt="Thermostat" srcset="http://imgs.xkcd.com/comics/thermostat_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1912/">xkcd # 1912</a></p>

## Wednesday, November 8th
- Office hours are in the [syllabus](syllabus.html)
- The course administration site URL has been changed: it's now https://slp.cs.virginia.edu/admin
- We are in the middle of iteration 4
	- Leads: your weekly reports were due yesterday by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
		- One didn't get it in...
    - Your journal entries were due yesterday as well
- We hope to have the mid-semester evaluations late this week or early next week
- Iteration 3 evaluations are out -- you have 2 weeks (until Nov 20) to request a re-eval
- Remember you have to report hours at least once each iteration
  - We had 14 people not do this in the last iteration, and there is a grade penalty for this...
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day

<h2>Defensive Profile</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/defensive_profile.png" title="NO DRAMA ZONE -> If I've made you sad, you'd better not tell me, because I am TERRIFIED of that situation and have NO IDEA how to handle it." alt="Defensive Profile" srcset="http://imgs.xkcd.com/comics/defensive_profile_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1911/">xkcd # 1911</a></p>

## Monday, November 6th
- Office hours are in the [syllabus](syllabus.html)
- The course administration site URL has been changed: it's now https://slp.cs.virginia.edu/admin
- We are in the middle of iteration 4
    - Leads: your weekly reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- We hope to have the mid-semester evaluations late this week
- Iteration 2 evaluations are out; you have until Nov 6 (today!) to request a re-eval
- Iteration 3 evaluations should be out later today
- Remember you have to report hours at least once each iteration
  - We had 14 people not do this in the last iteration, and there is a grade penalty for this...
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day

## Attendance check-in
- Please do a check-in now:
  - Go to http://tinyurl.com/uvaslpcheckin
    - ***NOTE THE NEW URL*** -- it has "uva" in it now
    - The old one won't work anymore
  - Once that redirects (to https://slp.cs.virginia.edu/admin/checkins/checkin), you will need to log in via Netbadge
  - Enter the code: "winter"
    - Please maintain the same case and what-not
- Remember: if you miss class for a *valid* reason, you can submit an attendance excuse via the course management system

<h2>Digital Resource Lifespan</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/digital_resource_lifespan.png" title="I spent a long time thinking about how to design a system for long-term organization and storage of subject-specific informational resources without needing ongoing work from the experts who created them, only to realized I'd just reinvented libraries." alt="Digital Resource Lifespan" srcset="http://imgs.xkcd.com/comics/digital_resource_lifespan_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1909/">xkcd # 1909</a></p>

## Wednesday, November 1st
- Office hours are in the [syllabus](syllabus.html)
- The course administration site URL has been changed: it's now https://slp.cs.virginia.edu/admin
- We are at the start of iteration 4
    - Leads: your TPS reports were due yesterday by noon; see [here](course-introduction-fall.html#/reportsinfo) for details; somebody forgot theirs...
- We will have the mid-semester evaluations in about a week
- New documents in the repo
    - [Python's virtualenv setup instructions](../docs/virtualenv-setup.html)
    - [Github webhook configuration page](../docs/github-webhook.html); you can also deploy through the other two methods described in the [development environment setup page](../docs/dev-env-setup.html)
- Iteration 2 evaluations are out; you have until Nov 6 to request a re-eval
- Iteration 3 evaluations should be out next Monday
- Remember you have to report hours at least once each iteration
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day
  - As we approach the end of the semester, there are fewer "useful" lectures for me to present
  - We still expect there to be one or two more lectures, though

<h2>Credit Card Rewards</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/credit_card_rewards.png" title="I should make a list of all the things I could be trying to optimize, prioritized by ... well, I guess there are a few different variables I could use. I'll create a spreadsheet ..." alt="Credit Card Rewards" srcset="http://imgs.xkcd.com/comics/credit_card_rewards_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1908/">xkcd # 1908</a></p>

## Monday, October 30th
- Office hours are in the [syllabus](syllabus.html)
  - Mine will end at 2:00 today
- The course administration site URL has been changed: it's now https://slp.cs.virginia.edu/admin
    - Note that there is no port 444 on the URL now
    - Let me (Bloomfield) know if anything doesn't work or is wonky...
- The HWs are all graded; regrades due by the end of Oct (tomorrow!)
- We are at the end of iteration 3
    - Leads: your TPS reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- New documents in the repo
    - [Python's virtualenv setup instructions](../docs/virtualenv-setup.html)
    - [Github webhook configuration page](../docs/github-webhook.html); you can also deploy through the other two methods described in the [development environment setup page](../docs/dev-env-setup.html)
- Iteration 2 evaluations are out; you have until Nov 6 to request a re-eval
- Remember you have to report hours at least once each iteration
- Please update to Django 1.11.6 when you install virtualenv
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day

## Goals for Iteration 3
- Complete 4 story points worth of work per group member
  - Some of this will be the work done on the wireframing, some will be the work done on the CI testing
  - Your site should have significnantly more functionality than last time
- Ensure no valid passwords are stored in the repo (including past history)
- In the first week, complete the end-of-phase survey
- Show the wireframe to the customer, get their feedback, iterate on the design
- Configure your project with virtualenv on the course server; see [here](../docs/virtualenv-setup.html) for details
- You will have to configure your site with [TravisCI](https://travis-ci.com/)
  - The [last two slides](../slides/09-ci-testing.html#/howtobegin) of the [Continuous Integration Testing](../slides/09-ci-testing.html#/) slide set discuss how to begin
  - The CI server is already set up to run tests on your repo on every push
  - You have to write the .travis.yml configuration file to get it to work properly
- Extensive instructions for how to configure it (as well as sample configured projects) are available: the [CI testing slide set](../slides/09-ci-testing.html), the [CI setup](../docs/ci-setup.html) page, and sample configured repo ([django-test](https://github.com/uva-slp/django-test))
    - Because nobody is using Rails or CakePHP, the rails-test and cake-test repos are not being made available
- You will have to write a number of unit tests (at least 5 per person)
  - And one fixture each!  Note that at least one of your tests has to actually *use* that fixture.

<h2>Making Progress</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/making_progress.png" title="I started off with countless problems. But now I know, thanks to COUNT(), that I have "#REF! ERROR: Circular dependency detected" problems." alt="Making Progress" srcset="http://imgs.xkcd.com/comics/making_progress_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1906/">xkcd # 1906</a></p>

## Wednesday, October 25th
- Office hours are in the [syllabus](syllabus.html)
- The course administration site URL has been changed: it's now https://slp.cs.virginia.edu/admin
    - Note that there is no port 444 on the URL now
    - Redirects should all be in place, but change any existing bookmarks
    - Let me (Bloomfield) know if anything doesn't work or is wonky...
- The HWs are all graded; regrades due by the end of Oct
- We are in the middle of iteration 3
    - Leads: weekly reports were due yesterday by noon; see [here](course-introduction-fall.html#/reportsinfo) for details; everybody got them in!
    - Your journal entries were due yesterday by noon; you can submit them late until Friday at noon
- New documents in the repo
    - [Python's virtualenv setup instructions](../docs/virtualenv-setup.html)
	- [Github webhook configuration page](../docs/github-webhook.html); you can also deploy through the other two methods described in the [development environment setup page](../docs/dev-env-setup.html)
- Iteration 2 evaluations are out; you have until Nov 6 to request a re-eval
- Remember you have to report hours at least once each iteration
- Please update to Django 1.11.6 when you install virtualenv
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a CI testing work day

## Grades and such
- There are a [number of things](course-introduction-fall.html#/decrement) that decrement your grades in this class
    - These were gone over in the [course introduction slide set](course-introduction-fall.html#/)
- In particular:
    - Not submitting your hours at least once per iteration
    - Missing class without a valid attendance excuse
	- Not completing your journaling entries
- There are a bunch of you who are not doing these things!
- So, as a friendly reminder, please don't forget to do them...

## Today's task
- Today we will be working on the CI testing setup
- No groups are fully there yet (which is fine, since it's due at the end of the iteration)
  - 5 (of 15) groups have passing builds, but nobody has a significant number of their unit tests written yet
  - In addition, recall that each *person* must contribute at least 5 valid test cases (and one fixture per person; and at least one test must use that fixture)
- To do today:
  - Get Travis configured for your project: extensive instructions for how to configure it (as well as sample configured projects) are available: the [CI testing slide set](../slides/09-ci-testing.html#/), the [CI setup page](../docs/ci-setup.html), and two sample configured repos: ([cake3-test](https://github.com/uva-slp/cake3-test), [django-test](https://github.com/uva-slp/django-test), and [rails-test](https://github.com/uva-slp/rails-test))
  - Contribute the desired number of unit tests (at least 5 per person)
- At the end of today's class, all the build status badges should be green!
- A note about container usage
  - We only have one container for all 15 groups; this will cause delays if everybody pushes their commits around the same time, as they get queued up
  - If you are just writing unit tests, then please hold off on pushing those to let all the groups configure their builds (i.e., generate green status bars)
  - You should be able to run the unit tests in your development environment, so you can confirm to yourself that they works

## A rule for today...
- If you are configuring your repo, then please commit and push when you think you have configured it
- If you are just writing unit tests, please *DON'T* push, as we don't want to fill up the queue at this point
- I want to let those configuring the repos to have their pushes go through first

## Attendance check-in
- Please do a check-in now:
  - Go to http://tinyurl.com/uvaslpcheckin
    - ***NOTE THE NEW URL*** -- it has "uva" in it now
    - The old one won't work anymore
  - Once that redirects (to https://slp.cs.virginia.edu/admin/checkins/checkin), you will need to log in via Netbadge
  - Enter the code: "travis"
    - Please maintain the same case and what-not
- Remember: if you miss class for a *valid* reason, you can submit an attendance excuse via the course management system

CI Testing Status

amazonaid
bigevent
carobotics
cyberbadges
gardeners
gordie
housing

hspcreg
jaunt
meals
pride
quiztool
sara
servicedogs
wildrock

This page refreshes every 30 seconds

This page last updated on: ...

This page will not display the tokens properly unless you manually change the TravisCI token in the HTML code of this page, and remove all the HTML comment tags

<h2>Research Risks</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/research_risks.png" title="The 1919 Great Boston Molasses Flood remained the deadliest confectionery containment accident until the Canadian Space Agency's 2031 orbital maple syrup delivery disaster." alt="Research Risks" srcset="http://imgs.xkcd.com/comics/research_risks_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1904/">xkcd # 1904</a></p>

## Monday, October 23rd
- Office hours are in the [syllabus](syllabus.html)
- The course administration site URL has been changed: it's now https://slp.cs.virginia.edu/admin
    - Note that there is no port 444 on the URL now
    - Redirects should all be in place, but change any existing bookmarks
    - Let me (Bloomfield) know if anything doesn't work or is wonky...
- The homeworks are all graded and returned
    - Regrades need to be submitted by the end of October
- We are in the middle of iteration 3
    - Leads: your weekly reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
    - Your journal entries are due tomorrow by noon
- The [phase change survey](#/phasechangesurvey) must be completed!
    - Why don't you do that right after these announcements end?
- Iteration evaluations for iteration 1 are out; you have until Oct 30 to chat with Inkee about a possible re-evaluation
- We hope to have iteration 2 evals released today
- Remember you have to report hours at least once each iteration
- Please update to Django 1.11.6 when you install virtualenv
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today is a group work day; Wednesday is a CI testing work day

<h2>Bun Trend</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/bun_trend.png" title="Our experts have characterized the ecological impact of this trend as "adorable."" alt="Bun Trend" srcset="http://imgs.xkcd.com/comics/bun_trend_2x.png 2x"/>
<p class="center"><a href="http://xkcd.com/1903/">xkcd # 1903</a></p>

## Wednesday, October 18th
- Office hours are in the [syllabus](syllabus.html)
- Yes, the spring version is at 10 a.m.  No, we can't change it.
- The homeworks are all graded and returned
    - You can see the grades, and submit regrade requests, through the course management system
    - This needs to be done within two weeks (by the end of October)
- We are at the start of iteration 3
    - Leads: your TPS reports were due yesterday by noon; see [here](course-introduction-fall.html#/reportsinfo) for details; everybody got them in!
- With the end of iteration 3, we have a *phase change*
    - New leads and new secretaries (incoming project lead emails went out last night)
    - The phase change survey (more on that shortly)
- Iteration evaluations for iteration 1 were released last week
    - You have two weeks to chat with Inkee about them (so during your next meeting)
- We hope to have iteration 2 evals released by next Monday
- Remember you have to report hours at least once each iteration
- Remember about how to [reserve a room for the meetings](#/meetingsrsvp); and about the [meeting report format](course-introduction-fall.html#/meetingreport)
- Django 1.11.6 just came out; please update
  - You can do this when you install virtualenv
- The course server will have a bit of downtime "soon" (< 15 mins)
- Today will be a lecture on [continuous integration testing](../slides/09-ci-testing.html)

## Phase change survey
- Everybody has to fill it out!
  - It's a course requirement
- The *ONLY* people in the class that will see the results are myself and the instructors
  - I encourage you to be open an honest, and I promise I will preserve your anonyminity
- It should take about 10 minutes to complete
- The same survey will be completed after each phase
  - So you will have to complete as many as there are members in your group
- You can see the questions asked in Collab under Resources/surveys/phase-chage (it's one page, and can be found [here](https://collab.its.virginia.edu/access/content/group/9d516a99-7444-481d-b79c-521b6f1ad522/surveys/phase-change/phase-change-survey.html))
- There is about a week-long period to fill it out
  - There is a big grade penalty for not filling it out (or just giving quick dummy answers)
- The URL for the survey is in the PostEm in the course management system
- There is a *timeout* issue with regard to filling out surveys
  - LimeSurvey (the survey tool being used) will time you out after 10 (or so) minutes -- and then you'll have to start over!
  - So, if you want to spend time thinking about the responses, look over the survey in Collab first!
  - If you do get timed out, I can send you your saved responses (if you saved them through the survey)

## CI Testing Setup
- Today is the lecture on [continuous integration testing](../slides/09-ci-testing.html#/)
- All of you now have access to the [django-test](https://github.com/uva-slp/django-test) repo
  - You will only need to use the one that corresponds to the platform you are using
  - Note that it's a slightly older version of the framework, but the setup should be the same
  - Let me know if anything doesn't work!
- I will shortly be enabling TravisCI for all of your repos
  - It will email you when a build fails; I wanted to warn you about this before I flipped the switch
  - Note that if a lot of people push their commits at the same time, it will form a long queue of the ones waiting to be tested
- We are not using CircleCI this year
- There is an entire page named [Continuous Integration Testing: Getting Started](../docs/ci-setup.html), and you should read that and the [CI testing slide set](../slides/09-ci-testing.html#/)

## Attendance check-in
- Please do a check-in now:
  - Go to http://tinyurl.com/slpcheckin
  - Once that redirects (to https://slp.cs.virginia.edu:444/admin/checkins/checkin), you will need to Netbadge in
  - Enter the code: "travel"
    - Please maintain the same case and what-not
- Remember: if you miss class for a *valid* reason, you can submit an attendance excuse via the course management system

<h2>State Borders</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/state_borders.png" title="A schism between the pro-panhandle and anti-panhandle factions eventually led to war, but both sides spent too much time working on their flag designs to actually do much fighting." alt="State Borders" srcset="http://imgs.xkcd.com/comics/state_borders_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1902/">xkcd # 1902</a></p>

## Monday, October 16th
- Office hours are in the [syllabus](syllabus.html)
- The homeworks are all graded and returned
    - You can see the grades, and submit regrade requests, through the course management system
    - This needs to be done within two weeks (by the end of October)
- We are at the end of iteration 2
    - Leads: your TPS reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- Iteration evaluations for iteration 1 were released last week
    - You have two weeks to chat with Inkee about them (so during your next meeting)
- Remember you have to report hours at least once each iteration
- Remember about how to [reserve a room for the meetings](#/meetingsrsvp); and about the [meeting report format](course-introduction-fall.html#/meetingreport)
- Web hooks coming soon...
- The course server will have a bit of downtime "soon" (hopefully less than 15 minutes a piece)
- Today will be a group work day; Wednesday will be a lecture on continuous integration testing

## Grad TA meeting schedule
- First Friday of an iteration (starts Oct 6):
    - 11:00-11:30: bigevent (in Rice 504)
	- 11:30-12:00: servicedogs (in Rice 504)
	- 1:30-2:00: amazonaid (in Rice 504)
	- 2:00-2:30: sara (in Rice 108)
	- 2:30-3:00: cyberbadges (in Rice 108)
	- 3:00-3:30: carobotics (in Rice 108)
- Second Tuesday of an iteration (starts Oct 9):
    - 1:00-1:30: housing (in Rice 414)
- Second Thursday of an iteration (starts Oct 10):
    - 6:15-6:45: wildrock (in Rice 534)
- Second Friday of an iteration (starts Oct 13):
    - 10:30-11:00: gordie (in Rice 504)
	- 11:00-11:30: quiztool (in Rice 504)
	- 11:30-12:00: meals (in Rice 504)
	- 1:30-2:00: gardeners (in Rice 504)
	- 2:00-2:30: jaunt (in Rice 108)
	- 2:30-3:00: pride (in Rice 108)
	- 3:00-3:30: hspcreg (in Rice 108)
- Remember that EVERYBODY needs to attend this meeting!

## Goals for Iteration 2
- Have a site that should start to look like a workable site for the requirements
  - Some just had one or two MVC components for the first iteration (which was fine, as that is what was required for then)
  - Going to http://server/tag should bring up something other than "Hello World", or the Django error page
- Complete 4 story points worth of work per group member
- Your regular iteration meeting with the customer and the grad TA should happen
- Specific goals:
  - Generate wireframes: that's [an entire lecture](../slides/08-wireframing.html#/); this will likely take 3 or 5 story points of work.  The intent is to show them to the customer in iteration 3
  - Enable easy deployment via automatic logins or ssh keys: see the [Development Environment Setup page](http://aaronbloomfield.github.io/slp/docs/dev-env-setup.html) for details.  This also includes enabling easy downloading of the database
  - Publishing to the course server is best done via a github web hook and deploy key; see [that same page](http://aaronbloomfield.github.io/slp/docs/dev-env-setup.html) for details, but only I can set up both of those due to the github security setup
  - Ensure that *everybody* in the development group can develop on his/her own machine
- Some things to keep in mind:
  - Your requrements document will be iterated on throughout the year
  - What format you keep it in is up to you (although we recommend markdown), but we need to be able to view it
  - Having the source (from the [uva-slp/projects repo](https://github.com/uva-slp/projects) repo) copied into a `docs/` directory in your repo is quite reasonable

## Monday, October 9th
- Office hours are in the [syllabus](syllabus.html)
- The homeworks are all graded, and just have to be loaded (likely this week)
- We in the middle of iteration 2
    - Leads: your weekly reports are due tomorrow by noon; see [here](course-introduction-fall.html#/reportsinfo) for details
- Iteration evaluations will be out later this week (they are delayed a bit)
- Remember you have to report hours at least once each iteration
- Remember about how to [reserve a room for the meetings](#/meetingsrsvp); and about the [meeting report format](course-introduction-fall.html#/meetingreport)
- Your journal prompt for iteration 2 is out, and is due tomorrow by noon
- Remember that you have to [upgrade to Django 1.11.5](#/dupgrade)
- PostEms have now moved to the [course administration system](https://slp.cs.virginia.edu:444/admin/)
- The course server will have a bit of downtime "soon" (hopefully less than 15 minutes a piece)
- Today will be a group work day; Wednesday will be a lecture on wireframes

## Grad TA meeting schedule
- First Friday of an iteration (starts Oct 6):
    - 11:00-11:30: bigevent (in Rice 504)
	- 11:30-12:00: servicedogs (in Rice 504)
	- 1:30-2:00: amazonaid (in Rice 504)
	- 2:00-2:30: sara (in Rice 108)
	- 2:30-3:00: cyberbadges (in Rice 108)
	- 3:00-3:30: carobotics (in Rice 108)
- Second Tuesday of an iteration (starts Oct 9):
    - 1:00-1:30: housing (in Rice 414)
- Second Friday of an iteration (starts Oct 13):
    - 10:30-11:00: gordie (in Rice 504)
	- 11:00-11:30: quiztool (in Rice 504)
	- 11:30-12:00: meals (in Rice 504)
	- 1:30-2:00: gardeners (in Rice 504)
	- 2:00-2:30: jaunt (in Rice 108)
	- 2:30-3:00: pride (in Rice 108)
	- 3:00-3:30: hspcreg (in Rice 108)
- Not yet scheduled: wildrock :-(
- Remember that EVERYBODY needs to attend this meeting!

<h2>Self Driving</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/self_driving.png" title=""Crowdsourced steering" doesn't sound quite as appealing as "self driving."" alt="Self Driving" srcset="http://imgs.xkcd.com/comics/self_driving_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1897/">xkcd # 1897</a></p>

## Wednesday, October 4th
- Office hours are in the [syllabus](syllabus.html)
- The homeworks are (mostly) all finished and are being graded
- We are at the start of iteration 2
    - It's not a phase change, so no iteration survey or leadership switch
- Leads: your TPS report was due yesterday; everybody got it in!
- Remember you have to report hours at least once each iteration
- Remember about how to [reserve a room for the meetings](#/meetingsrsvp); and about the [meeting report format](course-introduction-fall.html#/meetingreport)
- Your journal prompt for iteration 2 will be out later today, and is due next Tuesday by noon (partial credit available until Friday at noon)
- Remember that you have to [upgrade to Django 1.11.5](#/dupgrade)
- PostEms have now moved to the [course administration system](https://slp.cs.virginia.edu:444/admin/)
- The course server will have a bit of downtime "soon" (hopefully less than 15 minutes a piece)
- Because we did not have class on Monday, we'll have group meetings today

## End of iteration 1
- After each iteration, you will receive an *iteration evaluation*
    - Should be out by the next Monday's class
- It will have a paragraph for the *entire* group, as well as a progress rating (excellent, good, fair, poor, none)
    - That is the group grade!
	- Keep in mind that the group grades are modified by the [work-done factor](course-introduction-fall.html#/factor)
		- We'll have an estimate of this in early November
- It will also have:
    - Your attendances (or lack thereof)
	- Project lead or secretary duties summary (if appropriate)
	- Whether you reported your times or not
    - Some of them may have comments, but most won't
- If you feel that we did not evaluate you or your group properly (or missed something, etc.) please speak to the grad TA within 2 weeks
    - So at your next TA meeting with him
    - Unless there are exception circumstances, we will *not* allow re-evaluations after the 2 week period

## Grad TA meeting schedule
- First Friday of an iteration (starts Oct 6):
    - 11:00-11:30: bigevent (in Rice 504)
	- 11:30-12:00: servicedogs (in Rice 504)
	- 1:30-2:00: amazonaid (in Rice 504)
	- 2:00-2:30: sara (in Rice 108)
	- 2:30-3:00: cyberbadges (in Rice 108)
	- 3:00-3:30: carobotics (in Rice 108)
- Second Tuesday of an iteration (starts Oct 9):
    - 1:00-1:30: housing (in Rice 414)
- Second Friday of an iteration (starts Oct 13):
    - 10:30-11:00: gordie (in Rice 504)
	- 11:00-11:30: quiztool (in Rice 504)
	- 11:30-12:00: meals (in Rice 504)
	- 1:30-2:00: gardeners (in Rice 504)
	- 2:00-2:30: jaunt (in Rice 108)
	- 2:30-3:00: pride (in Rice 108)
	- 3:00-3:30: hspcreg (in Rice 108)
- Not yet scheduled: wildrock :-(
- Remember that EVERYBODY needs to attend this meeting!

<h2>Real Estate</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/real_estate.png" title="I tried converting the prices into pizzas, to put it in more familiar terms, and it just became a hard-to-think-about number of pizzas." alt="Real Estate" srcset="http://imgs.xkcd.com/comics/real_estate_2x.png 2x">
<p class="center"><a href="http://xkcd.com/1894/">xkcd # 1894</a></p>

## Wednesday, September 27th
- Office hours are in the [syllabus](syllabus.html)
- The homeworks are (mostly) all finished and are being graded
    - [HW 6: Iteration checklist](../docs/hw6-iteration-checklist.html) is due this Friday by midnight
- We are half-way through iteration 1
- Leads: your first report was due yesterday; everybody got it in!
- Remember you have to report hours at least once each iteration
- Remember about how to [reserve a room for the meetings](#/meetingsrsvp); and about the [meeting report format](course-introduction-fall.html#/meetingreport)
- Your journal prompt was due yesterday by noon; see [here](#/journaling) for details (partial credit available until Friday at noon)
- Remember that you have to [upgrade to Django 1.11.5](#/dupgrade)
- PostEm has now moved to the [course administration system](https://slp.cs.virginia.edu:444/admin/)
- The course server will have a bit of downtime this week (hopefully less than 15 minutes a piece)
- TA meeting times & locations will be out soon
- Today is a an [estimation workday](../slides/07-estimation.html#/)

## Basecamp
- Your basecamp projects are all set up
- To join, you have to follow the URL given in the `basecamp_url` field of your "Accounts" PostEm
  - Which is now in the course management system
  - In theory, that should allow you to join (you likely will have to create an account)
- Basecamp is meant to handle inter-group communication
  - Chats, message boards, to-do lists, scheduling, documents & files, etc.
- It is <font color='red'>NOT</font> to be used in lieu of the things that we are using github for
  - We'll see these today, but they include: issues, story points, backlogs, and file storage
- Everybody has to join in *this* iteration (it's now a listed [iteration goal](iteration-goals.html#/))

## Goals for iteration 1
See [here](../slides/05-project-start.html#/it1goals) for full details, but briefly:
- Fully understand the requirements
- Meet with the customer
- Design (and implement) a basic DB schema
- Get your development environment set up (see the [slp docs](../docs/index.html) and [uva-slp/tutorails](https://github.com/uva-slp/tutorials) for guidance)
- Get a basic MVC site working on the course server
  - Once done, you have to email me so that I can complete the apache2 configuration
- Have the system stored properly in the github repo (no passwords!!!)
  - That means having all your framework created files in an app/ (or similar) folder
- Enter all the requirements as tasks as Github issues (today)
- Everybody MUST have a github commit this iteration (and, in general, every iteration)
- Everybody must add themselves to their basecamp project

## Attendance check-in
- Please check-in now http://tinyurl.com/slpcheckin
- Today's code: mountain
- Please check in *now*; I'll wait!
- Remember: if you miss class for a *valid* reason, you can submit an attendance excuse via the course management system