-
Notifications
You must be signed in to change notification settings - Fork 15
/
daily-announcements.html
2092 lines (1780 loc) · 126 KB
/
daily-announcements.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>CS 4970: daily-announcements slide set</title>
<meta name="description" content="A set of slides for UVa's Service Learning Practicum course">
<meta name="author" content="Aaron Bloomfield">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="../slides/reveal.js/css/reveal.css">
<link rel="stylesheet" href="../slides/reveal.js/css/theme/black.css" id="theme">
<link rel="stylesheet" href="../slides/css/slp.css">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="../slides/reveal.js/lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? '../slides/reveal.js/css/print/pdf.css' : '../slides/reveal.js/css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="../slides/reveal.js/lib/js/html5shiv.js"></script>
<![endif]-->
<script type="text/javascript" src="../slides/js/dhtmlwindow.js"></script>
<script type="text/javascript" src="../slides/js/canvas.js"></script>
<link rel="stylesheet" href="../slides/css/dhtmlwindow.css" type="text/css">
<style>
.reveal li {
font-size:70%;
line-height:120%;
}
</style>
</head>
<body>
<div id="dhtmlwindowholder"><span style="display:none"></span></div>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section data-markdown><script type="text/template">
# CS 4970
### Capstone Practicum I
### Fall 2017
<center><small>[Aaron Bloomfield](http://www.cs.virginia.edu/~asb) / [[email protected]](mailto:[email protected]) / [@bloomfieldaaron](http://twitter.com/bloomfieldaaron)</small></center>
<center><small>Repository: [github.com/aaronbloomfield/slp](http://github.com/aaronbloomfield/slp) / [↑](../slides/index.html) / <a href="daily-announcements.html?print-pdf"><img class="print" width="20" src="../slides/images/print-icon.png"></a></small></center>
## Daily Announcements
</script></section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Felsius</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/felsius.png" title="The symbol for degrees Felsius is an average of the Euro symbol (€) and the Greek lunate epsilon (ϵ)." alt="Felsius" srcset="http://imgs.xkcd.com/comics/felsius_2x.png 2x"/>
<p class="center"><a href="http://xkcd.com/1923/">xkcd # 1923</a></p>
</section>
<section data-markdown data-separator="^\n$"><textarea data-template>
## 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
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
## 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
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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)
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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 "[email protected]"
```
- 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
## 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)
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
## 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 "[email protected]"
```
- 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
## 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)
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
## 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
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
## 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
## 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
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
## 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
## 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
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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.
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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...
## 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.
## 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
</textarea></section>
<section id="cistatus"><h2>CI Testing Status</h2>
<table class="transparent" style="font-size:18pt"><tr><td>
<table class="transparent" style="font-size:18pt">
<tr><td style="border-bottom:0px">amazonaid</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/amazonaid"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/amazonaid.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">bigevent</td><td style="border-bottom:0px"><!-- <a href="https://circleci.com/gh/uva-slp/bigevent"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/bigevent.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">carobotics</td><td style="border-bottom:0px"><!-- <a href="https://circleci.com/gh/uva-slp/carobotics"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/carobotics.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">cyberbadges</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/cyberbadges"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/cyberbadges.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">gardeners</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/gardeners"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/gardeners.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">gordie</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/gordie"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/gordie.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">housing</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/housing"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/housing.svg?token=travistoken"></a> --></td></tr>
</table>
</td><td> </td><td>
<table class="transparent" style="font-size:18pt">
<tr><td style="border-bottom:0px">hspcreg</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/hspcreg"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/hspcreg.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">jaunt</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/jaunt"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/jaunt.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">meals</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/meals"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/meals.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">pride</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/pride"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/pride.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">quiztool</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/quiztool"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/quiztool.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">sara</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/sara"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/sara.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">servicedogs</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/servicedogs"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/servicedogs.svg?token=travistoken"></a> --></td></tr>
<tr><td style="border-bottom:0px">wildrock</td><td style="border-bottom:0px"><!-- <a href="https://magnum.travis-ci.com/uva-slp/wildrock"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/wildrock.svg?token=travistoken"></a> --></td></tr>
</table>
</td></tr></table>
<p>This page refreshes every 30 seconds</p>
<p style="font-size:18px">This page last updated on: <span id="cistatusdate">...</span></p>
<script>
var now = new Date();
document.getElementById("cistatusdate").innerHTML = now;
</script>
<p style="font-size:18px">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
</section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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
## 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.
</textarea></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section data-markdown data-separator="^\n$"><textarea data-template>
<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)
## 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.
</textarea></section>
<section data-markdown id="phasechangesurvey"><textarea data-template>
## Phase change survey
- Everybody has to fill it out!
- It's a course requirement