MarkUs Blog

MarkUs Developers Blog About Their Project

December 4th Status Update

with 2 comments

Farah

Status

Next Steps

  • Discuss the issues related to the Table View at the meeting tomorrow
  • Commit my code since I got my last “Ship It” for my current review requests and then do some ticket clean-up

Roadblocks

  • None this week

Fernando

Status

  • Added the link so a TA can create or view notes while grading
  • Fixed bugs 506 and 505 which are in the branch release
  • Did the screen-casts of the notes modal dialog

Next Steps

  • Sleep

Roadblocks

  • As usual time

Severin

Status

  • Ticket #437 committed
  • Created some tickets, feature requests
  • Fixed reviews for which I got feedback
  • Didn’t get to post my next automated testing blog-post (Hrmph)

Next Steps

  • Write a blog post about a feasible scenario which could be implemented next summer regarding automated testing (we need to allow check in of instructor generated (test-) files to student repositories, first)
  • Talk with Mike and Karen about must-fix tickets/features for the spring courses round. Think about a schedule until our next deployment round in January.

Roadblocks

  • Time

Tara

Status

  • Finalized and committed Notes tab code for groupings
  • Closed ticket #500 – Grader view: rubrics are nested in the table

Next Steps

  • Commit ticket #507 – Groups controller tests missing fixture student7
  • Screencast
  • Wiki documentation on Notes
  • Make notes on my investigation for ticket #361 (Grader View: shoudn’t unmarked rubric be expanded by default?) since I don’t have time to finish it

Roadblocks

  • None – just finals left to write!

Gabriel

Status

  • Committed Cucumber integration (ticket 460) and created a wiki page about using it.
  • Opened a review request to show the tests I made with Machinist and MarkUs.

Next Steps

I’m afraid there are, just give me the week-end.

  • Selenium testing added functionalities.
  • Add what’s needed to have Selenium used inside Cucumber tests.
  • Updated documentation on what’s left to do for the Flexible marking scheme feature.

Roadblock

  • Design III, alias: The Robot

Simon

Status

  • Introduced MarkUs to our colleagues (and shared our experience) during our QA class
  • Did nothing else this week except work on a robot for a course but it is now FINISHED !!

Next Steps

  • Create tickets for what is left to do on the Flexible criteria feature
  • Document the Flexible criteria features state (wiki)
  • Look at acceptance tests that could be done.
  • Look at the grading view and estimate the time it could take.

Roadblocks

  • None

Melanie

Status

  • Worked on and finished Ticket #457
  • Published 2 screencasts to explain the flexible criterion implemented features.
  • Demo for our QA course that presents Cross-Canada, Markus and our implication
  • Started the document about the Flexible criteria features state

Next Steps

  • Write some Selenium tests
  • Publish the document about the Flexible criteria features state
  • Study for my final exams

Roadblocks

  • None

Mike

Status

  • Reviewed lots of code
  • Looked into ReviewBoard large-diff problem:  looks like we’ll just have to split into smaller diffs for now

Next Steps

  • Now that things have calmed down, have a meeting with Karen to figure out how to prepare MarkUs for next semester

Roadblocks

  • None

Written by m_conley

December 4th, 2009 at 10:29 am

Posted in Uncategorized

2 Responses to 'December 4th Status Update'

Subscribe to comments with RSS or TrackBack to 'December 4th Status Update'.

  1. […] by mikec86 on 2009/12/04 The MarkUs team have posted their punchlines for December 4th.  Click these words for the full […]

  2. […] Here is an example of a status report post – notice how short and punchy each status report is.  They get right to the point:  Status, Next Steps, Roadblocks.  Point form is fine.  Again, these should be collected and posted, and then read by the team before the IRC meeting.  This way, we’re all more or less on the same page when the meeting begins. […]

Leave a Reply