CS 4970

Wednesday, December 3rd, 2014

• We are at the start of iteration 6
• Customer meetings in 1 line: reports (1 sentence) but not w/Jamie; name tags
• Everybody got their TPS reports submitted!
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out through iteration 4
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (for iteration 2) or Jamie (for the other iteraitons) during office hours or the meeting, and we will re-do the evaluation
• We expect iteration 5 evaluations to be out next Monday
  • Iteration 6 will be slightly different, as there will be an end of the semester evaluation in lieu of iteration 6's evaluation
• It is very bad of your CI testing does not work
• Today is a group work day, and our last class meeting until January 12th

Final Projects: Tutorials

• The project is to write a tutorial on something that you had to work through this semester
  • Something that, if you had had a tutorial ahead of time, would have saved you time or effort
  • It must be something that there does not exist a tutorial already online
• They are due at the end of the normal final exam period (Mon, Dec 15 @ noon)
• Everybody will have to one (individually) or convert two (from an older format)
  • Note that conversion means making sure that it still works!
• The format will be Markdown
  • There is a repo that everybody will fork: uva-slp/tutorials
    • You may want to unwatch it to avoid receiving all the notifications...
  • The README.md contains instructions for topic reservation and how to complete the tutorial (which is dine via a pull request)
• This is meant to take about 3 hours, which is the time a final exam would take
• This will count in lieu of your final exam, which will be a non-insignificant part of your final grade
• In an effort to keep this sane for us, will are going to insist that you please follow the directions laid out in that tutorial

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
    • This means that most (if not all) of your minimum requirements should be implemented!
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Updated things to be completed this semester

• Finish development through iteration 6
  • This means that your CI testing had better be green!
• Everybody should continue to report your hours
• Leads: submit your weekly and TPS reports on the next two Mondays
• Email your customer to start using the system
  • More info on this from me soon; you will also have to CC me on that
• Complete your tutorial(s) and submit via a pull request
• Complete the last end-of-phase survey (released on Sun, Dec 14)
• Have your final group meeting/presentation with Jamie (details to follow)
• Upload your STS prospectus (if you are using SLP for your technical project)
  • Last night I emailed all those who have not yet done so

Note that you will receive an incomplete if any of these things are not done when I submit the final grades!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• Alzheimers: issue #103
• Hope's Legacy: issue #291

You can give a tag of "story-points-none" if the task is not worth any story points

Holiday Break

• I will do my best not to bother you until we return. But...
• If something goes wrong with the system, or the customer can't use it, then I'll start sending emails
• The customer may (or may not) email you
  • In the directions for the "hand-off", I'll suggest a way to phrase it so that they give you all of their comments once you return
• My hope is that I don't have to contact anybody (I want a break from course work too...)

Preview of next semester

• There will be 8 iterations instead of 6
  • The first 5 will be development; the last 3 deployment
  • 6 and 7 person groups will have a different phase schedule as a result
  • Desired requirements are due by March 23rd, 2015 (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
  • I will guide you through all of these
• And, of course, lots of progress on your projects!

Monday, December 1st, 2014

• We are at the end of iteration 5
• Customer meetings in 1 line: reports (1 sentence) but not w/Jamie; name tags
• Leads: your TPS reports are due by noon tomorrow
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out through iteration 4
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (for iteration 2) or Jamie (for the other iteraitons) during office hours or the meeting, and we will re-do the evaluation
• It is very bad of your CI testing does not work
• Today is a group work day; it will also be a group work day on Wednesday

Final Projects: Tutorials

• The project is to write a tutorial on something that you had to work through this semester
  • Something that, if you had had a tutorial ahead of time, would have saved you time or effort
  • It must be something that there does not exist a tutorial already online
• They are due at the end of the normal final exam period (Mon, Dec 15 @ noon)
• Everybody will have to one (individually) or convert two (from an older format)
  • Note that conversion means making sure that it still works!
• The format will be Markdown
  • There is a repo that everybody will fork: uva-slp/tutorials
    • You may want to unwatch it to avoid receiving all the notifications...
  • The README.md contains instructions for topic reservation and how to complete the tutorial (which is dine via a pull request)
• This is meant to take about 3 hours, which is the time a final exam would take
• This will count in lieu of your final exam, which will be a non-insignificant part of your final grade
• In an effort to keep this sane for us, will are going to insist that you please follow the directions laid out in that tutorial

Wait, you already had tutorials???

• Well, yes, technically
• But they were either:
  • For a different API version (CakePHP's tutorials were all prior to the 3.0 API; Rails' tutorials were for a different version also)
  • Not for the desired language (no Django tutorials)
  • Mostly for things in Ruby that were either covered by the intro tutorial or things people have not yet gotten to
• And they are in all different formats, and most are outdated
• That's why they haven't been released until now...

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
    • This means that most (if not all) of your minimum requirements should be implemented!
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Things to be completed this semester

• Finish development through iteration 6
  • This means that your CI testing had better be green!
• Email your customer to start using the system
  • More info on this soon
  • You also have to CC me
• Complete your tutorial(s) and submit via a pull request
• Complete the last end-of-phase survey
• Have your final group meeting/presentation with Jamie
• Upload your STS prospectus (if you are using SLP for your technical project)

Note that you will receive an incomplete if any of these things are not done when I submit the final grades!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• WTJU: issue #78

You can give a tag of "story-points-none" if the task is not worth any story points

Monday, November 24th, 2014

• We are half-way through iteration 5
  • Last week was a phase change, and an end-of-phase survey to complete
• Customer meetings in 1 line: reports (1 sentence) but not w/Jamie; name tags
• Leads: your weekly reports are due by noon tomorrow
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out through iteration 4 (just released)
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (for iteration 2) or Jamie (for the other iteraitons) during office hours or the meeting, and we will re-do the evaluation
• Today is a group work day; there is no class on Wednesday

Final Projects and Presentations

• Final projects
  • The project is to write a tutorial on something that you had to work through this semester
    • Something that, if you had had a tutorial ahead of time, would have saved you time or effort
    • It must be something that there does not exist a tutorial already online
    • There will be a topic reservation system; details to follow
  • Everybody will have to one (individually) or convert two (from an older format)
    • Note that conversion means making sure that it still works!
  • The format will be Markdown
    • There will be a single repo that everybody will fork: uva-slp/tutorials
    • The README.md will contain the instructions for how to complete the tutorial; it is submitted via a pull request
  • This is meant to take about 3 hours, which is the time a final exam would take
  • This will count for 82954% of your final grade
  • More details after Thanksgiving -- you'll receive a notification that you were added to the uva-slp/tutorials repo
• Final presentations: still working out the details (they may not happen)...

Wait, you already had tutorials???

• Well, yes, technically
• But they were either:
  • For a different API version (CakePHP's tutorials were all prior to the 3.0 API; Rails' tutorials were for a different version also)
  • Not for the desired language (no Django tutorials)
  • Mostly for things in Ruby that were either covered by the intro tutorial or things people have not yet gotten to
• And they are in all different formats, and most are outdated
• That's why they haven't been released until now...

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
    • This means that most (if not all) of your minimum requirements should be implemented!
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• Band: issue #39
• JAUNT: issue #93

You can give a tag of "story-points-none" if the task is not worth any story points

Monday, November 17th, 2014

• We at the end of iteration 4; iteration 5 starts tomorrow
  • This means a phase change: new leads and new secretaries
  • And an end-of-phase survey, which I will release later today
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your TPS reports are due by noon tomorrow
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• The (customer) meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out through iteration 3 (released last week)
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (for iteration 2) or Jamie (for iteraitons 1 and 3) during office hours or the meeting, and we will re-do the evaluation
• Today is a group work day

Wednesday's lecture

• John Feminella, a local software engineer, will be giving a guest talk
  • LinkedIn: http://linkedin.com/in/johnxf
  • Stack Overflow: http://stackoverflow.com/users/75170/
  • Github: http://github.com/fj
  • Twitter: @jxxf
• As per your requests, it will be on "software engineering in the real world" with a heavy focus on (1) what working in a startup is like, (2) what kinds of tools we use in our workflow, and (3) his professional experience
• Don't be late! I will get VERY cranky if you all show up late!

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
    • This means that most (if not all) of your minimum requirements should be implemented!
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• Hope's Legacy: issue #239

You can give a tag of "story-points-none" if the task is not worth any story points

Wednesday, November 12th, 2014

• We are one week into iteration 4
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your weekly reports were due yesterday by noon
  • Everybody got them in!
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out through iteration 3 (which was just released)
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (for iteration 2) or Jamie (for iteraitons 1 and 3) during office hours or the meeting, and we will re-do the evaluation
• Thinking about grad school? Attend the CS grad school session on Thu @ 7 p.m. in OLS 005
• Today will be a CI testing work day

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• JAUNT: issues 60 and 63

You can give a tag of "story-points-none" if the task is not worth any story points

Today's task

• Today we will be working on the CI testing setup
• Only one group is fully there yet (which is fine, since it's due at the end of the iteration)
  • 7 groups have passing builds, but only one of those seven have all the unit tests configured
  • Recall that each person must contribute at least 5 valid test cases (and one fixture per person)
• To do today:
  • Get Travis or Circle configured for your project; see the CI testing slide set for details
  • Contribute the desired number of unit tests (at least 5 per person)
• At the end of today, all the build status badges should be green!

CI Testing Status

• Alzheimer's Association:
• The Arbor:
• CARS:
• Band:
• Hope's Legacy:
• Innisfree Village:
• JAUNT:
• Loaves and Fishes:
• Madison House:
• Service Dogs:
• The Haven:
• Shelter for Help in Emergency:
• TJACE:
• Wintergreen Adaptive Sports:
• WTJU 91.1 FM:

This page refreshes every 30 seconds

Monday, November 10th, 2014

• We are one week into iteration 4
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your weekly reports are due tomorrow by noon
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out through iteration 3 (which was just released last night)
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (for iteration 2) or Jamie (for iteraitons 1 and 3) during office hours or the meeting, and we will re-do the evaluation
• Today is a group meeting day

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Guest talk

• Next week we will have a guest lecturer: John Feminella
  • LinkedIn: http://linkedin.com/in/johnxf
  • Stack Overflow: http://stackoverflow.com/users/75170/
  • Github: http://github.com/fj
  • Twitter: @jxxf
• He has a lot of experience with Rails, start-ups, open source, etc.
• He wanted to know what topics you all would like him to cover
• Please fill out the survey at http://tinyurl.com/lqucens
  • That's a lower-case "L" in the url, not the number one

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• jaunt: issues 60 and 63
• haven: issues 9, 13, 22, 31, and 47
• shelter: issues 26, 29, 36, 38, 41, and 47

You can give a tag of "story-points-none" if the task is not worth any story points

Wednesday, November 5th, 2014

• We are starting iteration 4
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your TPS reports were due yesterday by noon
  • One group didn't get it in...
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out for iteration 1 and 2; iteration 3 is coming later this week
  • Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
  • Once that is fixed, come see me (during office hours), and I will re-do the evaluation
• Today we'll talk about Continuous Integration Testing

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • See the details in the Continuous Integration Testing slide set
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• band: issue #33

You can give a tag of "story-points-none" if the task is not worth any story points

Monday, November 3rd, 2014

• We are at the end of iteration 3
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your TPS reports are due tomorrow by noon
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
  • I have it from exactly two groups...
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations out for iteration 1; iteration 2 and 3 coming this week
  • I realize we are a bit late with the first two...
• Continuous integration services: any preferences? We'll be using two: Travis CI and Circle CI
• You can view a graph of your github issue data in the course reporting tool (under 'project details')
  • This is purely for informative purposes -- there is no "right" or "wrong" look to the graph, and thus no grade penalty (or bonus) depending on it's look

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing
    • This will be described in detail in the continuous integration testing slide set discussed on Wednesday
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• arbor: issue 59

You can give a tag of "story-points-none" if the task is not worth any story points

Wednesday, October 29th, 2014

• We are one week into iteration 3
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your first weekly reports were due yesterday by noon (and everybody got them in!)
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• A note about the meeting reports: they should only be 1 sentence!
  • And no need to mention a meeting with Jamie
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
  • I have it from exactly two groups...
• Don't forget to report your hours!!! This is a course requirement!
• Iteration evaluations coming soon!
• Continuous integration services: any preferences? We'll be using two...
• You can view a graph of your github issue data in the course reporting tool (under 'project details')
  • This is purely for informative purposes -- there is no "right" or "wrong" look to the graph, and thus no grade penalty (or bonus) depending on it's look

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing (more on this in a future lecture)
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• nobody! w00t!

  You can give a tag of "story-points-none" if the task is not worth any story points

Today's Task

• Today we are going to investigate whether an online tool, Pivotal Tracker (https://www.pivotaltracker.com) would be worth using for our projects
  • Before having all of you to use it, I want your opinion as to whether it would be useful or not
• What I want to know at the end of today: disregarding the learning curve, would a tool such as Pivotal Tracker help your group's productivity?
• Your task:
  • Turn of Facebook, Twitter, and other social media
  • Split into your project groups, as you will be collaborating on this
  • Create an account on Pivotal Tracker; it's free
  • Create a sample project (not a blank project!)
  • Fool around with the interface to get an idea of what it can do
    • Add stories, modify stuff, understand the UI features, display options, etc.
    • Talk with each other about how this would be used
    • Understand how this integrates with github (just google for "pivotal tracker github integration")
    • You should be spending ~30-40 minutes on all of this -- the idea is for you to really understand how it works!
    • You should be experts at this tool by the end of today's lecture!
  • Fill out the survey at https://libra.cs.virginia.edu/ptsurvey (it's all of 4 questions)
    • This is where you tell me how useful it would be
    • This is also today's attendance, so be sure to fill it out!

Monday, October 27th, 2014

• We are one week into iteration 3
  • Everybody filled out the end-of-phase survey!
• Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
• Leads: your first weekly reports are due tomorrow by noon
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• A note about the meeting reports: they should only be 1 sentence!
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• You can view a graph of your github issue data in the course reporting tool (under 'project details')
  • This is purely for informative purposes -- there is no "right" or "wrong" look to the graph, and thus no grade penalty (or bonus) depending on it's look

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing (more on this in a future lecture)
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Github Story Points
Hall of Shame

Remember that all issues (even closed ones) must have a story points tag. The following do not:

• Alzheimers: issue 65
• WTJU: issues 38, 39, and 41

  You can give a tag of "story-points-none" if the task is not worth any story points

Wednesday, October 22nd, 2014

• We are in the first day of iteration 3
  • We had a phase change with the start of iteration 3
  • New lead and new secretary
  • Everybody has to fill out the end-of-phase survey
  • See here for details on the end of phase and the survey
• Customer meetings: don't forget to submit the meeting report when you have met with them!
  • And don't forget to wear your name tags!
• (Old) leads: your TPS reports were due yesterday by noon
  • Two groups didn't get them in...
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!! This is a course requirement!
• Today is a lecture on documentation

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
  • Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
  • Iteration 4: implement continuous integration testing (more on this in a future lecture)
  • Iteration 5: get a preliminary system that implements the minimum requirements working
  • Iteration 6: get a final system that implements the minimum requirements working
• Keep in mind that iteration 6's goal is what you are working toward this entire semester!

Issues missing story points

Remember that all issues must have a story points tag

• Arbor: issues 39-45
• Band: issue 8
• Jaunt: issue 39
• Madison house: issue 24
• Service dogs: issues 90 and 91
• WTJU: issues 38-41

  You can give a tag of "story-points-none" if the task is not worth any story points

Monday, October 20th, 2014

• We are at the end of iteration 2
• Customer meetings: don't forget to submit the meeting report when you have met with them!
  • And don't forget to wear your name tags!
• Leads: your TPS reports are due tomorrow by noon
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
• Don't forget to report your hours!!!
  • This is a course requirement -- not completing them will result in a failure for the course
• Grades for the first three homeworks have been returned
  • You can submit regrades (through the end of this week) via the course management system when they were returned (Sep 29)
• If you are fine with your git hw grade, PLEASE DELETE YOUR GIT HW REPOS
  • Or you can remove myself and Jamie as collaborators
  • Or you will not get any credit for the assignment
• Today is a group meeting day; Wednesday will be lecture, likely on documentation

Iteration 2 Goals

• You should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Your regular iteration meeting with the customer and Jamie should happen
• Specific goals:
  • Generate wireframes (see the wireframing lecture and consider using jetstrap)
  • Set up everybody's development environment (see the development environment setup (md) page)
    • Enable easy deployment via automatic logins or ssh keys
    • Enable easy downloading of the database
    • Ensure that everybody in the development group can develop on his/her own machine
• Requirements document
  • Your requrements document will be iterated on throughout the year
  • What format you keep it in is up to you, but I need to be able to view it
  • Having the original source (in the uva-slp/projects repo repo) in a docs directory in your repo is quite reasonable

Phase Change

• All groups will have a phase change at the end of iteration 2
  • This means a new lead and new secretary take over
  • The new lead should indicate that they are such to the customer (either by email or at your next meeting)
  • I'll be sending the new leads info on their lead-ness
• And there is an "end-of-phase" survey to complete
  • Completing this survey is a course requirement
  • All info that you put down is confidential -- no other students in this class will see your results
  • I may release averages and such, as long as it preserves anonyminity
  • I will not be basing your grades on your responses, so please be honest and frank! And verbose.
• The invitation to complete the survey will be mailed to you shortly

Upcoming Iteration Goals

• Future iterations this semester will have fewer explicit goals
• For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Some specific iteration goals follow:
• Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
• Iteration 4: implement continuous integration testing (more on this in a future lecture)
• Iteration 5: get a preliminary system that implements the minimum requirements working
• Iteration 6: get a final system that implements the minimum requirements working
  • Keep in mind that this is the goal you are working toward this entire semester!

Wednesday, October 15th, 2014

• We are in the second week of iteration 2
• I won't have office hours today unless someobdy lets me know they will be there...
• Customer meetings: don't forget to submit the meeting report when you have met with them!
  • And don't forget to wear your name tags!
• Leads: your weekly reports were due yesterday by noon
  • Everybody got them in, albeit some were late
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• Don't forget to report your hours!!!
  • This is a course requirement -- not completing them will result in a failure for the course
• Grades for the first three homeworks have been returned
  • You can submit regrades (through the end of this week) via the course management system when they were returned (Sep 29)
• If you are fine with your git hw grade, PLEASE DELETE YOUR GIT HW REPOS
  • They are all showing up in my listings...
  • Or you can remove myself and Jamie as collaborators
  • One of these two options will be needed to get credit!
• As there was no group meeting day on Monday, we'll have one today
• ACM game night this Thursday at 8 p.m. in Rice 436!

Iteration 2

• You should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Your regular iteration meeting with the customer and Jamie should happen
• Specific goals:
  • Generate wireframes (see the wireframing lecture and consider using jetstrap)
  • Set up everybody's development environment (see the development environment setup (md) page)
    • Enable easy deployment via automatic logins or ssh keys
    • Enable easy downloading of the database
    • Ensure that everybody in the development group can develop on his/her own machine
• Requirements document
  • Your requrements document will be iterated on throughout the year
  • What format you keep it in is up to you, but I need to be able to view it
  • Having the original source (in the uva-slp/projects repo repo) in a docs directory in your repo is quite reasonable

Wednesday, October 8th, 2014

• We are on the second day of iteration 2
• Customer meetings: don't forget to submit the meeting report when you have met with them!
  • And don't forget to wear your name tags!
• Leads: your TPS reports were due tomorrow by noon
  • Everybody* got them in!
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• Don't forget to report your hours!!!
  • Not everybody got those in...
• Grades for the git HW and the cake HW have been returned; any concerns should be addressed within 2 weeks of when they were returned (Sep 29)
• Today is a lecture on wireframing; next Monday is fall break; next Wednesday is a (belated) group work day

Iteration 2

• You should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
• Your regular iteration meeting with the customer and Jamie should happen
• Specific goals:
  • Generate wireframes: that's today's lecture; this will likely take 3 or 5 story points of work
  • Enable easy deployment via automatic logins or ssh keys (we'll see how to do this next week, likely in a tutorial or such)
  • Enable easy downloading of the database
  • 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, but I need to be able to view it
  • Having the original source (in the uva-slp/projects repo repo) in a docs directory in your repo is quite reasonable

Monday, October 6th, 2014

• We are on the last day of iteration 1
• Customer meetings: don't forget to submit the meeting report when you have met with them!
  • And don't forget to wear your name tags!
• Leads: your TPS reports were due tomorrow by noon
  • The reporting system is through netbadge via https://libra.cs.virginia.edu/slp/
  • Remember that the entire group gets a penalty if the report is not submitted!
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• Don't forget to report your hours!!!
• Account information (git and pegasus), as well as framework setup (including Django) can be found in the daily announcements from Mon, 9/29
  • If you are running into deployment issues, don't wait until the last minute to get them resolved!
• My office hours are back to being 2:00-3:30 M/W
• Grades for the git HW and the cake HW have been returned; any concerns should be addressed within 2 weeks of today
• Today is a group work day; Wednesday is a lecture on wireframing
• If we still need them, then I have the meeting locations

A few clarifications

• Issues in github should be development-related, not meeting-related
• Your landing page on your project's URL should point to the various CRUD pages (and put in a reasonable title, etc.)
  • Remember that this is what you are going to demo to the customer!
• Your database schema should be called schema.sql (or schema.py, or schema.rb, etc.), and should be in the root directory of your repo, so that we can find it
• Having deployment issues? I can help, but not at the last minute...

Goals for iteration 1

• This is duplicated from the 06: project start slide set (specifically, here)
• Fully understand the requirements
  • Generate questions to ask the customer!
  • This may mean that the requirements document is updated or changed; the original source version is in the uva-slp/projects repo
• Meet with the customer
  • As the questions that you generated!
• Design a basic DB schema
  • And enter it into your pegasus group DB, or generate the forms via Rails or Django
  • So that we can find it, commit it as schema.sql or db/schema.sql
• Get a basic MVC website working (CRUD operations for the schema tables)
  • This should all be working on pegasus by the end of the iteration
• Have the system stored properly in the github repo
  • You are all members of your respective repos
  • I will give directions for initalizing the repo later this week
  • PASSWORDS ARE NOT TO BE STORED IN THE REPO
• Enter all the requirements as tasks as Github issues
  • This is described in the estimation slide set

Wednesday, October 1st, 2014

• We are one week into iteration 1; iteration goals on an upcoming slide
• Customer meetings
  • Don't forget to submit the meeting report when you have met with them!
  • And don't forget to wear your name tags!
• Leads: your first weekly reports were due yesterday by noon
  • The reporting system is through netbadge via https://libra.cs.virginia.edu/slp/
  • One group didn't get it in
  • Remember that the entire group gets a penalty if the report is not submitted!
  • Everybody can view the submitted reports through the reporting system
  • Details can be found in the course introduction slide set, specifically here
• Don't forget to report your hours!!!
• Account information (git and pegasus), as well as framework setup (including Django) can be found in Monday's daily announcements (9/29)
• My office hours are back to being 2:00-3:30 M/W
  • Although I won't be there today unless you let me know that you want to meet...
• Grades for the git HW and the cake HW have been returned; any concerns should be addressed within 2 weeks of today
• Today is a half lecture on estimation, and then a half group workday on entering issues
• If we still need this, then I have the meeting locations

Goals for iteration 1

• This is duplicated from the 06: project start slide set (specifically, here)
• Fully understand the requirements
  • Generate questions to ask the customer!
  • This may mean that the requirements document is updated or changed; the original source version is in the uva-slp/projects repo
• Meet with the customer
  • As the questions that you generated!
• Design a basic DB schema
  • And enter it into your pegasus group DB, or generate the forms via Rails or Django
  • So that we can find it, commit it as schema.sql or db/schema.sql
• Get a basic MVC website working (CRUD operations for the schema tables)
  • This should all be working on pegasus by the end of the iteration
• Have the system stored properly in the github repo
  • You are all members of your respective repos
  • I will give directions for initalizing the repo later this week
  • PASSWORDS ARE NOT TO BE STORED IN THE REPO
• Enter all the requirements as tasks as Github issues
  • This is described in the estimation slide set

Monday, September 29th, 2014

• We are one week into iteration 1
  • Iteration goals on an upcoming slide
• Customer meetings
  • Don't forget to submit the meeting report when you have met with them!
  • If you met last week, and didn't submit it, then please do so during class today
  • And don't forget to wear your name tags!
• Leads: your first weekly reports are due tomorrow by noon
  • Details can be found in the course introduction slide set, specifically here
  • We will see the reporting system today
• My office hours are back to being 2:00-3:30 M/W
• Grades for the git HW and the cake HW have been returned; any concerns should be addressed within 2 weeks of today
• Today is a group meeting day
• Wednesday is a half lecture on estimation, and then a half group workday on entering issues

Reporting System

• Two ways to access it
  • Via the "Reporting" tool in Collab
  • Through netbadge via https://libra.cs.virginia.edu/slp/ (netbadge should work, but only on https, not http)
    • (please use that URL -- even though it's a redirect, the final URL will be changing soon, but that redirect will still point to the right one)
• This is how you submit your reports for this course
• Features
  • Submit, view, and edit reports
  • Submit, view, and edit hours worked
  • View attendance, evaluations, grades, leadership iterations, and project members
• We'll see a tour of it today

Project accounts, git, etc.

• How to initalize the repo with git...
  • You should add a readme.md file (and fill it in appropriately)
• I need to know, soonish, the platform choice of that one last group...
• Properly configured URLs (here 'project' is your project tag):
  • CakePHP: put the files in project@server:~/html; the URL will be http://server/~project/ (no configuration from me needed); in all cases, http://server/project redirects to http://server/~project
  • Ruby: the files will go in ~/project (aka ~project/project), and the URL will be http://server/project; this is alrady configured on the web server
  • Django: it's all working! Directions on the next slide; the URL will be http://server/project
• The server account info on PostEm has been updated with the group account info

Django instructions

• Create the django project:

  django-admin startproject project
  

  • And set up the DB, etc.
• Create the Django app:

  django manage.py startapp app
  

  • This implies that the static directory is: app/static/app/
• Set the Django app's URLs, as described in the "Setting the static directory" section of the Django getting started (md) page
• Change the location of the static directory in settings.py, as described on that same page in the "Setting the static directory" section
  • This may require different settings.py on the local machine and on the server
• Upload those files to the project accout, and then (as the project user), run:

  wsgi-admin -register <wsgi.py> -app app -root
  

• At this point, your project should be available at http://server/project

Goals for iteration 1

• This is duplicated from the 06: project start slide set (specifically, here)
• Fully understand the requirements
  • Generate questions to ask the customer!
  • This may mean that the requirements document is updated or changed; the original source version is in the uva-slp/projects repo
• Meet with the customer
  • As the questions that you generated!
• Design a basic DB schema
  • And enter it into your pegasus group DB, or generate the forms via Rails or Django
  • So that we can find it, commit it as schema.sql or db/schema.sql
• Get a basic MVC website working (CRUD operations for the schema tables)
  • This should all be working on pegasus by the end of the iteration
• Have the system stored properly in the github repo
  • You are all members of your respective repos
  • I will give directions for initalizing the repo later this week
  • PASSWORDS ARE NOT TO BE STORED IN THE REPO
• Enter all the requirements as tasks as Github issues
  • We'll talk about this in an upcoming class

Meting locations

• Do we still need this? If so, then it's in a local file

Wednesday, September 24th, 2014

• Projects have started!
  • Contacting the customer: I emailed them (very early) this morning, so you can contact them about arranging an initial meeting
• We will see the system for entering time and reports likely next Monday (there will probably not be enough time today)
  • The first report is not due until next Tuesday
  • This means you will have to keep track of your time separately until then
  • This system will also hold your homework grades, iteration evaluations, etc.
• github stuff
  • Issues and wiki have been enabled in all the repos
  • We will go over entering issues next Wednesday
  • I do not "watch" the repos, so to get my attention, you need to tag me ("@aaronbloomfield")
  • This is NOT how you ask me to do something!
• My office hours are back to being 2:00-3:30 M/W
• Today we will start (and finish) 07: Customer meetings

Project accounts, git, etc.

• How to initalize the repo with git...
  • You should add a readme.md file (and fill it in appropriately)
• I need to know, soonish, the platform choices of two of the groups
  • By next Monday, at the latest
• Properly configured URLs (here 'project' is your project tag):
  • CakePHP: put the files in project@server:~/html; the URL will be http://server/~project/ (no configuration from me needed)
  • Ruby: the files will go in ~/project (aka ~project/project), and the URL will be http://server/project; this is alrady configured on the web server
  • Django: that's what I get to do this weekend; the URLs will either be http://project.server or http://server/project
    • The former will not work with the server's SSL certificate; the latter one will, but is a beast to configure
• The server account info on PostEm has been updated with the group account info

Goals for iteration 1

• This is copied from the 06: project start slide set (specifically, here)
• Fully understand the requirements
  • Generate questions to ask the customer!
  • This may mean that the requirements document is updated or changed; the original source version is in the uva-slp/projects repo
• Meet with the customer
  • As the questions that you generated!
• Design a basic DB schema
  • And enter it into your pegasus group DB, or generate the forms via Rails or Django
• Get a basic MVC website working (CRUD operations for the schema tables)
  • This should all be working on pegasus by the end of the iteration
• Have the system stored properly in the github repo
  • You are all members of your respective repos
  • I will give directions for initalizing the repo later this week
  • PASSWORDS ARE NOT TO BE STORED IN THE REPO
• Enter all the requirements as tasks as Github issues
  • We'll talk about this in an upcoming class

Monday, September 22nd, 2014

• The projects start today! So lots to do...
• My office hours are generally 2:00-3:30 M/W, but are 12:00-1:30 today
• We have a VirtualBox Linux image for you to use; installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well on Windows if you have anti-virus software installed; consider installing 4.3.12 instead
• Today we will finish 06: Project start, and start on 07: Customer meetings on Wednesday

Wednesday, September 17th, 2014

• The second homework (frameworks), is out
  • The Django part is due by Fri, 9/19, by the end of the day
    • There will not be deployment to the web server
    • And it turns out that you won't need a second database...
• My office hours have changed: 2:00-3:30 M/W
• All of the project descriptions are out
  • Clone the uva-slp/projects repo; you should all have read access
  • Specifically, see the 2014/readme.md file
  • These are not for public dissemination!
• Complete the survey by the end of the day tomorrow!
  • Unless you are coming to class (or my office) on Friday to ask about it
  • You received an email link as to where to participate
• We have a VirtualBox Linux image for you to use; installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well on Windows if you have anti-virus software installed; consider installing 4.3.12 instead
• Today we will likely finish 05: Requirements, and start on 06: Customer meetings

Upcoming schedule

• Friday, September 5th: no class; the git/github HW (md) is due by 10 a.m.
• Monday, September 8th: lecture as usual
• Wednesday, September 10th: lecture as usual
  • The CakePHP part of the frameworks HW is due by the end of the day
• Friday, September 12th: no class
• Monday, September 15th: lecture as usual
  • The start of semester survey becomes available (you'll receive an email)
  • The last of the requirements documents are added to github (in uva-slp/projects)
  • The Ruby on Rails part of the frameworks HW is due by the end of the day
• Wednesday, September 17th: lecture as usual
• Thursday, September 18th: The start of semester survey is due by the end of the day
• Friday, September 19th:
  • The Django part of the frameworks HW is due by the end of the day
  • There will be class, but only for all those who did not fill out the survey, or have project / survey questions
• Sunday, September 21st: When the project assignments will be determined
• Monday, September 22nd: Likely when the project assignments will be announced; first group meetings

Monday, September 15th, 2014

• The second homework (frameworks), is out
  • The CakePHP part was due last week
  • The Ruby on Rails part is due today, by the end of the day
  • The Django part is due by Fri, 9/19, by the end of the day
    • I will be giving everybody a second database ("mst3k2") for the Django part
  • All parts of the assignment are ready!
• My office hours have changed: 2:00-3:30 M/W
• All of the project descriptions are out
  • Clone the uva-slp/projects repo; you should all have read access
  • These are not for public dissemination!
  • More on the projects (and the survey) shortly...
• We have a VirtualBox Linux image for you to use; installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well on Windows if you have anti-virus software installed; consider installing 4.3.12 instead
• Today we will work through 05: Requirements

Homework 2 (and 3 and 4)

• It's in the repo, on the docs page (md), along with a lot of relevant documentation
• Basically, it's to build a basic MVC site in each of three frameworks: CakePHP, Ruby, and Django
  • There are specific tutorials to follow; you can't just create anything
  • The URLs for your sites must be EXACTLY correct
• A few notes:
  • We are using the 3.0 CakePHP API, although it is still in beta right now
  • The CakePHP: getting started (md) page lists three more commands you need to run to get your VirtualBox image ready
• All parts are ready!
• You can veiw your page at http://server/~mst3k
  • Your login credentials are in the PostEm tool in Collab
  • ssh RSA key fingerprint is 51:c6:7e:a6:44:b3:8e:f9:85:57:e0:7f:fb:c7:20:d3
  • ssh ECDSA key fingerprint is ed:1c:0e:61:94:2c:3f:53:d1:f1:dd:90:9b:f7:cb:a7
• Make sure the URLs match! You can find them listed at the end of the homework page

Upcoming schedule

• Friday, September 5th: no class; the git/github HW (md) is due by 10 a.m.
• Monday, September 8th: lecture as usual
• Wednesday, September 10th: lecture as usual
  • The CakePHP part of the frameworks HW is due by the end of the day
• Friday, September 12th: no class
• Monday, September 15th: lecture as usual
  • The start of semester survey becomes available (you'll receive an email)
  • The last of the requirements documents are added to github (in uva-slp/projects)
  • The Ruby on Rails part of the frameworks HW is due by the end of the day
• Wednesday, September 17th: lecture as usual
• Thursday, September 18th: The start of semester survey is due by the end of the day
• Friday, September 19th:
  • The Django part of the frameworks HW is due by the end of the day
  • There will be class, but only for all those who did not fill out the survey, or have project / survey questions
• Sunday, September 21st: When the project assignments will be determined
• Monday, September 22nd: Likely when the project assignments will be announced; first group meetings

Project Descriptions

See the https://github.com/uva-slp/projects repository (you all have access).

Specifically, see the 2014/readme.md file. Let's chat about the projects...

The survey

• You will shortly receive an email to participate
• You really do have to read through each of the requirements documents
  • You don't have to memorize every detail; you can skim some of the finer details here
  • But for your top choice projects, you really do need to read through the entire thing
• A listing of the survey questions is in the uva-slp/projects repository
  • In 2014/survey
  • There are four parts, which we'll go over today

Wednesday, September 10th, 2014

• The second homework (frameworks), is out
  • The CakePHP part is due by today, by the end of the day
  • The Ruby on Rails part is due by Mon, 9/15, by the end of the day
  • The Django part is due by Fri, 9/19, by the end of the day
  • All parts of the assignment are ready!
• Apparently there is an issue with CakePHP table prefixes...
• Late policy: there is none. Late homeworks receive zero credit.
• My office hours have changed: 2:00-3:30 M/W, although they will be 12:00-1:30 M/W this week
• Some of the project descriptions are out
  • Clone the uva-slp/projects repo; you should all have read access
  • These are not for public dissemination!
  • There are 13 known projects, and 2 more that are being generated (although only 10 of the requirements documents are in the repo)
• We have a VirtualBox Linux image for you to use; installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well on Windows if you have anti-virus software installed; consider installing 4.3.12 instead
• Today we will finish 04: Frameworks

Homework 2 (and 3 and 4)

• It's in the repo, on the docs page (md), along with a lot of relevant documentation
• Basically, it's to build a basic MVC site in each of three frameworks: CakePHP, Ruby, and Django
  • There are specific tutorials to follow; you can't just create anything
  • The URLs for your sites must be EXACTLY correct
• A few notes:
  • We are using the 3.0 CakePHP API, although it is still in beta right now
  • The CakePHP: getting started (md) page lists three more commands you need to run to get your VirtualBox image ready
• All parts are ready!
• You can veiw your page at http://server/~mst3k
  • Your login credentials are in the PostEm tool in Collab
  • ssh RSA key fingerprint is 51:c6:7e:a6:44:b3:8e:f9:85:57:e0:7f:fb:c7:20:d3
  • ssh ECDSA key fingerprint is ed:1c:0e:61:94:2c:3f:53:d1:f1:dd:90:9b:f7:cb:a7
• Make sure the URLs match! You can find them listed at the end of the homework page

Upcoming schedule

• Friday, September 5th: no class; the git/github HW (md) is due by 10 a.m.
• Monday, September 8th: lecture as usual
• Wednesday, September 10th: lecture as usual
  • The CakePHP part of the frameworks HW is due by the end of the day
• Friday, September 12th: no class
• Monday, September 15th: lecture as usual
  • The start of semester survey becomes available (you'll receive an email)
  • The last of the requirements documents are added to github (in uva-slp/projects)
  • The Ruby on Rails part of the frameworks HW is due by the end of the day
• Wednesday, September 17th: lecture as usual
• Thursday, September 18th: The start of semester survey is due by the end of the day
• Friday, September 19th:
  • The Django part of the frameworks HW is due by the end of the day
  • There will be class, but only for all those who did not fill out the survey, or have project / survey questions
• Sunday, September 21st: When the project assignments will be determined
• Monday, September 22nd: Likely when the project assignments will be announced; first group meetings

Monday, September 8th, 2014

• The second homework (frameworks), is out
  • The CakePHP part is due by Wed, 9/10, by the end of the day
  • The Ruby on Rails part is due by Mon, 9/15, by the end of the day
  • The Django part is due by Fri, 9/19, by the end of the day
  • All parts of the assignment are ready!
• Late policy: there is none. Late homeworks receive zero credit.
• My office hours have changed: 2:00-3:30 M/W, although they will be 12:00-1:30 M/W this week
• Some of the project descriptions are out
  • Clone the uva-slp/projects repo; you should all have read access
  • These are not for public dissemination!
  • There are 13 known projects, and 2 more that are being generated (although only 10 of the requirements documents are in the repo)
• We have a VirtualBox Linux image for you to use; installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well on Windows if you have anti-virus software installed; consider installing 4.3.12 instead
• Today we will finish 03: Legal issues, and start on 04: Frameworks

Homework 2 (and 3 and 4)

• It's in the repo, on the docs page (md), along with a lot of relevant documentation
• Basically, it's to build a basic MVC site in each of three frameworks: CakePHP, Ruby, and Django
  • There are specific tutorials to follow; you can't just create anything
  • The URLs for your sites must be EXACTLY correct
• A few notes:
  • We are using the 3.0 CakePHP API, although it is still in beta right now
  • The CakePHP: getting started (md) page lists three more commands you need to run to get your VirtualBox image ready
• All parts are ready!
• You can veiw your page at http://server/~mst3k
  • Your login credentials are in the PostEm tool in Collab
  • ssh RSA key fingerprint is 51:c6:7e:a6:44:b3:8e:f9:85:57:e0:7f:fb:c7:20:d3
  • ssh ECDSA key fingerprint is ed:1c:0e:61:94:2c:3f:53:d1:f1:dd:90:9b:f7:cb:a7
• Make sure the URLs match! You can find them listed at the end of the homework page

Upcoming schedule

• Friday, September 5th: no class; the git/github HW (md) is due by 10 a.m.
• Monday, September 8th: lecture as usual
• Wednesday, September 10th: lecture as usual; the CakePHP part of the frameworks HW is due by the end of the day
• Friday, September 12th: unsure if there will be class or not
• Monday, September 15th: lecture as usual
  • The start of semester survey becomes available (you'll receive an email)
  • The last of the requirements documents are added to github (in uva-slp/projects)
  • The Ruby on Rails part of the frameworks HW is due by the end of the day
• Wednesday, September 17th: lecture as usual
• Thursday, September 18th: The start of semester survey is due by the end of the day
• Friday, September 19th:
  • The Django part of the frameworks HW is due by the end of the day
  • There will be class, but only for all those who did not fill out the survey, or have project / survey questions
• Sunday, September 21st: When the project assignments will be determined
• Monday, September 22nd: Likely when the project assignments will be announced; first group meetings

GPL in the news

• DMCA Claim Over Non-Compliance Shuts Off Minecraft Plug-Ins
• Basically, a developer wrote 23k lines of GPL'ed code which allows Minecraft plug-ins...
  • And this code is not allowed to be used in commercial applications unless they release the code...
  • And since they are not releasing the code, this has to be resolved before development continues...
  • And it may shut down Minecraft plugins until the framework can be re-written

Wednesday, September 3rd, 2014

• The first homework, on git and github, is out; it's due Friday by 10 a.m.
  • There is also a brief intro to git as well, and everybody should at least skim through it...
  • You have to allow aaronbloomfield and floydbe to be Collaborators on the private repo you create for this assignment
• My office hours have changed: 2:00-3:30 M/W
• There is "one" more homework, in 3 parts; the first part is ready -- see the next slide for details
• Some of the project descriptions are out
  • Clone the uva-slp/projects repo; you should all have read access
  • These are not for public dissemination!
  • There are 12 known projects (of 15-16 or so total), 9 of which have fully written requirements documents
• We have a VirtualBox Linux image set up for you to use for this course, with all the software installed
  • The image is on Collab (direct link); installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well if you have anti-virus software installed; consider installing 4.3.12 instead
• ACM ice cream social this Friday (9/5) @ 1 p.m. in Rice 4th floor lobby
• Today we will work through 03: Legal issues
  • There will not be class this Friday, Sep 5th (w00t!)

Homework 2 (and 3 and 4)

• It's in the repo, on the docs page (md), along with a lot of relevant documentation
• Basically, it's to build a basic MVC site in each of three frameworks: CakePHP, Ruby, and Django
  • There are specific tutorials to follow; you can't just create anything
  • The URLs for your sites must be EXACTLY correct
• A few notes:
  • We are using the 3.0 CakePHP API, although it is still in beta right now
  • The CakePHP: getting started (md) page lists three more commands you need to run to get your VirtualBox image ready
• ONLY THE CAKEPHP PART IS READY
  • I am still working on the Ruby and Django parts, so don't start them yet
• You can veiw your page at http://server/~mst3k
  • Your login credentials are in the PostEm tool in Collab
  • ssh RSA key fingerprint is 51:c6:7e:a6:44:b3:8e:f9:85:57:e0:7f:fb:c7:20:d3
  • ssh ECDSA key fingerprint is ed:1c:0e:61:94:2c:3f:53:d1:f1:dd:90:9b:f7:cb:a7

Upcoming schedule

• Friday, September 5th: no class; the git/github HW (md) is due by 10 a.m.
• Monday, September 8th: lecture as usual
• Wednesday, September 10th: lecture as usual; the CakePHP part of the frameworks HW is due by the end of the day
• Friday, September 12th: unsure if there will be class or not
• Monday, September 15th: lecture as usual
  • The start of semester survey becomes available (you'll receive an email)
  • The last of the requirements documents are added to github (in uva-slp/projects)
  • The Ruby or Django (which one still to be determined) part of the frameworks HW is due by the end of the day
• Wednesday, September 17th: lecture as usual
• Thursday, September 18th: The start of semester survey is due by the end of the day
• Friday, September 19th:
  • The Ruby or Django (the one that wasn't due on Wednesday) part of the frameworks HW is due by the end of the day
  • There will be class, but only for all those who did not fill out the survey, or have project / survey questions
• Sunday, September 21st: When the project assignments will be determined
• Monday, September 22nd: Likely when the project assignments will be announced; first group meetings

Monday, September 1st, 2014

• The first homework, on git and github, is out; it's due Friday by 10 a.m.
  • There is also a brief intro to git as well, and everybody should at least skim through it...
  • You have to allow aaronbloomfield and floydbe to be Collaborators on the private repo you create for this assignment
• My office hours have changed: 2:00-3:30 M/W
• There is "one" more homework, in 3 parts; it should be out late this week
  • Basically, build a basic MVC site in each of three frameworks
• We have a VirtualBox Linux image set up for you to use for this course, with all the software installed
  • The image is on Collab (direct link); installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well if you have anti-virus software installed; consider installing 4.3.12 instead
• Unlike CS 2150, I don't care what system you develop on
  • But most (if not all) of the software will be on a LAMP system, so you'll have to use something similar to LAMP. I've seen people set up Mac OS X to run MAMP, and Window to run WAMP...
• How many of all y'all know C#?
• Please fill out the github userid survey by the end of the day tomorrow (Tuesday).
• Today we will finish up 02: Development methods and start on 03: Legal issues

Friday, August 29th, 2014

• The first homework, on git and github, is out; it's due next Friday by 10 a.m.
  • There is also a brief intro to git as well, and everybody should at least skim through it...
  • You have to allow aaronbloomfield and floydbe to be Collaborators on any private repos you create for this assignment
• There will be two more homeworks each successive week, then we start the projects
• We have a VirtualBox Linux image set up for you to use for this course, with all the software installed
  • The image is on Collab (direct link); installation instructions can be found here; details about the image can be found here
  • Be aware that VirtualBox 4.3.14 (the current version) does not work well if you have anti-virus software installed; consider installing 4.3.12 instead
• Unlike CS 2150, I don't care what system you develop on
  • But most (if not all) of the software will be on a LAMP system, so you'll have to use something similar to LAMP. I've seen people set up Mac OS X to run MAMP, and Window to run WAMP...
• Please fill out the github userid survey by early next week! Say, by the end of Tuesday.
  • I will need that information to get your assignments graded, and to release the proejct information to you