MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for the ‘Status Reports’ Category

Status Report – October 28

without comments

Bryan
This Week:
  • Completed initial prototypes for the Tagging feature views. This includes a new tagging view and additions to the Submissions and Results views to implement the tagging features.
  • Created CSS elements for tags and tagging features.
  • Improved my proficiency in CSS.

Next Week:

  • Getting feedback on the initial prototype and making improvements to it.
  • Cleaning up some of the visual elements to make them conform to the MarkUs standard.
Irene
This Week:
  • Learned about how the controller connects with the models and views
  • Completed dashboard design (sketch and wireframe)
  • Started implementation of the new dashboard. I have split the view into two with the list of assignments and grading spreadsheets on the left but I am still trying to change the view on the right through links in the list. Still trying to figure out how the controller links to the view (getting a nil class error)

Next Week:

  • Continue to implement the dashboard. Next I will need to implement the functionality t hat determines which assignment to display.
Nathan
Last Week
  • finished implementing proof-of-concept to create tags associated with groupings, save in database, and retrieve tags by groupings when loading submissions table
  • minor revisions to migration files as a result of the code I implemented this week
  • opened pull request with migration files and models
Next Week
  • I’m not quite sure what I should do prior to Bryan’s view implementation being merged into the tagging branch.  Once that is merged in, I will implement the code in the correct places to allow creation of tags wherever he has created an UI to do so.  Also I will implement the code to retrieve tags wherever tags are displayed.
Tori
Last Week
  • converting repo browser table to React

Next Week

  • finish converting repo browser table to React

Written by Irene Fung

October 28th, 2014 at 3:49 pm

Status Reports – Oct 21

without comments

Nathan

Last Week

  • revised the proposed schema for database definitions upon further research/readings
  • implemented two migration files for creating Tags Model and a join table for the has_many_and_belongs_to relationships between tags and groupings
  • implemented some code to retrieve tags for each grouping when the submissions table is loaded (hasn’t been tested yet)

This Week

  • sync up with David/Bryan about my migration files
  • implement code to create tags (need to sync with Bryan exactly what information the user will enter for each tag i.e. name, description) etc.
  • once code to create tags is implemented, test creating tags and retrieving when submissions table loaded

Irene

Last Week

  • revised Dashboard plan based on feedback from Karen and David
  • sketched three versions of Dashboard wireframes and chose one with feedback from David
  • started implementing the changes (phase one: separate the view with list on the left that controls the details on the right)

This Week

  • continue implementation of new design
  • commit phase one

 

Written by Nathan Chow

October 21st, 2014 at 6:22 pm

Status Reports – October 14

without comments

Irene
Last week:
  • Fixed and closed Issue #1720 - Ascending/Descending icons change column widths
  • Emailed dashboard plan to Karen and David
This week:
  • Revise plan based on feedback and design wireframes
Bryan
This week:
  • Submitted a new view for issue #1726 (https://github.com/MarkUsProject/Markus/issues/1726). The Flexible Criteria view now has an upload dialog that only enables its upload button when a file is selected.
  • Added and improved a Tag view for the tagging feature. This view is not connected to a working controller but has working upload, download, create dialogs and a React table that is currently filled with “dummy data”.
  • Submitted a post to the MarkUs blog outlining the tagging feature and upcoming features for it.
Next week:
  • Adding tag functionality to the submissions page and the assignment screen. This will allow filtering by tag and assigning tags to assignments. This will still not be connected to the tag controller.

Nathan

Last Week:

  • Looked over the database schema and wrote up proposed changes to the schema for the tagging project
  • Read up on ActiveRecord
  • Unfortunately did not have much time to work on Markus due to other course commitments and going out of town for Thanksgiving weekend

This Week:

  • Begin implementing changes reflected by the proposed changes to the database schema
  • implement logic to create new tags, query for tags, and display tags next to submissions
Tori
Last week:
  • checking out React.js tutorials
  • looking over existing React tables for reference
This week:

  • conversion of table in Repository view to React

Note: I had a hectic sort of week and didn’t put much time into this course; my goal for this week is to put in a minimum of 10h and make up for lost time the following week, which should be less busy.

Written by Nathan Chow

October 14th, 2014 at 7:58 pm

Posted in Status Reports

Status Report October 7th

without comments

Nathan

Last Week:

  •  closed rspec tests and issue 1701
  • started back end investigations for tagging project
  • investigated how to interact with database, putting, getting etc.

This Week:

  • grab Bryan’s starter code when it’s ready
  • hash out concrete design and schema changes
  • start implementing the back end
Irene

Last week:

- Made revisions to grouping rspec test file

- Closed Pull Request #1800

This week:

- Write plan for dashboard and send to Karen and David

- Close Issue #1720
Bryan
This week:
  • Submitted an updated fix for issue #1726 (https://github.com/MarkUsProject/Markus/issues/1726). This improved the javascript code such that multiple independent file upload boxes each with their own upload buttons could be controlled independently of each other.
  • Created a model, controller and new view for the tagging system. This new view can be accessed off each assignment page. It allows administrators to create, manage and delete tags. The view currently has no functionality.
Roadblocks:
  • A major roadblock was learning how to incorporate views into MarkUs. It took several hours to ensure the links and stylesheets all worked for the new view.

Next week:

  • Improving the tag view.
  • Adding tag functionality to the submissions page and the assignment screen. From here, TAs can see tagged assignments and can tag assignments with preset tags.
Tori
Last week:
  • testing issue #1722
This week:

  • get a feel for React tables
  • begin conversion of table in Repository view to React

Written by Nathan Chow

October 7th, 2014 at 5:38 pm

Posted in Status Reports

Status Report for Sept 30th

without comments

Nathan

Last Week:

  • address comments on rpsec pr and resubmitted pr
  • submitted a pr for issue #1701 (download all files button not working, include annotations not working for single file downloads)

This Week:

  • address any comments on two outstanding prs
  • start working on submission tagging project
  • code investigation, how to interact with database
  • what steps need to be taken to display table?
  • what steps need to be taken to insert tags and associate it with a submission?

Irene

This week:
* Created and sent out user study questionnaire regarding MarkUs dashboard
* Submitted pull request for Group model RSpec tests
Next week:
* Fix Issue #1720 “Ascending/Descending icons change column widths”
* Gather responses to questionnaire and start designing wireframes (Issue #1668 Revamp Admin Dashboard)

 

Tori
Last week:
  • learning more ruby/rspec
  • testing issue #1722
  • addressing Hound comments on issue #1722 and AssignmentFile spec
This week:

  • finish testing issue #1722 (i.e. issue #1799)
  • get a feel for React tables
  • begin conversion of table in Repository view to React
Darren
Last week:
* started getting a feel for the RJS files in app/views understanding what I have to change.
* Understanding how to transition the code in app/views from prototype to jquery.
This week:
* continue to learn what exactly needs to be changed in the RJS files
* and implement the changes from prototype to jquery
Brian
This week:
  • Submitted a fix for issue #1726 (https://github.com/MarkUsProject/Markus/issues/1726). This issue was a stylistic problem where upload buttons would remain enabled even when a file was not selected. Now, a jQuery script was written that only enables the button when a file is selected. This change was implemented across multiple modal dialogs.
  • Started working on the back-end for the new assignment tagging system by creating model and controller Ruby scripts for the tags. With this, a schema was created to illustrate what data needed to be stored and the relationships between the Tag model and other models.
Roadblocks:
  • A major roadblock was understanding how Ruby on Rails stores data using ActiveRecord. This roadblock is still ongoing but the issue is starting to make more sense.
Next week:
  • Getting a simple working model and controller implemented for the Tag feature. Although it won’t have full functionality, it will serve as a starting point for implementing the tagging feature.

Written by Nathan Chow

September 30th, 2014 at 12:46 pm

Posted in Status Reports

Status Report for Sept 23rd

with 2 comments

Irene

Last week:

  • Attended the code sprint in Toronto!
  • Fixed Issue #1959 Spreadsheets “Select: All” button doesn’t select all
  • Changed spreadsheets to bigger page sizes

This week:

  • Continue working on Issue #1920
  • Expand on rspec for group model
  • Write questionnaire for Dashboard usability study

 

Bryan

Last week:

  • Attended the code sprint in Toronto and met the rest of the UCOSP participants!
  • Fixed Issues #1728 (Can’t upload hidden assignments) and #1729 (Spreadsheet csv shouldn’t require “”).
  • Created an rspec test for the Annotations model.

This week:

  • Continue working on Issue #1726 with Nathan.
  • Begin to explore a feature to allow TAs and admins to tag assignments. Currently exploring different options on how this can be carried out. See feature #8 for more information.

Darren

Last week:

  • Attended the code sprint in toronto
  • worked on my assigned rspec tests
  • got my development environment set up

This week:

  • Finish off issue #1763
  • start transitioning from prototype to jquery which is issue #1496

Nathan

  • Attended code sprint in toronto
  • finished off first issue
  • started working on issue 1726 and 1701
  • created rspec test for image_annotations

This week:

  • address pull request comments on rspec tests
  • continue working on issue 1701

 

Written by Irene Fung

September 22nd, 2014 at 11:02 pm

Posted in Status Reports

Status Report for Sept 15th

without comments

Bryan
This week:
  • The development environment for the MarkUs Project was setup using Vagrant and Ubuntu 13.
  • Submitted pull request #1750 (https://github.com/MarkUsProject/Markus/pull/1750) for a fix to issue #1728 (https://github.com/MarkUsProject/Markus/issues/1728). This issue was a bug that improperly formatted hyperlinks on the assignment dropdown for assignments marked as hidden. To test the fix, several new assignments were created and marked as hidden. The assignment sidebar worked properly for all these new assignments.
Roadblocks:
  • There was some trouble setting up Vagrant and MarkUs on Windows.  To get around this, Ubuntu was installed and MarkUs was set up on this environment instead.
Next week:
  • Getting ready for the UCOSP code-sprint in Toronto! Working on new issues and fixing bugs.
Chris
This Week:
  • Setup a stable and usable virtual machine running to develop the application in. I had Vagrant running almost immediately and MarkUs shortly there after. However I then noticed that while the application was running in Vagrant there were very long page load times (20+ Seconds). Instead I imported the the VirtualBox machine into Parallels. That improved page load times to about a 1 – 5 seconds on average.
  • I fixed Issue #1493 and submitted a pull request. This was a problem with how totals were displayed and updated in the marks spreadsheet.
  • I noticed the “total_grade” column is managed in ruby and am unsure why this value is being calculated server side and having to be managed manually when it could simply be a calculated SQL column. I have filed an issue (#1762) in regards to this.

Next Week:

  • If Issue #1762 is approved I would like to fix that issue.
  • Complete some more tasks/issues. Possibly some of the spreadsheet related items since I now have some experience working with that component in the application.
  • Attend the Code Sprint!
Irene
This week:
  • Set up development environment. There was trouble setting up MarkUs on Windows 8.1 so Ubuntu 14.04 was installed and it is now working fine.
  • Familiarizing myself with Ruby and Git.
  • Work on Issue #1759.
Next week:
  • Fix Issue #1759, test and submit pull request.
  • Head to Code Sprint in Toronto!
Jakub
This week:
  • Fixed Issues #1746 & #1748. Pull requests have been accepted.
Next week:
  • Determine why some rake tests appear as failing for my environment. Potentially create a couple of issues — depending on their validity — and pick up more issues to tackle.

Nathan
This week:

  • Set up dev environment.  Have a fix for issue 1730
Before code sprint:
  • submit pull request for my fix

Yusi
This week:

  • Set up development environment.
  • Read development guideline and other documentation of Markus
  • Submit pull request of issue-1735
Next week:
  • More reading and prepare for the Sprint.
  • Wait for feedback of the pull request.

Tori
This week:

  • Setting up the development environment. Had some issues dual booting Linux Mint 17 and Windows 8.1 and had to format/repartition my poor laptop 4-5 times (all is well now).
  • Reading up on Git and Ruby tutorials
  • Reading developer guidelines for MarkUs

Next week:

  • Continue getting familiar with Ruby, Rails and MarkUs
  • Get assigned an issue to work on
  • Attend Code Sprint!

Alex & Mark
This week:

  • Solve issue #1456 which is related to SVN repo creation issues (which is a good primer to our main project listed for next week)
Next week:
  • Continue our investigation into how Git has been integrated so far into Markus on the Git branch and assess the contributed code for quality before adding more.

Written by Irene Fung

September 15th, 2014 at 11:22 pm

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