The MarkUs Team is proud to present MarkUs 0.7.0!
Archive for the ‘MarkUs’ Category
Posted by Mike Conley on 2010/04/29
Posted by brianxu on 2010/03/26
The meeting minutes can be found here
Posted by Mike Conley on 2010/03/20
The MarkUs Team is proud to present 0.6.3! Full details here.
Posted by Joseph on 2010/03/19
- Brainstormed ideas for the Dashboard.
- Went through draft Dashboard contents with Karen and Farah and got some good and constructive feedback
- With the feedback I got back regarding the potential Dashboard contents, come up with a preliminary prototype — one that we can take apart and help establish a better idea as to how we’d like to design the Dashboard.
- Swamped with work (from my full-time position).
- Applied 0.6 patches to trunk
- Also caught some missing translations and brought them over from 0.6
- Reviewed a bunch of code
- Email / IRC development support
- Same as always – review, review, review. Answer email. Help where I can.
- Finished implementing the ability for an instructor to release/unrelease the marks for grade entry forms
- Submitted a review request (in two parts) for the student UI and releasing the marks (see http://review.markusproject.org/r/458 and http://review.markusproject.org/r/459/)
- Modified the table view so that the text boxes for entering grades are smaller
- Worked on unit tests for the student UI and releasing the marks and submitted a review request (see http://review.markusproject.org/r/473/)
- Work on functional tests for the student UI and releasing the marks
- Implement CSV upload/download for grade entry forms
- Tests for CSV upload/download
- None this week
- Met with Mike on Tuesday to discuss how to test the server side pagination
- renamed ajax pagination helper to pagination helper ( http://review.markusproject.org/r/470/ )
- migrate the submissions_controller_test from fixtures to machinist ( http://review.markusproject.org/r/474/ )
- continue with the testing
- finish of the suggestions from reviewers
- get a start on the detailed submissions view
- Wrote a draft version of user stories: assigning graders to criteria.
- Introduce factory data preloader, which can be used in conjunction with Machinist and improve its speed. Modified the results_controller_test.
- Finish the class diagram and database schema for the feature “assigning graders to criteria”
- Plan how to use single table inheritance to implement flexible and rubric criterion
- Find a good pattern for factory data preloader
- The ability to create Notes on Assignments, and Students from the new notes page is complete and awaiting final approval.
- Added tests for the new noteables to the Notes Controller Test
- Converted Notes Controller Tests to Machinist
- Added a Machinist blueprint for Notes.
- Add the notes dialog links to the Student pages and the Assignment pages.
- Convert the Student and Assignment tests to Machinist and Shoulda.
- Fix a small bug Ticket #622
- Working on refactoring database, doing some test
- Improving flexible schemes
- make flexible scheme ready to ship
- make prototype of new database design
Posted by Farah Juma on 2010/03/13
The MarkUs team had its weekly meeting this afternoon. It’s getting close to the final stretch now! Our meeting minutes can be found here.
Posted by Mike Conley on 2010/03/07
The team is pleased to present 0.6.2! Full details here.
Posted by Mike Conley on 2010/03/06
The MarkUs team is plowing forward, fleshing out some fantastic new features, and kicking a bunch of bugs to the curb! You can read our meeting minutes here.
Posted by brianxu on 2010/03/01
The MarkUs team’s meeting minutes for this week can be found here.
Posted by brianxu on 2010/03/01
The MarkUs team’s status punchlines for this week can be found here.
Posted by brianxu on 2010/03/01
The time is running so fast that it is already the middle of the term. It has been a quite exciting time for me since I joined UCOSP, joined my team – MarkUs. After 2 months work with our team, I feel more confident in working for MarkUs.
What I have learned
For the technique aspect, I am more familiar with Rails development. I have learned setting up the workspace for Rails, basic Ruby syntax and basic way of Rails development. I have better understanding of MVC framework after diving into our project. I have to say it accelerates my learning speed of Rails a lot with such a well organized application on hand. When I look into the codes, I found it really easy to read and understand. Even if sometimes I got confused, I can ask our team members and get immediate response. After the first half semester, I got better understanding of our project and I learned a method to “find a way to go” for a problem.
For the team work aspect, I feel really comfortable working in our team. Communication is emphasized a lot in our team. As we have a pretty big team with team members located in different cities even in different country such as France, we are using several ways such as irc weekly meeting to keep in touch with each other. I like the weekly meeting which provides chance to present our progress and ask questions. I also find it benefits me a lot to communicate with our team on review board. Our team’s members usually give immediate feedback for the uploaded codes and those suggestions are really helpful. It is also very exciting to see your team members give a “ship it” after your revise your codes several times. I feel encouragement from my team consistently and it provides me more enthusiasm to work on our project.
What I have done
Up to now, I feel that I am on track with my assignment for Markus. For the first few weeks, I spent most of my time to solve some easy tickets on the list. It was also a good practice of learning Rails. After finishing several tickets I started to work on the main task of the semester – flexible scheme at week 6. In the following 2 weeks I spent my time reading the task proposal and exploring the existing project. I produced a prototype with most of the basic functionalities last week. If everything goes well, the flexible scheme shall be finished within 2 weeks.
For the next half of the semester, I will firstly make the flexible scheme be ready to ship as soon as possible and I will keep fixing bugs on the ticket list. I think for the first half of the semester, I didn’t review other members’ code enough. So I will also spend more time reviewing codes on review board. I am also willing to get other “big” task to do if I have time. I think my overall performance is “ok” .However that’s because I spent a lot of time in searching and exploring to understand the problem which might not be very efficient. I will focus on increasing my efficiency for the rest of the semester.
Thanks to UCOSP to give me such an opportunity to work on such an exciting project. I am sure I will carry more enthusiasm and do better performance for the next half of the semester!