UCOSP brings together students from coast to coast to work together on joint capstone projects. Students learn first-hand what distributed development is like. Each team has students from two or three schools, and uses a mix of agile and open source processes under the supervision of a faculty or industry lead. Find out more about UCOSP.

Latest news

MediaWiki spins up

Shealen Clare writes:

After a great kickoff weekend in Vancouver we’re back in our separate cities, ready to continue work on our selected project. We’ve chosen to adapt the existing Wikipedia Android app to a Wiktionary app. Our goal is to provide maximum functionality with minimal change to the code – especially restricting our changes to the Javascript wherever possible.

As of the beginning of February, we’ve got a product that works but still requires some fine-tuning. The WMF team we’re working with – including Amgine, Sumanah, Tomasz, Brion and Yuvipanda – meet with us twice weekly to help us keep moving forward. So far we’ve had a number of Scrum-style meetings that have resulted in a number of larger solutions, including the decision to rebase and the request to have our own repository.

Features that are either close to, or already, finished include language detection, “look up in Wiktionary” (from any other app,) audio pronounciation of words and Word of the day.

Our wiki page: https://mediawiki.org/wiki/UCOSP_Spring_2012

Our git repo: Current: https://github.com/pfhayes/WiktionaryMobile

Our git repo: Future: https://github.com/wikimedia/WiktionaryMobile

UMPLE’s first status update

James Zhao writes:

This is the first blog post from the UCOSP Umple Team for Winter 2012. We are working on Umple project, which is a modeling tool and programming language which allows one to perform model-oriented programming.

My fellow USCOP colleagues have been working on some interesting projects. Adam Dzialoszynski has been working on SQL statement generation, which allows Umple to generate an SQL database schema. Sonya Adams has been working on adding a new feature to the Umple language which allows a class to be declared as immutable. Jordan Johns has been working on improving how code comments written in Umple code are saved and transferred to the compiled destination programming language code. Luna Lu is currently working on issue 142 which deals with a bug in the language where deletion on a object that has a 1-to-many association is not working. Song Bae Choi is working on issue 21, where Umple in a certain circumstance generates uncompilable Java code.

What I have been working on is to make the Umple compiler appear more like the gcc compiler. I have started by adding command line options to the Umple compiler, implementing some of the simpler command line options, such as printing the current compiler version number. I am currently working on a command line option feature, which can control the programming language Umple will output.

After having started working on Umple for three weeks, I have learned how to look at large projects with multiple components. Also now understand the use of ant build scripts, which will be very useful in the future. A challenge now is juggling time between my other busy courses and Umple work. I expect this to be a very important skill to have since I would like to participate in more OpenSouce projects in the future.

 

MarkUS on the Code Sprint

Oloruntobi (Tobi) Ogunbiyi writes:

The UCOSP code sprint for the winter 2012 semester was held at UBC, Vancouver between January 20th and 22nd. The MarkUs Canadian team for this semester is made up of 3 students from UBC, 4 students from University of Toronto, 1 from York, and 1 from SFU. MarkUs is an online marking tool that provides instructors with the ability to hand out assignments online, students with the ability to submit the assignments and graders with the ability to grade and give feedback to students.

Most of Friday was spent at getting MarkUs development environments set up. There was also a Distributed Version Control System tutorial focusing more on the general use of Git which was followed by a MarkUs specific Git tutorial. Due to numerous architecture and operating systems issues, we also had to spend part of Saturday setting up some environments while students already set up fixed some bugs. Sunday was spent working on bugs and saying good byes. By the end of the code sprint, we got to fix three bugs and start working on many more.

The code sprint this semester was great. We got to visit Vancouver and meet other UCOSP students.