MarkUs Blog

MarkUs Developers Blog About Their Project

Punchlines – UCOSP Winter 2013 – Week 8

without comments

Daniel

Status:

Roadblocks:

  • Hoping to get the above pull request merged. 🙂

Next week:

  • Work on a submissions resource and refactoring the existing submission downloads controller. Start thinking about what I’ll do for the API Documentation.

Oussama

Status:

  • Resolved issue 1035: changed grades spreadsheet by adding a hide/show hyperlink under “Total”, clicking on this link invokes a JavaScript function that toggles the visibility of all totals.
  • Need to confirm the above functionality with Karen before submitting a pull request.
  • Working on going graders more options in terms of which students records they’re allowed to view in grades sheet.

Roadblocks:

  • None.

Next week:

  • Continue working on grades sheet.

Alysha

Status:

Roadblocks:

  • Would be nice to have pull request-1052 reviewed and merged so i can use the helper methods I implemented to tackle an overall update of the code base with these methods (ie: issue 1027)

Next week:

  • Review pull request as needed
  • Work on issue 1027 once pull request is reviewed and merged
  • Work on other issues logged that aren’t dependent on pull request

Nick

Status:

  • Wrote a short blog about how the test framework can be used in several different real-world situations.
  • Played around with resque and resque-status. Resque-status is this new gem I found! It is a plugin for Resque. It lets you view the progress of one, single test run. So it will tell you things like “This test run is 40% complete” but it will not tell you that “This test run is queued and in position #46”.

Roadblocks:

  • I sent an email around asking about how the test_results table should be re-designed. I haven’t heard back yet, because I sent the email pretty late.
  • Although Resque-status lets us view the progress of one test run, I’m not sure if I am allowed to use it. It’s a new gem that we’ll have to add. Also I’m not sure how to install the resque-status files into MarkUs’s lib/ folder.
  • I still need to find a way to get the position of a test run in the resque queue.

Next week:

  • If I get feedback on the test_results table, then I can work on that.
  • Alternatively, I can keep working on Resque queues. I still need to find a way to get the position of a test run in the resque queue.

Marc

Status:

  • Working on advanced features of table views such as batch operations and pop up boxes for actions within tables (Specifically, working on the students table).

Roadblocks:

  • None so far.

Next week:

  • Going to meet up with Daryn for another code sprint working out any problems encountered thus far. We will also attempt to combine some of the seperate elements we have been working on with eachother. Overall, I will keep working on refactoring.

Daryn

Status:

  • Completed the admin function to “view as” a student. (icon on the top right, left of logout)
  • That sums up the Main views
  • Moved into the Assignments views

Roadblocks:

  • Figuring out the purpose of the update_collected_submissions function as it is used by a periodical prototype function

Next week:

  • Meeting Marc again next week for another day of hacking and consolidate our work.
  • Continue migrations.

Mike Wu

Status:

  • Fixed the bug where the UI states stored in the cookie were not properly restored (#1036).
  • Proposed a design for pre-populating the rubric with original result for remarking (#1028).
  • Started looking into the annotation component for #1029.

Roadblocks:

  • None.

Next week:

Ian

Status:

  • Fixed issues 102210231024, and 1025 (which is the same and issue 1015). All fixes have been merged.

Roadblocks:

  • Not sure what to do next.

Next week:

  • Possibly make a full test script. Work with resque to determine where tests are in the queue (if Nick hasn’t already started this).

Mike

Status:

  • Completing the grader tab for grade entry.

Roadblocks:

  • Working to figure out what database schema changes will be necessary.

Next week:

  • Have a working UI of the grader tab, and hopefully much of the back-end functionality in place.

Written by Daryn Lam

March 13th, 2013 at 1:30 am

Posted in Status Reports

Leave a Reply