Archive for the ‘Agendas’ Category
The Winter 2013 MarkUs team had a fun and productive 3 day weekend at Facebook HQ for our educational hackathon. I just wanted to let everyone else on the MarkUs team know what we accomplished, what our future goals are and what each of us plan to be working on for this term.
What did we accomplish while we were there?
The team was mostly setting up for the day. There were some issues happening with the svn-ruby bindings on Mac OS X and Linux, but they were resolved by the end of the day.
The team eagerly started looking at issues and making trivial commits to get a hang of Git and Github. A bunch of issues were created, older issues were cleaned up, and we got a feel for how MarkUs worked from the demo Karen gave. The team also got a nice amount of pull requests in fixing previous issues.
The last little bit of coding was mostly looking at the pull requests from saturday and fixing any issues that occurred. The team continued to work until the presentations where all the hackathon teams gave an overview of their project.
Winter 2013 Term Goals for MarkUs
What are some of the goals we would like to see get accomplished this term?
Testing Framework – Feature
One of the more important features of MarkUs. This testing framework will allow graders to upload their testing suite to MarkUs that can be used to run student’s code to determine any faults in their programs. The goal here is to fix up remaining bugs as well as code syntax issues.
Remark Requests – Feature
Another nice feature that would be beneficial to MarkUs. This is where students have the ability to submit a remark requests for assignments. A nice feature we can add here is to add a side by side comparison window (original assignment vs remark assignment).
Grade Entry Sheets
Grade entry sheets already exist within MarkUs, but more functionality can be added to them. A couple features we discussed are:
- Multiple Sections for Students
- Give the ability to assign students to multiple sections
- TA Grading
- Allow TA’s to enter marks
Switch Prototype to jQuery
- The difference between communities is huge
- Because of the popularity of jQuery, there has been an enormous increase of Stackoverflow questions (jQuery’s 265932 tagged questions vs Prototype’s 2114 questions) and plugins for it. Along with popularity, if students know jQuery coming into MarkUs, that is one less framework they have to learn.
- jQuery allows chaining and if used properly, allows for more readable and understandable code.
Upgrade Ruby & Rails versions
Make the upgrade to Ruby 1.9.x and upgrade Rails to 3.2. We also discussed whether or not this should be left for the summer team to complete, as we did not know how complex this would be.
Replace SVN for Git
This is one of the lower priority goals for the term. Git is another version control that has seen an immense popularity gain in the last few years. Few key reasons for this:
- Git repo size much smaller compared to SVN size
- Git is faster than SVN
- Git is a distributed system
svn-ruby bindings are a bit of a pain to set up on some operating systems. Not sure if Git will be any easier, but more research on this topic will definitely have to be done.
What will the team be focusing on for the time being?
Daniel St. Jules – Database issues, schema and performance optimization
Alysha Kwok – Remark requests
Nick Lee – Testing framework
Mike Wu – Remark requests
Mike Stewart – Grade entry
Ian Smith – Testing framework
Marc Bodmer – Prototype to jQuery and replacing SVN for Git
(copied and adapted from Mike’s post last term)
The MarkUs team is meeting weekly on irc.freenode.net #markus on Thursdays at 3:00PM(EST). Every Wednesday, each member of the team must come up with a “punchline” status update. These updates are short, bulleted, straight-to-the-point reports that tell us how everybody is doing. They follow a very simple format: see these three examples. The punchlines need to be published on this blog every Wednesday, and it is every team member’s responsibility to give them a read before coming into the meeting.
But instead of everybody logging in and editing a single blog post for the status updates, we’ll rotate responsibility for collecting/publishing punchlines every week. Similarly, we will rotate the duty of converting our IRC meeting logs into notes.
Here’s the schedule outlining who is doing what each week. Teammates: I highly suggest bookmarking this page.
- Jan 27: punchlines: Misa, minutes: nobody
- Feb 3: punchlines: Yansong, minutes: Karel
- Feb 10: punchlines: Karel, minutes: Danesh
- Feb 17: punchlines: Danesh, minutes: Ibrahim
- Feb 24: punchlines: Ibrahim, minutes: Bertan
- Mar 3: punchlines: Bertan, minutes: Oloruntobi
- Mar 10: punchlines: Oloruntobi, minutes: Misa
- Mar 17: punchlines: Misa, minutes: Yansong
- Mar 24: punchlines: Yansong, minutes: Karel
- Mar 31: punchlines: Danesh, minutes: Ibrahim
- Apr 7: punchlines: Bertan, minutes: Oloruntobi
- Post-mortem (date TBD): punchlines: Misa, minutes: Yansong
Note that this schedule may be subject to change. Check back frequently.
Victoria has made a solid improvement on the look and feel of group and assignment pages
Assigning TAs among students should be made easier.
Grade Entry Page
Farah has released the grade entry page, which looks fantastic.
Farah will work on the tickets related to the student UI, and implement the feature that enables users to release the marks.
Mike has shown a demo where user use back, forward and bookmark on the the submission pages.
Joseph has altered the submission pages to use server side pagination, and he is dealing with the filters and showing X per page.
Joseph has also figured out how to put page parameters into url.
Flexible Marking Scheme
Brian is focusing on the functionalities currently and will soon produce some prototypes.
Bryan will soon join the implementation of Flexible Marking Scheme.
Robert has made Assignments and Students compatible with notes system
Robert will turn Student and Assignment Unit tests to Machinist by the end of the week.
Farah has created a tichet for CSV upload/download.
Bryan has solved a ticket and done some Machinist tests.
Severin’s api for loading test results has enabled users to delete a bunch of results
Please contact Victoria and Karen if there are UI issues.
Two full-time students will work for the summer.
- Great job on getting the development environment installed! And on all three platforms! Wow!
- Check that all the travel arrangements are set. (Code sprint is one week away)
- Dole out some tickets. Talk about how to approach it. If there isn’t a test already that shows how it fails, it may be worth writing the test. (If all that is manageable is to write the test that exposes the bug, that would be a big step.) Sometimes, it might not be necessary or possible to write the test.
- Time management. It would be amazing if everyone could come to the code sprint having already checked in some code, but we will be spending all of the next weekend working on MarkUs, so everyone should make sure that they spend enough time on their other school work.