MarkUs Blog

MarkUs Developers Blog About Their Project

Status Reports, Oct. 22

with one comment

Mike Conley

Status

  • Reviewed a tiny bit of code here and there

Next Steps

  • Dole out some new tickets to willing volunteers

Roadblocks

  • School

Mélanie Gaudet

Status

  • Worked on ticket #309 (Write test for annotationControler)
  • Wrote a document highlighting details for scenario 1 and created a document detailing scenario 4 and 5 for the flexible marking scheme

Next Steps

  • Continue with ticket #309
  • Plan to work on Greg Wilson’s writing requirement
  • Plan to work on the new marking scheme

Roadblocks

  • We really need to identify the best DB scenario in order to start development for the new marking scheme

Fernando Garces

Status

  • V2 of logging will be in review board by Thursday night
  • Commented on Severin’s post about automated testing
  • Started working on bug #377

Next Steps

  • Finalize the logging feature
  • Close ticket #377 by next week
  • Meet with Tara to start working on the messaging systems

Roadblocks

  • Having 3 midterms, a presentation and an assignment in 3 days is not good for my mental health ^_^

Severin Gehwolf

Status

  • Prepared patches for MarkUs 0.5; helped Alan with the patches
  • Wrote blog posts and comments
  • Merged code from the release_0.5 branch into trunk, but hit a roadblock (testing didn’t work as expected)

Next Steps

  • Rethink changes to repository library (it’s not as cleanly a distinct library from MarkUs anymore; I think this makes testing a little hard, merge problem)
  • Automated testing document

Roadblocks

  • Adaptation of tests to reflect changes in repository library (Simon and Gabriel helped, but it’s not resolved yet). Thanks Simon and Gabriel

Tara Clark

Status

  • Fixed Ticket #435 (https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/435) – defect found in Assignments Controller
  • Completed Ticket #434 (https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/434) (analysis for messaging system) Blog post on this: http://blog.markusproject.org/?p=607
  • Commented on Greg’s blog post here: http://ucosp.wordpress.com/2009/10/21/a-lesson-from-coders-at-work/ as per his request
  • Commented on Flexible marking scheme
  • Ticket #427 (https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/427): The area for clicking on a rubric level is too small (code complete, will submit soon)

Next Steps

  • Submit Ticket #428 (https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/428): Marking state icons are too similar
  • Finish up Ticket #358 (https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/358): When adding members to a group as an Instructor, we cannot add several students at a time
  • Proposing a more technical proposal for the notes system and breaking it up into sub-tickets
  • Picking up some more tickets

Roadblocks

  • Waiting on comments on the notes system prior to being able to examine it technically

Simon Lavigne-Giroux

Status

  • Finished ticket #326
  • I’ve read the blog
  • I created tickets for each task in the new marking scheme
  • I finished my exams, I can now work on MarkUs

Next Steps

  • Work on the new marking scheme
  • Work on ticket #439

Roadblocks

  • I can’t work on the new marking scheme before a final decision is made about the database model.

Farah Juma

Status

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

Next Steps

  • Work on Ticket #429 (https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/429): Create grade entry creation form

Roadblocks

  • My other courses took up a lot of time this week
  • Will spend more time on MarkUs this weekend and next week

Gabriel Roy-Lortie

Status

  • Completed ticket number #416 – Making student_test.rb pass [https://stanley.cdf.toronto.edu/drproject/csc49x/olm_rails/ticket/416]. The code is still on review board.
  • Tried to help Severin with his merging by providing with a new version of admin_test.rb (which, unfortunately still doesn’t completely do the trick)
  • That’s it. (big exam week, as anyone else)

Next steps

  • I guess we will have enough feedback to start working (I mean implementing) the flexible marking scheme.
  • I’m still looking forward to writing a “fixture replacement” proposal blog post.

Roadblocks

  • Getting the GO on the flexible marking scheme.

Karen Reid

Status

  • Worked with Severin, Mike and Alan to get patches installed on the production version
  • Spent some time checking to see if the patches solve the problems.
  • Wrote a script to deduce grace day usage from the repositories to get around both the problem of having TAs add results files to the repos after the fact, and because there is a bug in the download of the CSV
  • Diane is planning to use MarkUs for A2.  Fingers are crossed that we don’t encounter another show-stopper.

Next steps

  • Write a proposal for a CRIF (Curriculum Renewal Initiatives Fund) grant to work on MarkUs, especially the automated testing component.
  • Start preparing a poster for the Research in Action day on Nov 17.
  • Write a blog post about the problem of adding results files to the repositories.

Roadblocks

  • Meetings, interruptions, and overcommitment.

Written by Severin

October 22nd, 2009 at 10:16 pm

Posted in Uncategorized

One Response to 'Status Reports, Oct. 22'

Subscribe to comments with RSS or TrackBack to 'Status Reports, Oct. 22'.

  1. […] Posted by jerboaa on 2009/10/23 The weekly status report of the MarkUs team can be found here: http://blog.markusproject.org/?p=615 […]

Leave a Reply