POSSE California CS 2010 Friday

From Teaching Open Source

Jump to: navigation, search

Day 5 session for POSSE. Theme for the day: and (Development continued...)

Contents

[edit] Status Check

  • Brief quiz/review of previous day.
  • Discussion of Overnight Deliverables -- status, problem encountered, concepts learned.
  • Physical wiki update.
  • Open source news -- current developments.
  • Follow-up
    • Fedora package review (Fedora bug 510788)
    • Next steps:
      • CVS
      • Koji
      • Bodhi
      • Push to repositories
    • Reflection on review discussion

[edit] Debugging and testing

Morning A Session

  • Overview and Demos of various debugging tools and techniques
    • Locating Regression Windows, using "blame"
    • Advanced code searching tools
      • DXR
    • printf
    • Debuggers
      • gdb
      • Visual Studio
      • Firebug, DOM Inspector
    • Stack Traces

[edit] Open Source Collaborative Development

Morning B Session

Lab: Working as a Team to Solve a Problem, Leveraging Open Source

According to Google, you can and should leave many HTML tags unclosed. Using the techniques we've learned this week, and the entire group of participants, do the following:

  • Instrument the Mozilla HTML parser to print a message to the console when the browser starts to parse a new document.
  • Instrument the Mozilla HTML parser to print messages differentiating how <li> tags are closed. For example:
    • <li>...</li> (i.e., closed by explicit close tag)
    • <li>...<li> or some other tag (i.e., closed by implicit close tag)
  • Create a series of test cases, i.e., HTML documents, which test the modified parser's behaviour with <li>.
  • Create a larger real-world test set of 1,000 HTML documents which contain the <li> tag.
  • Create a test harness to process pages through the modified browser and collect data and process it to yield implicit and explicit counts by document.

Discussion

  • Was the team successful in its tasks?
  • Which tasks were completed, which ones were not?
  • For those that were not, what prevented them from being completed?
  • How would you evaluate students who did this work?

[edit] Student Project Case Studies

Afternoon Session

We'll examine a number of Open Source student projects and identify:

  • How to find projects
    • Community-built Potential Projects lists
    • student-project flags
  • Assessment and grading
  • Risk management
  • What is success and failure?

Group discussion about potential student projects of interest to the participants.

[edit] Dinner

  • Get to know some local Open Source community members at [TBD].