MarkUs Blog

MarkUs Developers Blog About Their Project

Punchlines – UCOSP Winter 2013 – Week 2

without comments

Marc

Status:

  • Pushed a couple changes to some small issues and attempted to work on issue 80.
  • Also researched the change over from Prototype to jQuery as can be seen on my blog post.

Roadblocks:

  • Issue 80 will take me a significant amount of time due to its complexity, so I will most likely put it on backlog for later.

Next week:

  • I want to start working on converting over Prototype to jQuery. Since I am working with Daryn on this, We will set up a Google Doc to track which changes we are making, and who is working on what task.

Ian

Status:

  • Pulled the test-framework branch from github. I fixed some problems with the branch (syntax and no method errors) and got the configuration set up so I can run tests without crashing on my local machine.

Roadblocks:

  • I’m not sure what the test framework is actually supposed to be doing.

Next week:

  • Get the test framework to mark an assignment.

Daryn

Status:

  • Looking over Markus source code to get a scope on the magnitude of prototype dependent code.
  • Documenting findings in spreadsheet to keep track of progress on specific files.

Roadblocks:

  • Re-familiarizing myself with jQuery/getting the rust off.
  • Determining how completed code changes will be submitted.

Next week:

  • Planning to start digging into the code and testing results.
  • Will be absent over the weekend (attending MHacks event in Michigan)

Nick

Status:

  • This week I familiarized myself with the testing framework. I looked over some of the testing framework code. I think I have the main ideas in my head, and I’ll try to create a flowchart/schematic drawing sometime soon.
  • In the end, I was able to manually force a test to run through rails console, and now I can see some test results when grading in MarkUs.

Roadblocks:

  • I don’t think the documentation on the testing framework is very good. I had to figure everything out by reading the code (which wasn’t that bad).
  • When grading in MarkUs, I can see the test results in a “Test Results” tab. But how do I transfer those marks automatically to the rubric on the right?

Next week:

  • Keep staring at testing framework code.
  • Figure out: (1) what features still needs to be implemented, (2) who will be implementing them, and (3) the order the features should be implemented in (priority).

Alysha

Status:

  • Working on issue 941. Becoming more familiar with code revolving around remark feature. Have a working way of getting old result and remark result without relying on database ordering and timestamp.

Roadblocks:

  • Spent a lot of time trying different things out (trial and error) and learning ruby on rails. Initially tried to change submission schema from “has_one :result, :dependent => :destroy” to “has_many :result, :dependent => :destroy” but it affected too much of the code at once. Decided to first find a solution for the query and write the get_result and get_old_result methods, then to work on changing the schema.

Next week:

  • Finish up this issue (changing the schema). Possibly write a blog post to follow-up on this post which was about the original issue and the temporary fix that I am working on replacing.

Mike Stewart

Status:

  • Spent quite a bit of time resolving some new issues with my environment. Everything is working now.
  • Completed testing and code review of pull request #928.
  • Reviewed other issues related to grade entry, to get a sense of what all will need to be done.

Roadblocks:

  • It would be ideal if pull #928 can be merged before I proceed with making additional changes to that code.

Next week:

  • Coordinate with Oussama to see how we will divide the work to be done on grade entry, then start making progress.

Oussama

Status:

  • working on grade entry aspect of Markus
  • fetched branch ‘issue894’ from Kira’s repository
  • performed review for pull request …
  • tested functionality changes

Roadblocks:

  • trying to understand some of the code changes as I am still familiarizing myself with Ruby on Rails

Next week:

  • do some more reading on the Ruby framework
  • start working on grades sheet

Mike Wu

Status:

  • Committed some additions to MarkUs setup documentation for Linux on Wiki (pull #16).
  • Added median grade for assignments, number of fails, and number of zeros to dashboard; some refactoring to do before submitting a pull request for issue #915.
  • Set up MarkUs project in Aptana (as an Eclipse plugin, a more familiar environment for me).

Roadblocks:

  • How to get French translations in general? Is Google Translate reliable for English-to-French? Should I get them before committing or create separate issues for translations and use English temporarily in the initial commit?
    • Currently, those for “Number of zeros” and “Number of fails” are needed for issue #915.
  • Learning Ruby syntax and the structure of codebase was where most of my time was spent.
  • Setting up Eclipse and Aptana was mostly straight-forward with a few tricky bits.

Next week:

  • Commit issue #915.
  • Learn the structure surrounding the remark feature by working on issue #938.

Daniel

Status:

  • Completed fixes for issues #63 and #860.
  • Discussed and proposed a solution to issue #19.
  • Made a wiki pull request cleaning up a few things: pull 14
  • Wrote a blog post about the switch from svn to git. Wrote a script for the comparison.

Roadblocks:

  • None.

Next week:

  • Finalize a fix for issue #19 once we’ve all agreed.
  • Research other areas that might help improve Markus performance.
  • Decide exactly what I’d like to work on this term.

Written by Daniel St. Jules

January 30th, 2013 at 2:04 am

Posted in Uncategorized

Leave a Reply