Archive for September, 2011
Here are the punchlines of our group (students from Centrale Nantes), working on the test framework of Markus.
Markus is installed on my personal Laptop. I did some first tests on Markus. First attempt to define the key elements we have to do on the project.
Next Step :
Define precisely the tasks we have to do. Understand exactly what was done concerning Markus test framework (what is working or not? What still remain to do?)
installation of markus done on my computer
first browsing through the markus platform
first glimpse of technical expectations (one of the main task will be to manage “view” aspects of the test framework)
Next Step :
list precisely what has already been done concerning the test framework
complete specifications of our project
list precisely what has to be done to achieve our project, in agreement with specifications
Having set up the different tools and applications in order to work efficiently on Markus and the project.
Next Step :
First test on the Markus program itself. First attempt to define the job description for the project (requirements and their applications).
I’ve Markus running on my computer. I discovered the Admin section of Markus. Also learn a bit about Rails and the MVC schema (thought I already knew a bit about MCV structure).
Next Step :
Have a loo at the test framework, test what exist for the moment, and write specifications of our project (should be done on Monday)
Markus is now running on my fedora distribution
I discovered the MVC mode
Next Step :
Explore the Markus website when it’s running on my computer. (Admin / student / graders).
Visit the markus developer’s blogs in purpose of knowing what has already been done.
Read some documentations about ant and ruby.
Improve my knowledge in MVS schema.
None for now
Markus account created.
Understand Markus functions and specify priority files.
Next Step :
Complete specifications: Needs evaluation
Install Markus and make my first tests.
Install MySQL on Ubuntu.
Discussed specifics of how people are progressing and gave suggestions to members who were still having trouble getting fully up and running. This included suggestions for tutorials and issues to look at that would help in the learning process.
The majority of projects that the UCOSP team will be looking at were not discussed this week except for the test framework which was discussed in broad detail only due to the fact that another team of students from Ecole Centrale de Nantes will also be working on said project throughout the term.
There was also mention of a co-op student being hired from University of Waterloo to spend a term working on the Markus project either coming winter or spring term.
The team is pleased to announce MarkUs 0.10.1!
MarkUs 0.10.1 fixes a nasty little bug that prevents students from viewing uploaded files when running the french translation.
If you’re running 0.10.0 and want to patch up – download the patch here (you’ll want to apply sequentially). It’s short, sweet, and shouldn’t require any special configuration. All wins.
Great job team – keep up the good work!
- Hacked on MarkUs at the code sprint last weekend and fixed some bugs.
- Reviewed some fixes on Review Board.
- Fix more bugs and start on my project.
- Currently going through Ruby+Rails tutorials
- Exploring and learning the code base
- Find an issue that I can tackle and properly finish it and submit a review
- Currently wrapping my brain around the massive code base that is Markus
- Thinking about which project I would rather work on
- Actually fix a bug and submit a review request
- Finished up issue 269. Added a test to it.
- Refactor old tests to use proper assert statements.
- Work on issue 434.
- Tough to figure out the process taken by the website to present a pop up form on screen.
- Lab machines set up (all clients have an OS on them now, MarkUs runs on the server machine)
- Looked at old benchmark scripts
- Finished hidden assignments (Pending review)
- Had a fun code sprint last weekend 🙂
- Write blog post about how I plan to go about getting some performance/profiling data
- Create a clustered setup of MarkUs on the server machine (i.e. a production installation)
- Try to run old benchmark scripts and see if I can recreate the problem we were seeing when 500+ student-repos were created and started submitting.
here are our first punchlines.
I just install Ubuntu and I will try to install Ruby, RoR and Markus before thuesday. I’m also discovering other tool like IRC and GIT.
I’ve installed Fedora and ruby on my computer, and i’m now working on installing markus. I hope i’ll manage to run it before Benjamin comes to us.
I’ve started to install Markus. And I am trying to understand Markus structure by reading the code on Review Board.
I’m trying to install markus on my computer, my objective is to set it up before our first meeting with B. Vialle.
I have installed Ubuntu and I am discovering more precisely Markus project by reading Markus reports and some releases on Markus website and blog.
As you can see, we just join Markus project last week. The next important step is the meeting with Benjamin next Thuesday.
The MarkUs team is hard at work at our code sprint in Toronto this weekend. We even have some returnees!
Introduction of old members to new members.
Making sure everyone has travel arrangements for code sprint happening Sept 23rd – 25th.
Email code sprint info email will be sent out Sept 15th or 16th.
Reviewed each member’s current Rails knowledge. Advised to get familiar with Rails before the code sprint.
Review Git before coming to code sprint: http://gitcasts.com/
Reviewed each member’s progress installing MarkUs on their machines.
Tentative code sprint schedule:
- Thursday, Sept 22nd: Nothing.
- Friday, Sept 23rd: Meet at CS dept. (40 St. George St) room 3200 at 9am. Work until 5pm. Bring your own laptop. Going out for dinner together, will be paid.
- Saturday, Sept 24th: Meet at CS dept. (40 St. George St) room 3200 at 9am. Work until 5pm. Bring your own laptop. Paid lunch only.
- Plan: A tutorial will be given on Git and how we use it with MarkUs. Ideally 1 ticket closed by everyone by Sunday.
- Created github account and pulled MarkUs
- Installed all necessary gems
- Actually run the thing!
- Trying to get development environment working on a Mac
- Get issues of my setup resolved.
- I am having some issues running the rake commands
- Trying to get dev environment working on ubuntu
- Get issues resolved
- Having trouble with the bundle installer
- MarkUs is not yet set up. Just got Ruby on Rails set up.
- Reading about Ruby on Rails from a textbook I have.
- Get MarkUs set up on my machine
- Late admission.
- In process of getting a “lab” setup for MarkUs performance analysis.
- Determine which resources to use and actually install MarkUs and profilers
- Blog about planned approach for performance analysis in order to get early feedback
- Getting access/Organizing lab machines
The MarkUs team is meeting weekly on irc.freenode.net #markus on Wednesdays, 3 p.m. (EDT). Every Tuesday, each member of the team (including myself) 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 Tuesday, 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.
- Week of Sep 12: punchlines: Severin, minutes: Alex
- Week of Sep 19: code sprint
- Week of Sep 26: punchlines: Luke, minutes: Razvan
- Week of Oct 3: punchlines: Eric, minutes: Severin
- Week of Oct 10: punchlines: Alex, minutes: Luke
- Week of Oct 17: punchlines: Razvan, minutes: Eric
- Week of Oct 24: punchlines: Severin, minutes: Alex
- Week of Oct 31: punchlines: Luke, minutes: Razvan
- Week of Nov 7: punchlines: Eric, minutes: Severin
- Week of Nov 14: punchlines: Alex, minutes: Luke
- Week of Nov 21: punchlines: Razvan, minutes: Eric
- Week of Nov 28: punchlines: Severin, minutes: Alex
- Week of Dec 5: punchlines: Luke, minutes: Razvan
- Week of Dec 12: punchlines: Eric, minutes: Severin
We are 5 students working on MarkUs – as part of UCOSP – this fall. Who are we?
Alex is a forth year Computer Science student at UofT. He is the vice president of the Computer Science Student Union at UofT, creating ample opportunities for students to socialize and have fun while making valuable connections for the future. Alex has most of his experience in Java, C, and Python, but in the past has dabbled in languages such as Scheme. He occasionally uses his coding skills to make little apps that help him make accurate decisions in his favourite video games or help his fellow neighbours. Besides coding, Alex enjoys recreational activities which include but not limited to: ultimate Frisbee, playing board games, baking cakes and muffins, as well as staring at cute pictures of cats.
Luke is a fourth year Computer Science student at UBC. He has worked for UBC on their website UBC Events, for SAP in their Innovation Center and recently for EA on their FIFA site. Luke has worked in Ruby, PHP, Java, C, a little Perl and soon to be added Erlang, Haskell and Prolog! He has also done freelance work on the side, creating websites, and is in the midst of starting a company with a friend. When he’s not on the computer, Luke is rock climbing, bouldering, skiing and playing video games… okay that last one is on the computer too.
Razvan is a fourth year computer science student at UW. He has worked all of his off terms while in school for a startup company in Waterloo called Aeryon labs doing software development for their product. Razvan has spent most of his development experience in C, C++, and Java. In his spare time he enjoys bicycling, running, and exploring the art of video game design.
Erik is a fourth year computer science student at UW. As a co-op student, some of my work terms have included doing SQL & PL/SQL scripting, teaching scheme and c/c++ to first and second year students at the university, and doing iPhone development in objective-c. In my spare time, I like to play dungeons and dragons as well as Magic: the Gathering. In fact, I was invited to nationals in august, and I will be attending a tournament this weekend (sept 17) in Montreal.
Severin is a fourth year Computer Science student at University of Toronto who spent most of the last 16 months hacking on Eclipse plug-ins. In particular, Fedora Packager for Eclipse and Eclipse Linux Tools. Severin’s programming experience ranges from Perl hacking on XIMS, Ruby and Ruby on Rails to Java and Eclipse Plug-ins with some occasional forays into the C/C++ programming world. Severin studied business in Austria, has done Apache httpd web server administration, is now maintainer of some Fedora packages and currently works for Red Hat. He is mostly interested in operating systems, networking, Web programming and computer systems in general. He enjoys to hack on MarkUs in his spare time and will have a closer look at MarkUs’ performance this term. In his spare time he enjoys canoeing, skiing, running, reading, good food and the occasional beer as well as describing himself in the third person 😉
I look forward to meeting you at the code sprint!