MarkUs Blog

Robert

Status

• Shipped fix for 510 for release 0.6
• Invited down to California for Facebook interviews. [Yay!]
• Kept up with discussion on reviews.

Next Steps

• Determine if my fix for 510 also resolves issue 569 for occasional non updates of grader assignments.
• Find more time to work on MarkUs. This should arrive next Thursday, and during reading week.

Roadblocks

• Lack of time due to interviews and other classes. 4 interviews with Amazon this week.
• Unable to conduct code reviews on many changes this week.

Mike

Status

• Reviewed a bunch of code
• Wrote a handy-dandy script that lets me test drive diffs-for-review quickly and easily. See http://mikeconley.ca/blog/2010/02/02/pre-commit-code-review-in-markus-development/ towards the bottom. I’m going to polish this tool up and upload it somewhere if people are interested in using it.
• Answered some emails, commented on the blog, tried to be helpful

Next Steps

• Look into Details CSV Report issue that Karen and Byron are having
• Upon (hopefully) fixing above, prepare patch (possibly including other fixes for 0.6 that have been committed)
• Review more code.
• Answer any more questions that people have. Fire away!

Roadblocks

• These past two weeks have been super busy. I have a feeling my two courses this semester are synchronized to bring the pain simultaneously. Coming up to a rest point though.

Bryan

Status

• Wrote my first unit tests!
• Closed #393 (“Repository folder does not allow paths such as “test/path1″, 393)
• Reviewed some code

Next Steps

• Work on #418: Changing an assignment’s due date doesn’t update the SubmissionRule’s cache
• Write a blog to share my newbie experiences
• Gain more RoR knowledge

Roadblocks

• There was an essay that took me almost two days!

Victoria

Status

• Completed MarkUs Usability and Interface Design Plan.

Next Steps

• Start prototyping for the group formation tab.

Roadblocks

• None

Joseph

Status

• I completed all the requests from the review. We are not longer
  escaping the validate script for the user. I have figured out a way to
  check for a validate script that does not have the spaces escaped by
  looking at the error code from p.open and then $?
• I found a second bug that I will write a blog post about so I can
  get into details and give code examples with pretty highlights

Next Steps

• Check-in the stuff I talked about above
• Still need to look at will_paginate

Roadblocks

• Next week is an extremely busy week

Farah

Status

• Didn’t get much time to work on MarkUs this week because I had three assignments due

Next Steps

• Will spend extra time on MarkUs this weekend and next week
• Finish functional tests for the grades table and submit a review request
• Work on the student UI

Roadblocks

• My other courses took up most of my time this week

Brian

Status

• Ticket 531,571,512 done
• Start to work on UI issue now

Next Steps

• finish test cases of above ticket
• write a blog to summary up a few discoveries

Roadblocks

• Intensive reading of papers