MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for the ‘Status Reports’ Category

Status Update: February 27, 2014

without comments

Tiago

This Week: I worked on issue #1312

Roadblocks: None

Next Week: Try to make markus work with ruby 2.0

Rafael

This Week:
- I worked on issue #1220 and on the portuguese translation of MarkUs.

Roadblocks:
- No big roadblock, although I’m still not that comfortable with RoR and MarkUs.

Next Week:
- I’ll be travelling, but I’ll try to finish what I’m doing with the translation.

Kitiya

This Week:
- Worked on issue #1358
- Reviewed code on a Group page under the Assignment tab that already implemented the search function to get more understanding on the application.
- Learned more about Rails on the overview, Ruby and UI parts.

Roadblocks:
- Still not comfortable with Rails and it took me quite a bit of time to trace the program.

Next Week:
- Continue working on issue #1358
- Learned more about Rails on the Model part

Zach

This Week:
- Started marking up current git branch for readability
- Implemented jQuery filtering which ultimately didn’t work
- Discovered the correct solution, the FilterTable object which is nearing implementation (I think)

Roadblocks:
- Erroneous understanding of the DOM.

Next Week:
- Commence git work in earnest.

Jeremy

This Week:
I continued work on #1310 and started reading a book on rails to help better understand the project.

Roadblocks:
I fixed the one big roadblock I was having, which was not knowing how to query for the data that the project uses. For reference, if you’re using postgresql you go into the markus directory in the terminal and type psql postgres -d markus_development -U markus ….and then type in your password.

Next Week:
I’m hoping to have that ticket done by the end of this week, so next week I’ll be looking for new tickets to do, as well as getting together with Andrew and Sheng to work together on our assigned task.

David and Gillian

This week:
- Did testing for grades spreadsheet for both Master and Beta branches and compared functionalities
- Compiled user stories for spreadsheet
- Logged issues found during testing the spreadsheet on the Master branch
- Fixed issue #1376 (being able to upload no file or wrong files)

Next week:
- Fixing more issues with spreadsheet
- Additional testing of Beta and Master branches

Cornell (Alex, Ope, Christopher)

Ope

This Week:
- Created a branch on my fork that will be used for maintaining the group’s changes to the help system.
- Reviewed pages under the Assignment tab, and documented pages that already have help pages that can be expanded on and pages that have no help information.
- Reviewed fix for bug (issue #1361, pull request #1371) due to minor issues and merge conflicts. Fixed this, and awaiting merge from Benjamin.

Roadblocks:
- None

Alex

This Week:
- Worked on the design of the help system and created a proposal for the help system.
- Researched forms of help systems that other websites use.

Roadblocks:
- None

Christopher

This Week:
- Create a new branch for the helper system.
- Figure out several design of helper system and find the best way to implement the helper system.
- Write a proposal of the helper system on MarkUs blog.

Roadblocks:
- Find the best way to share a branch between us for the helper system.

Next Week:
As a group at Cornell next week we will start working on the help system that we have proposed. We hope to have feedback on our proposal by next week, so we can change things and add ideas before we start implementation.

Written by Kitiya Srisukvatananan

February 28th, 2014 at 9:42 am

Posted in Status Reports

Status Update: February 23, 2014

without comments

Zach

This Week:
- implemented search in the users view through ruby
- researched gems for git backend / familiarized myself with their basic usage

Roadblocks:
- None

Upcoming Week:
- install current git branch, complete search through jQuery so page reload isn’t required
- contribute to wiki

David Dias

This Week:
- Familiarizing myself with the Markus beta branch and how it works
- Learning more about Rails + Ruby to understand why errors in the beta are happening

I haven’t done as much as I’d like this week but I think I’ll fix a couple errors by next report.

Kitiya

This Week:
- Submitted pull request for issue #764 again (the previous one did not pass the test).
- Working on issue #1358 – adding search functionality on the user tab.
- Finalize my project topic -  An view of all of an individual student’s work.

Roadblocks:
- Got some problems on git commands.

Next Week:
- Continue working on issue #1358.

Rafael

This Week:
- This week I searched the github page for some issue I could work. Tried unsuccessfully to reproduce error from issue #1222, wrote at its page on github but I still got no response. So I worked with issue #1220, and came with a solution that isn’t ideal. I’ll still try to work something out for #1220 this week…

 Roadblock:
- I believe ruby on rails and, in lower scale, the understanding of how the MarkUs environment should be or behave sometimes are the major roadblocks.

 Next Week:
- Finish working on #1220 and talk to Karen about project idea for the term

Western University (Jeremy, Shenglong, Andrew)

Jeremy Winters

This Week:
- Was on vacation so didn’t have a large amount of time on the project. Time I got was spent working on #1310 and learning how rails is working.

Roadblocks:
- I traced the code to what table in the database the problem should be coming from, but I’m not quite sure how to query the database. I tried quite a few things but need help with this.

 

Next Week:
- Should be able to finish that issue once I get some help with the database problem. Shenglong, Andrew and I plan on getting together to discuss our work on the performance enhancements of MarkUs.

 

Andrew Hernandez

This Week:
- Spoke with Jeremy and Shenglong about which project we will be working on

Roadblocks:
- I have been out of town for a large part of the week so I have not had much time

 

Next Week:
- Will have an IRC meeting with Jeremy, Shenglong, and Karen, regarding which project we will work on

 

Shenglong Gao

 

This Week:
Sorry, I was travelling and in a week-long competition (we won, yay), so I haven’t been able to get much done this week. We have talked, among the Western group, and collaborated about the nature of what we’d like to do for the project, though.

 

Cornell (Alex, Ope, Christopher)

 

Ope:

 

This Week:
- Started looking into parts of system that could benefit from the help system, and possible implementations
- Fixed a bug (issue #1361). Created a pull request for the issue.Roadblocks: NoneAlex:This Week:
- Pushed a fix for issue #1342 where the groups were not rendering correctly in the assignment tab, which was worked out between Chris, Ope and I.Roadblocks:
-Trying to figure out to create a branch for the help system so everyone can see it.Christopher:This Week:
- Find a bug (issue#1360)
- Fix the bug (issue#1360)
- Started looking the way to develop the help system with Alex and Ope.

Roadblocks:
- local git hub issues, which I was able to resolve with Alex and Ope

Next Week:
As a group at Cornell next week we will start creating the wiki page with our proposal for the Help system. We will also work on the continued issues that we have been looking at.

 

Tiago

This Week:
- I looked for some bugs to work on, and decided to work on ruby 2.0 problems.

Roadblock: None

Next Week:
- Talk to Karen about project idea for the term

 

Written by Andrew Hernandez

February 23rd, 2014 at 11:04 pm

Posted in Status Reports

UCOSP Status Report – Week of Dec 2

with one comment

Daniyal

Status

  • Worked on implementing add user method in git_repository.rb. This deals with the authentication problems we were expecting to have so I haven’t been able to complete it yet.

Roadblocks

  • Documentation for the gitolite gem is hard to find, and what I did manage to find wasn’t very helpful.

Next week

  • Figure out how to use gitolite
  • Once the add user method is done using gitolite, the remove user, get permissions and set permissions methods should be fairly easy.

—————–

Bill

Status

  • Got the initialize function in GitRevision Class behaving exactly the same as the initialize function in the SubversionRevision class does.
  • Been working on the file path issue, committing and setting objects for a given file path is a trivial. Retrieving a file or object from a given path has been confusing, Rugged documentation is not clear.
  • Started playing around with Rugged tree objects and index object to see if I can get the files for a given path, I think index objects will work.
  • Discovered a potential issue with Markus git client, what happens when Markus encounters a merge conflict whena student adds files through the web client? Force push files to repo?

Roadblocks

  • Rugged documentation is pretty useless, and there are few working examples online of implementation.
  • Retrieving files given a path is undocumented.

Next week

  • Figure out this file path business, specifically retrieving files given a file path.
  • Even though I plan on continuing to contribute to Markus, I’m going to clean up and document my code thoroughly in case future students need to work on/with it.
  • Fully implement GitRevision class.

———————-

Xiang

Status

  • Worked with Jeremy and confirmed the commit of issue-1211
  • Fixed issue-1001

Roadblocks

  • not being familiar with the test framework stuff cost me a bit of time with issue-1211

Next week

  • review the issue I resolved and make sure the solutions are complete and clear
  • Ensure the blog post about the Summaries page which is my major contribution this term conveys everything

—————————–

Arianne

Status

  • Fixed Issue-100 and sent pull request

Roadblocks

  • Lots of pieces in the grade entry forms are broken. Especially updating grades, pagination, and navigation. This made it hard to test.
  • I also spent many fruitless hours looking into these bugs briefly before deciding to just keep going and finish the issue.

Next week

  • Either work on those bugs that I found this week or do something else that is more important
  • Write a blog post about either this week’s work or the stuff on grade entry item ordering
  • Create and give a presentation on the project for my school’s UCOSP requirements

Written by Arianne Dee

December 2nd, 2013 at 8:17 am

Posted in Status Reports

Punchlines ECN – 17/11/2013

without comments

Augustin

Status

- Migration to JQuery ongoing

- 2 PRs with some files from app/views/assignments

Roadblocks

- Some unknown translations from Prototype to JQuery

- I have not tested yet my work because I had some trouble executing cmd “bundle exec rails s”

Next Week

  – Functionnal test about my work

- Finish migration

 

Anthony

Status

- Migration to JQuery ongoing

- Pull request with some files of the app/view folder

RoadBlocks

- Some unknown translations from Prototype to JQuery

Next Week

- Make a pull request with my full part of the app/view

- Start my part of the js folders

Hamid

Status

-  Finishing the migration to jQuery

Roadblocks

- Some unknown translations from Prototype to JQuery

Next Week

 -  Make my pull requests

Julien

Status

-  Working with Loic on our migration, our part is almost over and should be done this week end

Roadblocks

- The translation of ajax request

- The translation of this kind of function :

@student_ids.each do |student_id|
end

Next Week

 - finish our part, with the tests and the commits

 

Loïc

Status

-  Working with Julien on our migration, our part is almost over and should be done this week end

-  Doing the commits for our part

Roadblocks

- The translation of ajax request

- The translation of this kind of function :

@student_ids.each do |student_id|
end

Next Week

 - finish our part, with the tests and the commits

 

François

Status

- Migration to JQuery in process

RoadBlocks

- Some trouble with specific Prototype functions: page.call(), Ajax.Request & replace_html with some @-parametres

Next Week

- Continue the migration

 

Written by Loïc Labagnara

November 17th, 2013 at 5:43 am

Posted in Status Reports

Status Report – Week of Oct. 28

without comments

Dylan

What I did:
- Looked into how user access is done for the current SVN system. Summarized my (rough) notes and passed onto Bill, Daniyal.
- Set up a Vagrant box to act as my dummy server to host my git repos on, and began playing around with gitolite.
- Now have an understanding of the basic architecture of gitolite, how users are added, and roles managed.
Roadblocks:
- Distance is a bit hard. This project will require us to have quite a few meetings, I think.
- Rugged (required to talk with the git repos) requires Ruby 1.9.3….but as we know this doesn’t work with existing code. Need to discuss how it’s best to go about testing our implementations.
Next week:
- Do up a quick document to get Bill and Daniyal up to speed with my findings.
- Meet with Bill and Daniyal to discuss putting some of these parts together.
- Write some code! See where/how to integrate gitolite and the permissions scheme into MarkUs. 

 

William

Status
 - Got libgit2 and rugged working on Ubuntu.
 - Working on writing a guide for installing libgit2 and rugged for the MarkUs blog.
 - Played around with some rugged methods to better understand how things work.
Roadblocks
 - libgit2 will NOT build on OSX 10.6, I tried for far to long to get it to work. However OSX 10.7 and higher are fine.
 - Rugged does not support ruby 1.8.7
Next Week
 - Post guide on installing libgit2 and rugged onto MarkUs Blog.
 - Ideally I’d like to meet with Daniyal and Dylan again to figure out how we’d like to proceed with implementation of git inside MarkUs
 - Begin implementation of git!

 

Arianne

Last week:

Created ticket for bug found: link not working for uploading grade entry form grades through csv. – Issue-1224

Fixed Issue-1224 and submitted pull request.
Worked on fixing old tests that broke from issue-1194 updates (still have 3 unit tests and 3 functional tests to fix).
This week:
Add a few tests for new functionality. Finish off this ticket!

 

Daniyal

Status:

- Researched libgit2, rugged and gitolite. Gitolite looks like something we will need for authentication as it allows for easier and more fine-grain control of repositories. It uses a file similar to svn_authz to determine which users have what kind of access to different repositories.
- Worked on issue-54, learnt a bit of JavaScript to format calendar_date_select in new assignment tab. Added a gap between buttons and increased button font size. Submitted a fix for this issue and made a pull request.

Issues:

- Haven’t been able to start add code for git repositories because I’m having trouble figuring out where to start.

Next Week:

- Meet with Dylan and Bill to figure out how/where to start implementing git.
- Get at least some code started for git implementation, even if it is very barebones.

 

Xiang

Status:
- Reviewed all the code written for the Summaries tab and did coding cleaning.
- Posted a blog post describing the functionalities of Summaries tab and implementation details as well as issues.
Roadblock:
- Had some issue with local Markus after update
Next week:
- Fix the issue with update
- Commit a working set of code
- Write tests for the Summaries tab

Written by Xiang Yu

November 6th, 2013 at 11:29 am

Posted in Status Reports

Status Report – Week of Oct. 28

without comments

William

Status

  • Researched and started making test projects for git-svn interactions. Discovered that git-svn can only make git repos, if we are to proceed with git-svn we would need a new authentication system because of the git repos. A new approach for the repositories in MarkUs is needed.
  • Had a meeting with Daniyal and Dylan about what we have learned about how Git and SVN interact, and how we should proceed with the repositories.
  • Started working on a Git implementation for MarkUs, working on installing libgit2 (http://libgit2.github.com/).

Roadblocks

Next Week

  • Work on installing libgit2 and writing an installation guide for the Daniyal and Dylan and/or MarkUs Wiki
  • Update the bundler for rugged (https://github.com/libgit2/rugged) and libgit2
  • Make sure git bindings work for ruby versions 1.8.7, 1.9.3, and 2.0

Dylan

Status

  • I looked more into the svn/git problem.
  • Met with Daniyall and Bill on IRC to discuss what we had found.
  • Got a new computer so I spent some time getting my environments back.

Roadblocks

  • Days are too short.

Next week

  • Research the authentication scheme used currently by SVN.

Xiang

Status

  • Improved the Summaries table columns by dynamically producing columns according to the marking rubric for a particular assignment.
  • Came up with a working method to provide sorting function for each marking criterion, avoiding repetition of code as the same time.

Roadblocks

  •  Still need to dig some more into Rails and Javascript to find possibly better solutions for the problem and further improve the summaries tab.

Next week

  • Write detailed description of the problem and current solution
  • keep looking for better solutions (possibly focusing on Javascript/Jquery)

Arianne

Status

  • I’m almost finished working on issue-1194.
    • Adding positions to grade_entry_items:
    • Positions are updating reliably, nothing is ever out of order if it saved properly
    • Needed to change some functionality on model validation for this to work:
    •     columns with empty names don’t get saved
    •     columns with empty out_of marks get a default value of 1 (can change this to 0, whatever makes most sense)
    •     columns with duplicate names get saved but have ‘(rename)’ appended to their name
    •     adding two columns at the same time that have the same name give a runtime error (i think it always did this anyways)
    •     this was all needed because if updating the model with all items didn’t work, then we’d lose all the position data from before because the page would refresh and any unsaved columns would lose their ordering
  • Uploading from CSV:
    • Feedback please! I can either have all un-uploaded columns deleted or keep all old ones and add just any new ones. If that’s the case, should the uploaded ones be inserted before or after the original ones?
  • Fixed adding grades:
    •    Ties grade to column name now
    •    Doesn’t save grades that are nil, “”
    •    Deletes old grades that are now nil
    •    Grades that aren’t valid (strings) will cause the whole row to not save (as before)

Issues

  • RuntimeError.message isn’t working anymore: saying can’t convert to String

Next Week

  • Write tests!
  • Finish working on csv upload
  • Finally start on something new

Daniyal

Status

  • Researched how repositories are handled in MarkUs. Particularly, how authentication is done.
  • Met with Dylan and Bill to discuss current issues and goals for next week.

Roadblocks

  • Does not look like we can remove SVN bindings by having git interact with SVN since git cannot create SVN repositories.
  • Git will require a authentication system.

Next week

  • Work with Dylan and understand how authentication is currently done.
  • Figure out some of the details of what would need to be done for the new authentication system.

Written by Daniyal Liaqat

October 28th, 2013 at 12:19 pm

Posted in Status Reports

Punchlines ECN – 27/10/2013

without comments

François

Status

- Tried for the third time to install MarkUs

- Self-training on Javascript

Roadblocks

- Markus has not been installed on my computer yet

Next Week

- Spend some time to understand Prototype and jQuery APIs

- Translate some Prototype function into jQuery ones

- Finish MarkUs installation

 

Augustin

Status

-  I was so busy and haven’t worked as planned

Roadblocks

- need to understand better Prototype and jQuery

Next Week

- Technical self-training about Prototype and jQuery

- Development: migration work with Hamid according to Loïc repartition

 

Julien

Status

- working on the translation from prototype to jQuery for some functions

Roadblocks

- Not familiar with the different languages used

Next Week

- Start the migration to give my first patch

 

Loïc

Status

- I have divided work for the team

Roadblocks

- Not really familiar with the different languages used

Next Week

- Self-training about various languages used

- Start work on first files for the first patch

 

Anthony

Status

- Tried to install MarkUs with the virtual machine

- Read tutorial on JQuery

Roadblocks

- Markus has not been installed on my computer yet

Next Week

- Install Markus without the virtual machine

- Read others tutorials on JQuery and Prototype

Written by Loïc Labagnara

October 27th, 2013 at 10:37 am

Punchlines ECN – 21/10/2013

without comments

Augustin

Status

- participated to MarkUs specifications redaction for our group project, especially on:

        – Introduction/Context

        – Listing MarkUs files we will have to migrate from Prototype to jQuery, focusing on api, assignments, automated-tests and flexible_criteria folders inside app>views

- spent some time to understand Prototype and jQuery APIs.

Roadblocks

- Limited understand of MarkUs files architecture, I’m not used to work on software repositories.

Next Week

- Technical self training

- Development: work on folder app/views

 

Hamid

Status

- Reinstallation of MarkUs on my computer

- Participated to MarkUs specifications redaction for our group project, especially on:

               - NEEDS ANALYSIS

               - Listing MarkUs files we will have to migrate from Prototype to jQuery. Especially Files  app/views/admin -> annotations  and in public/javascripts/Bluff & ajax_paginate.js -> create_assignment.js

 

Roadblocks

- Installation of MarkUs

Next week

- Moving the first files from prototype to jQuery

Anthony

Status

- participated to MarkUs specifications redaction for our group project, especially on:

        – Procedures

        – Listing MarkUs files we will have to migrate from Prototype to jQuery inside app>views (from grade_entry_forms to layout)

Roadblocks

- Markus is not installed yet on my computer

Next Week

- Spend some time to understand Prototype and jQuery APIs

- Finish markus installation

 

François

Status

- participated to MarkUs specifications redaction for our group project, especially on:

        – Planning

        – Listing MarkUs files we will have to migrate from Prototype to jQuery

Roadblocks

- Markus is not installed yet on my computer

 Next Week

- Spend some time to understand Prototype and jQuery APIs

- Translate some Prototype function into jQuery ones

- Finish MarkUs installation

Julien

Status

- participated to MarkUs specifications redaction for our group project, especially on:

       - Procedures

       - Listing MarkUs files we will have to migrate from Prototype to jQuery into :

                     - app/views/submission_rules -> app/views/users

                     - app/asset/javascripts/Students/edit.js -> app/asset/javascripts/users_manager.js

Roadblocks

- Not familiar with the different languages used

 Next Week

- Start the migration

- Follow some tutorials to understand languages

 

Loïc

Status

- participated to MarkUs specifications redaction for our group project to move from Prototype to jQuery:

                 - Organisation

                 - Listing MarkUs files we will have to migrate from Prototype to jQuery.

                    Especially Files  app/views/main -> app/views/results  and in app/assets/Groups -> PeriodDeltaChain

Roadblocks

- Not familiar with the different languages used

Next Week

- Follow some tutorials to understand languages

- Moving the first files from prototype to jQuery

 

Written by Loïc Labagnara

October 21st, 2013 at 8:34 am

Status Report – Week of Oct. 7

with one comment

William

Status

 - researched potential solutions for replacing SVN bindings
 - working on blog post explaining solutions SVN bindings for blog.markusproject.org
 - spent a small amount of time learning how SVN is implemented inside MarkUs

Roadblocks

 - Limited understand of how SVN is implement in MarkUs
 - Little idea of where to start working on the binding replacement

Next Week

 - Finish and publish blog post on replacing SVN bindings
 - try to speak to other MarkUs developers on the best approach for how to replace the bindings (with Dylan and Daniyal)
 - potential work on an easy issue ticket, likely issue-323 (https://github.com/MarkUsProject/Markus/issues/323).

Dylan

Status

- Researched solutions for the SVN/Git bindings issue.
- Collaborated with William and Daniyal on how to go about solving the SVN/Git issue.
- Contributed to the blog post to do with the SVN/Git issue
- Spent some time working on issue-999. Still haven’t gotten a hang of rspec/shoulda…

Roadblocks

- Not experienced with SVN, took some work to understand how all the parts like bindings fit together.
- rspec/shoulda are still confusing to me.

Next week

- Finally put issue-999 to rest.
- continue to work with Bill and Daniyal on the SVN/Git issue.

Xiang

Status

I continued to work on the new summary page this week. I got a table with a simple layout and basically all the required data  popped into the table. I am having some issues with the details such as sorting by the new columns and I am working on it. Hopefully I will be able to resolve them and get to more detailed specifications next week.

Arianne

Status

This was my first week really working on understanding the project. I’m still working on ticket 1194: grade entry items should stay in the position they’re added by the user and not get sorted automatically.

https://github.com/MarkUsProject/Markus/issues/1194

I’ve fixed the csv upload so that the order of columns is the same and the grades match up.

Feedback request: if there are grade entry items in the form already that are not in the uploaded csv file, should the extra columns be deleted or should they stay in the form? Ie, should the uploaded csv replace everything already in the form or should existing items be merged somehow (and how… columns with same name replaced and all others just left in? This was quite broken before, so what is the ideal function of upload csv?)

I’ve run into a problem with adding the correct position to grade entry items from the user interface. The main issue is that the attributes to update are sent as a hash and there is no specific order that the updates are done in. I sent an email to markus-dev outlining the problem and asking for feedback.

I’ve looked through a few possible solutions but many of them don’t work for one reason or another. Right now I’m trying to figure out how much more to work on this ticket to finish it up or to move onto something else altogether.

Most important things I’ve learned this week:
Active record associations: http://guides.rubyonrails.org/association_basics.html
Active record callbacks: http://api.rubyonrails.org/classes/ActiveRecord/Callbacks.html
Active record migrations: http://guides.rubyonrails.org/migrations.html
Form helpers: http://guides.rubyonrails.org/form_helpers.html

Daniyal

I’ve been extremely busy this past week, so I haven’t been able to contribute as much as I’d like. I’ve looked over lib/repos and am figuring out what sort of changes we would have to make for each solution. I will try to post my findings as a reply on your post if I can otherwise I will email you in the next few days.

I’m looking forward to starting coding after a bit more discussion on the different solutions.

Written by Dylan Runkel

October 15th, 2013 at 7:07 pm

Posted in Status Reports

Punchlines – UCOSP Winter 2013 – Week 11

without comments

Mike Wu

Status:

Roadblocks:

Next week:

Daniel

Status:

Roadblocks:

Next week:

Oussama

Status:

Roadblocks:

Next week:

Alysha

Status:

Roadblocks:

Next week:

Marc

Status:

Roadblocks:

Next week:

Daryn

Status:

Roadblocks:

Next week:

Ian Smith

Status:

Roadblocks:

Next week:

Mike Stewart

Status:

Roadblocks:

Next week:

Nick

Status:

Roadblocks:

Next week:

Written by Ian Smith

April 3rd, 2013 at 11:36 am