MarkUs Blog

MarkUs Developers Blog About Their Project

Punchline Status Reports – Oct 8, 2009

with 2 comments

These are the status punch lines of this week

Severin

Status

  • Added some blog posts
  • Currently looking into automated testing (research, reading papers)
  • Maintenance on MarkUs 0.5 (prepared patches/did reviews)
  • Try to get a review up by Friday (#420)
  • Investigated ticket #412 (seems to be a non-MarkUs issue)

Roadblocks

  • none

Next Steps

  • Automated testing (write a first blog post)
  • Make progress on my other tickets

Mike

Status:

  • Reviewed little chunks of code
  • Helped prepare patch 0.5.3 for release
  • Quite busy with work in other courses
  • Enjoyed the posts on the blog!  Well done everyone!

Next Steps:

  • Investigate performance and stability issues that Diane Horton is having
  • Optimize Submissions table

Roadblocks:

  • It’s hard to diagnose Diane Horton’s problems with MarkUs when I have no access to the machine, the logs, etc…

Farah

Status:

  • Finished working on Ticket #373: The number of students without a group and the “Students without a group list” were not being updated appropriately after removing a member from a group
  • Took a closer look at the way assignments are currently handled in MarkUs (eg. creation, the different views, attaching graders, etc.)
  • Worked on a design proposal for simple grade entry

Next Steps:

  • Get some more feedback about my design proposal at the meeting and then modify my proposal accordingly
  • Create tickets for myself once the design is finalized and start working on the implementation

Roadblocks:

  • None this week

Gabriel

Status:

  • The Laval’s trio met twice to draft on the “New marking scheme”
  • Wrote a blog post on the “New marking scheme” ‘s name
  • Cleared ticket #417 (making submission_rule_test pass)
  • Caught a typo in “views/groups/manage.rb” (which was also corrected in “branch 0.5″ by Mike)
  • Looked at code reviews (though I didn’t participate myself this week)

Next Steps:

  • Produce the “development proposition” for the “New marking scheme”
  • Ticket #400 (results functional test is empty) is still on my list
  • Intends to produce a blog post on acceptance testing

Roadblocks:

  • None

Fernando

Status:

  • Almost done with logging
  • Have been busy with other courses assignments

Next Steps:

  • Intend to upload the logginng class tomorrow or Saturday for a code review

Roadblocks:

  • None

Mélanie

Status:

  • Met Gabriel and Simon about “New marking scheme”
  • Started  the analysis document
  • Wrote a blog post about Functional testing with Selenium
  • Switched my development environment from JEdit to Eclipse

Next Steps:

  • Produce the “development proposition” for the “New marking scheme”
  • Ticket #309(Write test for annotationControler) is still on my list

Roadblocks:

  • None

Tara

Status:

  • Commenting on blogs and learning about the code from code reviews
  • Moved 3 of my tickets to Iteration 2.

Next Steps:

  • Will spend a big chunk this weekend working on MarkUs
  • Ticket #403 (template re-arranging in the file structure)
  • Tickets #408 and #357 (When adding a member to a group or renaming a group as an instructor, enter doesn’t do anything)
  • Analysis phase for the Messaging system

Roadblocks:

  • Between Grace Hopper and catch up work this week, had no time to work on MarkUs
  • Other than that, none

Simon

Status:

  • Met Gabriel and Mélanie about “New marking scheme”
  • Started the analysis document
  • Wrote a blog post about Unit testing with Mocha

Next Steps:

  • Produce the “development proposition” for the “New marking scheme”
  • Ticket #401

Roadblocks:

  • None

Written by fgarces

October 9th, 2009 at 2:22 am

Posted in Uncategorized

2 Responses to 'Punchline Status Reports – Oct 8, 2009'

Subscribe to comments with RSS or TrackBack to 'Punchline Status Reports – Oct 8, 2009'.

  1. [...] of the team will post a punchline status report to this blog before they go to sleep on Monday. This post (from the MarkUs team) shows you what we’re after: Status, Next Steps, and Roadblocks, with [...]

  2. [...] of the team will post a punchline status report to this blog before they go to sleep on Monday. This post (from the MarkUs team) shows you what we’re after: Status, Next Steps, and Roadblocks, with [...]

Leave a Reply