-
Notifications
You must be signed in to change notification settings - Fork 1
Home
MarkUs (pronounced "mark us") is an open-source tool which recreates the ease and flexibility of grading assignments with pen on paper, within a web application. Designed to support programming assignments, students may submit their work through the web interface or through a version control system. Students can form groups to collaborate on assignments. Instructors add marking schemes, assign graders to students and then later release the marks to the students. The graders can view the students submissions, fill in the marking schemes, and annotate the students work. MarkUs facilitates much of the administrative work of setting up and grading an assignment.
MarkUs is written using Ruby on Rails, and uses Subversion to store the student submissions. MarkUs is the successor to the OLM project, an earlier grading tool.
- Project Website
- Developer's Blog
- Code Review
- IRC Channel: Our channel is #markus on irc.freenode.net. Logs of the channel are also available.
- Sandbox
- Git Resources:
- Issue Labels
- Student File Submission: September 2 2009
- Student Group Formation: August 17, 2009
- The Grader View: June 6, 2009
- Flexible Marking Scheme Selection: December 1, 2009
- Flexible Marking Scheme Criterion: December 1, 2009
- Notes created through the Modal dialog as an Admin: December 3, 2009
- Notes created through the Modal dialog as a TA: December 3, 2009
- Creating and editing a grade entry form as an admin: December 4, 2009
- Notes tab: December 11, 2009
- Entering and releasing the marks for a grade entry form as an admin: April 4, 2010
NOTE: Windows is not supported anymore
Repository: Create a GitHub account and fork MarkUsProject/MarkUs (see GitHub help for more info).
Mailing list address: markus-dev@cs.toronto.edu
Mailing list archive at marc.info
Aaron Lee, Adam Goucher, Aimen Khan, Alexander Kittelberger, Alexandre Lissy, Alex Krassikov, Alysha Kwok, Amanda Manarin, Andrew Hernandez, Andrew Louis, Angelo Maralit, Anthony Le Jallé, Anton Braverman, David Das, Arianne Dee, Benjamin Thorent, Benjamin Vialle, Bertan Guven, Brian Xu, Bryan Shen, Camille Guérin, Catherine Fawcett, Christian Jacques, Christine Yu, Christopher Jonathan, Clément Delafargue, Clément Schiano, Danesh Dadachanji, Daniel St. Jules, Daniyal Liaqat, Daryn Lam, David Liu, Diane Tam, Dina Sabie, Dylan Runkel, Ealona Shmoel, Egor Philippov, Erik Traikov, Eugene Cheung, Evan Browning, Farah Juma, Fernando Garces, Gabriel Roy-Lortie, Gillian Chesnais, Geoffrey Flores, Hanson Wu, Horatiu Halmaghi, Ian Smith, Ibrahim Shahin, Jay Parekh, Jeffrey Ling, Jeremy Merkur, Jeremy Winter, Jérôme Gazel, Jiahui Xu, Jordan Saleh, Joseph Mate, Joseph Maté, Justin Foong, Karel Kahula, Kitiya Srisukvatananan, Kurtis Schmidt, Lawrence Wu, Luke Kysow, Marc Bodmer, Marc Palermo, Mark Rada, Mélanie Gaudet, Michael Lumbroso, Mike Conley, Mike Gunderloy, Mike Stewart, Mike Wu, Misa Sakamoto, Neha Kumar, Nelle Varoquaux, Nicholas Maraston, Nicolas Bouillon, Nick Lee, Nicolas Carougeau, Noé Bedetti, Oloruntobi Ogunbiyi, Ope Akanji, Rafael Padilha, Razvan Vlaicu, Robert Burke, Samuel Gougeon, Sean Budning, Severin Gehwolf, Shenglong Gao, Shion Kashimura, Simon Lavigne-Giroux, Su Zhang, Tara Clark, Tiago Chedraoui Silva, Tianhai Hu, Valentin Roger, Veronica Wong, Victoria Mui, Victor Ivri, Vivien Suen, William Roy, Xiang Yu, Yansong Zang, Zachary Munro-Cape
Supervisors: Karen Reid, Morgan Magnin, Benjamin Vialle, David Liu
Status Reports:
- Getting Started with Ruby, Ruby on Rails and MarkUs
-
MarkUs Coding Style/Coding Practices/Rails Gotchas
- Basic Guidelines for MarkUs Development (IMPORTANT!)
- How To Do a Code Review
- Rails erb quirks
- Please document your code according to the RDoc specification (see How to Use RDOC)
- Difference between COUNT, LENGTH, and SIZE
- Our Ruby/Rails testing guidelines
- Security testing guidelines
- Internationalization
- MarkUs API/Test Coverage
- MarkUs Releases
-
User Roles and Stories for MarkUs
- General / Constraints
- MarkUs is internationalized
- MarkUs is configurable
- Rubrics are not allowed to change once Submissions have been collected
-
Instructor
- Instructors can create / edit assignments
- Instructors can download / export files
- Instructors can hide students
- Instructors can do everything that Graders can do
- Instructors can release / unrelease completed marking results
- Instructors can map particular students / groups to Grader_(s) for marking
- Instructors can download / export a file that describes the Student /Grouping mapping to Graders
- Instructors can upload a file that will do the Student /Grouping mapping to Graders
- Instructors can manage groups without restrictions
-
Grader
- Graders can easily tell which submissions are assigned to them to mark
- Graders can view a Submission from a Student / Grouping
- Graders can view / annotate / mark a particular file from a Submission
- Graders can add annotations to particular lines of code within a Submission File
- Graders can create reusable Annotations
- Graders can create short, formatted overall comments on a Submission
- Graders can view and use a Rubric for marking a Submission for an Assignment
- Graders can view a summary of marked submissions
- Graders can add bonuses / penalties to submissions
- Graders can modify the marking state of a submission result
- Graders can easily switch to the next / previous Submission for marking
- Student
- General / Constraints
-
Database Schema
- AutoGenerate Database Schema
- Questions and Answers (Old Document)
- MarkUs Component Descriptions
- Feedback Notes
- Tips and Trick
- IDE/Editor Notes
- Setup Instructions for MarkUs Stable (MarkUs 0.10.0)
- Hosting several MarkUs applications on one machine (for Production)
- How to use LDAP with MarkUs
- How to use Phusion Passenger instead of Mongrel
- Old Setup Instructions for MarkUs Stable (MarkUs 0.5, 0.6, 0.7 and 0.8 branches)
For a complete list of local wiki pages, see TitleIndex.