MarkUs Blog

Mike Wu

Status:

• Submitted pull request #1063 to add indicator in “Annotation Summary” to distinguish remark annotations from original ones (issue 1029).

Roadblocks:

• None.

Next week:

• Coordinate with Karen on what to develop next.
• Write a blog post, topic TBD.

Daniel

Status:

• Finally finished /api/users/id/groups, updated submission_downloads, and added test coverage for submission_downloads. That pull request can be found here: https://github.com/MarkUsProject/Markus/pull/1062 It was interesting handling the test cases for submission_downloads, as I had to setup and imitate a user who had committed files to a repo for an assignment submission. And as for groups, I decided to just work with the groups class rather than groupings.
• I also pushed my current progress with RESTful API documentation to a branch on my fork, and the file can be previewed here: https://github.com/danielstjules/Wiki/blob/issue-1002/RESTfulApiDocumentation.rst

Roadblocks:

• None.

Next week:

• Finish documentation, update the Test Results routes.

Oussama

Status:

• Added an option to the grades entry form so that the totals column may or may not be rendered based on the admins choice.
• The implementation of the above feature required adding a new property to the grade entry form model, as a result, a new db migration has been created.
• Similarly, within the student view, the results are displayed as part of the grade entry forms list only if the admin checks the “show total” option, otherwise, a message will be displayed informing the student to look at their detailed marks.

Roadblocks:

• None.

Next week:

• Need to do simple CSS cleanup and add internationalization support for a few new labels.
• Finalize blog post.

Alysha

Status:

• Submitted pull request-1064 for fix to issue 1013 (late penalty description + mark not showing up once mark is submitted) as well as some other bugs I found

Roadblocks:

• Came across other bugs while working on fix (eg: penalty decay wasn’t working properly, “remove” button had a UI bug). Included these fixes with pull request.

Next week:

• Work on issue 1020 (fixing “show old mark summary” to show bonus/penalty mark section for old result)

Marc

Status:

• Finished work on term goal of converting prototype to jquery. Started looking through Github issues to see what issues I can fix for the remainder of the project.

Roadblocks:

• Cannot merge the prototype to jquery branch just yet into MarkUs master due to merge conflicts across a number of files. Daryn and I will have to meet up together to do this process together to make it go a lot smoother.

Next week:

• Work on Github issues

Daryn

Status:

• Finished implementing back drop down menu.

Roadblocks:

• Merging all changes into Markus master due to merge conflicts. Will consolidate with Marc to complete merges.

Next week:

• Either work on issues, testing pull requests for others, or find small prototype tools to be changed to jQuery.

Ian Smith

Status:

• Have the student interface for the automated testing set up. Students can run tests, and see results.
• The test_results are now associated with the test_script results so they display properly.
• A revision number of the repo that the test was used to run with is stored and displayed so the user knows which test ran with which version of their repository.

Roadblocks:

• Need more information about how “run on request” is supposed to work.

Next week:

• Finish and polish the student interface for automated testing.
• Merge and complete the work on unlimited tokens that I implemented previously.

Mike Stewart

Status:

• I’ve got graders being assigned to users through the grade entry graders tab, but still need to work out a few bugs.

Roadblocks:

• Working out a few last bugs with the grader tab, particularly with the tables not loading properly.

Next week:

• Fix bugs and submit a pull request for grader tab.

Nick

Status:

• Implemented a limit on the number of tests that can run simultaneously on a test server

Roadblocks:

• None

Next week:

• Display test run progress to TAs and students

Oussama

Status:
- Related to issue 1035:
- added internatiolization support for label of totals column
- tested changes in both English and French evironments successfully
- within he students view, changed the code that displays the list of of grade entry forms so that the total column is only displayed if the current user is either an admin or a TA

Roadblocks:
- Waiting for changes to be reviewed

Next:
- Not sure exactly as the my approach to the initial feature I planned to work on (allowing TAs to view only student they are assigned to) turned out to be incorrect.

Alysha

Status:
- Submitted pull request-1058 for fix to issue 1027 (the update of the code base to integrate possible existence of a remark result)
- Updated blog post to reflect changes

Roadblocks:

None

Next Week:
- Work on issue 1059  : carrying over bonus/penalty marks on to a remark result (may also be working on issues 1020 and 1013 which are slightly related – have to do with bonus/penalty mark UI section not updating/displaying accordingly)

Mike Wu

Status:
- Completed issue #1028 (highlighting old and new marks in the rubric and populating new remark result with old marks) and submitted a pull request (#1060).

Roadblocks:
- It took me several tries to find a way of properly duplicating marks.

Next week:
- Improve the patch #1060 if necessary. (merged)
- Review pull #1058.
- Start working on #1029.

Daniel

Status:
- Had to scrap my attempt from last week of modelling the assignments/id/submissions route. It made searching by group-name and users far too complex because of the resulting XML and JSON (lots of includes, too many nested layers). Instead, I’ve been working on using groupings for that sub collection, and calling it the route assignments/id/groups, so that users don’t need to understand the different class relations (groups/groupings, etc) I could have used groups, however, it would have resulted in an equally complex response as seen with assignments.

Roadblocks:
- I exchanged a few emails with Hanson Wu on the dev list. As of right now, I’m including a new method definition in grouping.rb that allows me to directly access group_name. However, because it’s not an attribute, the get_collection method I wrote in MainApiController doesn’t work out of the box for these nested routes with lots of includes. I’m trying to extend it to be able to achieve something like “collection.find_all { |resource| resource.send(key) == value }”, which compares a method named key to a specific value for each item in a collection. collection, in this class, is an instance of ActiveRecord::Relation, so I’ll have to see what’s available to achieve this.

Next week:
- Solve this problem, and continue work on the assignments routes to finish it up.

Daryn

Status:
- Completed updated_collected_submissions call in the assignments dashboard
- Updated all changes to be compatible with prototype
- Working on dropdown menu in assignments section

Roadblocks:
None

Next Week:
- Continue working on dropdown in assignments section.

Marc

Status:

Reintegrated Prototype back into the current changes involving jQuery so that they work side by side. Did some work on adding additional features to table views throughout the application.

Roadblocks:

Some of the features, such as searching, I am attempting to implement in the Data Table require some changes to the corresponding rails controllers. After looking at these changes, it is unclear on

Next Week:

Wrap up adding extra features to table views and attempt to merge in some changes from MarkUs master into the prototype to jquery feature branch.

Ian

Status:

Allowed students to submit automated tests. Created a simple UI that shows the marks they received on the automated tests.

Roadblocks:

None.

Next Week:

Expand the UI so that students can see all of the information about the test results.

Mike Stewart

Status:

Have the grade entry grader tab UI modified to assign graders to users.

Roadblocks:

Still trying to figure out the correct way to set up the models.

Next Week:

Complete the grader assignment.

Nick

Status:

Moved perform and the functions it depends on to a new job class.
Added configuration settings to let admin choose Redis server and queue name.
Worked on choose_test_server function.

Roadblocks:

None.

Next Week:
Keep working on displaying test run progress.

Daniel

Status:

• Made a pull request for the api/assignments resource, which can be found here: https://github.com/MarkUsProject/Markus/pull/1044

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:

• Logged additional bugs
• Fixed issues: 1016, 1018, 1031, 1021, 1030, 1051 (all related to issue 1027 - updating code to use remark result where applicable)
• Submitted pull request-1052 for fixes

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:

• Implement #1028.
• Propose a design for #1029.

Ian

Status:

• Fixed issues 1022, 1023, 1024, 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.

Status reports for Week 7 (February 27 to March 6, 2013).

Daniel

Status:

• Mostly completed the assignments part of the API. Expect a pull request in the next couple days once I have time to clean up my commits.

Roadblocks:

• Waiting for a pull request to go through. It’s already been tested and reviewed by a few others. The modifications to main_api_controller.rb are necessary for future changes to the API.

Next week:

•  Work on completing another set of routes and api controllers.

Daryn

Status:

• Worked with Marc on Friday to tackle .rjs file problems.
• Resolved the issue by replacing files with .js.erb files instead.

Roadblocks:

• Still looking for some prototype equivalent methods in jQuery.

Next week:

•  Working on admin functionality to act as different types of users (the button on the top right).

Marc

Status:

• Converted over LivePipe tables to jQueryUI tables which was a big change. This change involved rewriting Ajax calls that MarkUs was making to request data for the table. Rails controllers also had to be modified to return Json for the new jQuery Ajax calls. Further progress can be seen here:https://docs.google.com/spreadsheet/ccc?key=0AiA_01CwqYZtdFpuU3VXcFZBWHpyblRkTmN4b1Bzd0E#gid=0

Roadblocks:

• Spent a lot of time figuring out what the best plugin was to replace LivePipe tables was.
• Also, had to figure out how MarkUs was getting data with Prototype Ajax calls and apply it properly in jQuery.

Next week:

• Integrate Daryn’s changes regarding modals and make sure modals work correctly and submit the proper form data where applicable.

Alysha

Status:

• Reviewed Mike Wu’s pull request.
• Merged with my changes and updated with schema change.
• Submitted pull request 1026 for issue 941.
• Wrote a blog post about the change and future steps.
• Logged bugs I found.

Roadblocks:

• Waiting for my pull request (1026) to work on issue 1027 and related issues (updating code to use remark result where applicable).

Next week:

• Work on bugs I’ve logged either not related to remark or not blocked by merge of pull request. Revise pull request 1026 as needed.

Mike Wu

Status:

• Planned some UI features for remark with Karen (#1028 and #1029)
• Reviewed pull request #1026 by Alysha

Roadblocks:

• All remark features/bugs depend on pull #1026, so it would be nice to get it in soon.

Next week:

• Start working on #1029 (distinguishing remark annotations from original ones)
• Fix some bugs once #1026 is merged.

Oussama

Status:

• Working on implementing the following two changes in terms of how the grades entry sheet is viewed by TAs

1. displaying the relevant TA name in an added column
2. adding a menu whereby TAs can choose to view all students or only students that belong to one of their groups

• Started making changes in UI

Roadblocks:

• None

Next week:

•  Work on functionality of above feature as well as any possible DB changes

Ian

Status:

• Made it so test script max marks will be added to the total marks for an assignment, and the marks earned will be added to the marks earned for an assignment.
• Added row to summary table for the assignment results view so that user can see what they got total on the test scripts.
• Changed CSV output to added new column for test script marks.

Roadblocks:

• None

Next week:

• Finish up and make a pull request for the stuff I’ve been doing. Work on fixing Issues 1022-1025.

Nick

Status:

•  Fixed a few issues with my Test Framework’s Config/Settings page and asked for feedback on it.
• Found some bugs/issues and posted them on Github.
• Started working on the Test Results tab, which shows the test results to the graders when they are marking.

Roadblocks:

• I want to display the test results by test run, but the tables test_results and test_script_results do not provide me with the necessary information. Given a row from one of these tables, I cannot tell which test run it came from.

Next week:

• Continue working on Test Results tab.
• I want to start looking at how to display the progress of a test run to the admin/instructor.

Marc

Status:

• Completed 1 major folder in the refactoring of Prototype over to jQuery (students folder). Other progress can be seen here

Roadblocks:

• Existing AJAX call structure is confusing when trying to integrate with jQuery. I do not quite understand how the RJS files interact with the AJAX calls made in our application. Will have to talk to prior team to understand what is going on or talk to Daryn.

Next week:

• Meet up with Daryn for a hopefully efficient code sprint working out any problems encountered thus far. Keep working on refactoring.

Ian

Status:

• Made it so adding a test script will make a criterion for it with the same name as the script. I also got the marks from running the test script to be applied to the criteria.

Roadblocks:

• There’s some dependencies to fix up. (eg. if a test script is removed then it should delete the associated criterion)

Next week:

• Continue implementation of test generated marks.

Daryn

Status:

• Currently working on .rjs file compatibility with jQuery
• Pending solution: take jquery-ujs’s rails.js, which is an unobtrusive adapter for jQuery to rails and works with jQuery to use files such as .rjs type which supposedly only work with prototype.js

Roadblocks:

• Resolve .rjs type file usage
• Testing changes

Next week:

•  Will meet up with Marc to resolve issues on Friday

Nick

Status:

•  Finished working on Config UI.

Roadblocks:

• Found an issue: If you upload a test script, run a test on a student, then delete that test script, you can’t view the test results anymore.

Next week:

•  Start working on test results in grading interface.

Alysha

Status:

• Tested new fix for issue 941. Updated blueprints for schema change. From my testing, all functionality is the same as pre-schema change. Unit and functional tests do not fail on any tests that were not failing before the change.

Roadblocks:

• Waiting for Mike’s pull request to go through so I can fix conflicts before creating pull request for my issue.

Next week:

• Write blog post about database schema change. Log and start working on bugs found.

Mike Stewart

Status:

• Working on setting up the grade entry graders tab. Have got the UI started, and now working on functionality.

Roadblocks:

• None.

Next week:

• Travelling next week over March Break, but hope to get more of the Graders tab working.

Oussama

Status:

• Working on modifying grade entry forms so that only records for students assigned to a certain grader are displayed, currently, graders can see all students by default
• contemplating two design choices:
  1) add an extra column in the table that shows the group name the student is in
  2) add a drop-down menu above the table that displays the relevant groups of students assigned to the current grader, so that graders may display one group of students at a time

Roadblocks:

• None so far

Next week:

•  Continue working on above-mentioned feature
• Will have to coordinate closely with Mike-Stewart during the development of this feature since he is working on giving admins the ability of assigning graders to groups of students

Mike Wu

Status:

• Submitted pull request #1011 for issue #938.
• Decided to work on the UI side of the remark feature after discussion with Alysha.
• Began disussion with Karen regarding the UI for remark.

Roadblocks:

• Would like to have someone review pull request #1011 as Alysha is waiting on this change. Thanks in advance!

Next week:

• Start working on the UI for remark.

Daniel

Status:

• First milestone on issue 1002. Made a pull-request with all changes to api/users so far: https://github.com/MarkUsProject/Markus/pull/1014 I’ve now got a good base for the other routes.

Roadblocks:

• I’m not sure how to represent link rel=”self” elements in json, I don’t know what’s common convention. (perhaps http://caines.ca/blog/programming/json-is-under-defined-for-rest/) I’d like to have actions discoverable in a resource, as shown at http://timelessrepo.com/haters-gonna-hateoas  (see HATEOS on wikipedia) but rails doesn’t make it easy to do so by default. I’ve found the restfulie gem but it’s no longer maintained, so maybe roar using roar-rails? I need to keep looking into this.
• Hopefully get some criticism and comments on the pull request I made.

Next week:

• Continue work on assignments, keep looking into extending the response functionality.

Ian

Status:

• Got functional tests working with a few failure that are consistent with failures in the master branch. Also reviewed the current architecture for rubrics and testing.

Roadblocks:

• The design of how the tests will mark assignments needs to be discussed.

Next week:

• Start working on getting automated testing to mark assignments.

Nick

Status:

• Continue working on Config UI page. It’s taking longer than I thought it would.

Roadblocks:

• The reason is that there’s code using Prototype and I have to convert it to JQuery. I have to rewrite some of the code that was written last term.

Next week:

• Finish Config UI.

Mike Wu

Status:

• - Added remark request information on dashboard (#938), putting some finishing touches before committing.

Roadblocks:

• Not clear whether Alysha’s changes to database schema (#941) would affect my implementation of #938.

Next week:

• Submit pull request for #938.
• Plan remark features with Alysha and Karen.

Alysha

Status:

• Testing fix to issue 941.
• Discovered some problems with the database schema change, primarily from changing to methods that could be returning either the original result or remark result (since methods were based on “latest” results).
• After discussing with Karen, decided to change the approach to database schema change.

Roadblocks:

• Since the remark feature was added much later in the development, a lot of areas in the code are still using the original result even though a remark result should be used if it exists.

Next week:

• Change methods for new database schema to get_original_result and get_remark_result to provide a hopefully less complicated switch from the current implementation.
• Test.
• Write a blog post followup.
• Log issues found throughout testing.

Daniel

Status:

• Continued work on issue 1002: https://github.com/MarkUsProject/Markus/issues/1002 Now have common parameters working for collections returned using Markus’ RESTful API. Also went through some of https://gist.github.com/benjaminvialle/4055313 

Roadblocks:

• None.

Next week:

• Finish up /api/users and basic collection functionality; get filters working as well.

Daryn

Status:

• Decided to work without prototype.js so we don’t have to work with jQuery.noConflict()
• Also, by doing so easily determines which pages were dependant on prototype.js since errors would be raised.

Roadblocks:

• None.

Next week:

• Continue to cover the view files for any prototype.js dependancies.

Mike Stewart

Status:

• Continuing to work on getting a graders tab set up for grade entry.

Roadblocks:

• None

Next week:

• Get a basic graders tab implemented for grade entry, including all views components and basic functionality.

Marc

Status:

• Continuing to work on the change over from Prototype to jQuery. Got jQuery, jQuery UI, jQuery Browser Detection implemented. Completed login screen to use a jQuery UI modal.

Roadblocks:

• None so far.

Next week:

• Keep working on the changes over to jQuery. Now that I have the login page done, I will start work on the main application and will be working alongside Daryn to make sure we are following the same code conventions.

Ian

Status:

• fixed majority of test issues. Down from ~130 to ~20.

Roadblocks:

• Still some issues with the FlexibleCrtieriaController.

Next week:

• Fix up the rest of the tests.

Daryn

Status:

• Completing coverage of Dashboard/homepage migrations to jQuery

Roadblocks:

• None

Next week:

• Continue the grind of migrations. Going over Views first.

Nick

Status:

•  Started working on a new Config UI
  

Roadblocks:

•  My CSS and Javascript is a bit rusty, but no other roadblocks.
  

Next week:

•  Finish working on Config UI.
  

Alysha

Status:

• Continuing to work on issue 941. Tested application to look for any bugs caused by schema change. Worked on updating fix so that functionality mimics pre-schema change. Trying to also familiarize myself with the unit/functional tests since they need to be updated with the schema change.
  

Roadblocks:

• Realized some issues from swapping all “submission.result” references with new method “submission.get_result”. The former always returned the original result whereas the latter could return either the original or remark (since the new method returns the newest result). This changes some functionality/causes some bugs and needs to be rechecked.
  

Next week:

• Recheck affected areas to verify where differences in functionality/bugs are coming from and fix.
• Need to look into how blueprints work to update unit/functional test for new schema.
  

Mike Stewart

Status:

•  Discussed grade entry requirements with Oussama.
• Began implementing Graders tab view using reused code from assignments.

Roadblocks:

• Need to touch base with Karen to confirm requirements.
  

Next week:

• Get Graders tab view set up.
  

Oussama

Status:

• Examined existing grade entry functionality and code
• Found that large parts of the UI code can be recycled
• Still unclear about some issues regarding the nature of the work flow, since grade entry sheets exist already
• Connected with Mike

Roadblocks:

• None

Next week:

•  Need to talk with Karen about a few design decisions

Mike Wu

Status:

• Started on issue 938, but couldn’t go very far due to midterm preparations and Lunar New Year activities. (Happy New Year everyone! =])

Roadblocks:

• Pull 998 (adding assignment statistics to dashboard) is waiting for code review.

Next week:

• Continue with issue 938.
• Discuss with Alysha and Karen regarding developing remark feature.

Daniel

Status:

• Continued work on issue 1002 (https://github.com/MarkUsProject/Markus/issues/1002). Was able to test the existing API, and proposed re-organization and additional features. Completed a list of the API routes I’d like to complete this term, and included details of common parameters and other points of interest. Began re-organizing the /api/users controller.

Roadblocks:

• Hoping for input/criticism on the proposed design. Ideas for other features as well. Also, I’m trying to figure out the best way to allow filters in the URI for collections.

Next week:

• Continue work on /api/users and create/document a rough model for error handling in the API.

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.

Team is making steady progress. General conclusion was that most of us would be working on Github issues for weeks 1 and 2. Also, it was noted that it would be beneficial if team members started to review other people’s pull requests, so pull requests could be merged faster into master. The wiki pages were noted to be outdated, so if you ever see any outdated wiki pages make notes or edit them. In order to update changes, you will have to clone the wiki repo that exists within MarkUsProject and submit pul requests there.

Daryn will be working on switching over Prototype to jQuery and if time applicable, SVN to GIT.
Oussama will be working on grade entry sheets.

TLDR:

• Team working on issues for rest of week 1
• Review other team members pull requests to get changes merged in faster
• Make notes on outdated wiki pages and update them if possible

Link to IRC Log: http://www.markusproject.org/irc/markus20130123_pg1.html

Marc

Status:

• Last week we were at the sprint for the weekend. When I got back, I make 2 changes to pull requests I had submitted, and I wrote blog posts about the sprint and my introduction.

Roadblocks:

• svn-ruby bindings got into my way when trying to set up MarkUs during the sprint, and I was having a couple problems with git which are now resolved.

Next week:

• My plan for next week is to tackle a few more Github issues before I start working on my long term goal for the term.

Ian

Status:

• Got MarkUs up and running.
• Finished 2 issues relating to compatibility between MarkUs and Rails 3.0.19 and Ruby 1.9.3.
• Started looking in to how the test framework works currently.

Roadblocks:

• Setting up a test using the test framework is not very intuitive.

Next week:

• Figure out how the test framework is working currently.
• Determine what it can and can’t do.

Daryn

Status:

• Looking over issue 980 and 91 (related) and discussed plans to work with Marc on Prototype to jQuery and replacing SVN for Git

Roadblocks:

• Need to consolidate with Severin on decision about issue 980/91

Next week:

• Planning out the steps to take for transitions of jQuery

Nick

Status:

• Installed MarkUs
• Attended code sprint
• Made 2 pull requests
  • issue 577, which deals with timing out the user, and
  • issue 958, which deals with a JavaScript problem when creating assignments.

Roadblocks:

• I haven’t done much yet, so I have not encountered roadblocks so far.

Next week:

• I plan on reading through more Rails tutorials & guides and start looking at the testing framework code.

Alysha

Status:

• Set up MarkUs.
• Fixed a bug so that rubric criteria is ordered correctly when uploading and downloading yml files.
• Fixed a bug so that sorting columns that have html with text (ie: textboxes) is now sorting correctly.

Roadblocks:

• New to Ruby on Rails, still familiarizing myself with project code base

Next week:

• Look into and familiarize myself with the remark feature by looking into any related issues on GitHub.

Mike Stewart

Status:

• I’ve started reviewing Pull 928, to get a sense of the work that has been done on grade entry.

Roadblocks:

• None.

Next week:

• I plan to test the code that has been submitted (Pull 928), so I can complete the code review and get it into head.

Oussama

Status:

• Have become familiar with Rails to a certain extent.

Roadblocks:

• Still studying the MarkUs code-base.

Next week:

• Will finalize term objectives during upcoming team meeting.

Mike Wu

Status:

• Installed Linux and set up MarkUs
• Documented steps to resolve problems encountered during setup (to be submitted to wiki)
• Fixed an issue where the Assignment Submitted calculation on dashboard was incorrect.
• Uploaded group pictures taken at Facebook to Facebook and MarkUs blog.

Roadblocks:

• Encountered issues during the setup, resolved with the help from Nick and Mike.
• Continue learning the codebase and Ruby on Rails in general.

Next week:

• Post setup documentation on wiki
• Work on adding more information to dashboard, including statistics of assignment scores (#915) and remark information (#938).

Daniel

Status:

•  Setup Markus on OS X with Ruby 1.8.7 and rails 3.0.x
• Worked from Friday through Sunday, while flying back to Ottawa. It was a fight to keep my laptop charged, but I managed to fix a few extra issues because of it. The three that I completed at the codesprint related to browser compatibility dialogues and a simple tab issue. Those consisted of issue #658, #968, and #617. Aside from those, I also completed fixes for issue #982,  #953 and #415 on Sunday.

Roadblocks:

•  I’ve yet to be able to build SVN on OS X with Ruby 1.9.3. I experience issues when setting up SWIG.

Next week:

•  I intend to continue fixing other issues throughout the tracker to become more familiar with the codebase. So far this includes: issue #860 and #63.