Tuesday, February 24, 2009

Dead week

Well, with the first midterm and project 3 both out of the way, I'm really concentrating on my other class. The timing of projects and and exams is working out well so far between my Automata Theory, Graphics, Software Engineering, and Algebraic Structures classes.

Project 2, the Australian Voting Problem, was done with Joel Gardner. I hosted our repository on my home linux server once again (which makes collaboration very simple), and everything went smoothly. This was the first project that I've ever produced a UML doc, but after about five minutes of experimenting with DIA, we were able to begin creating our doc.

This next project, the Stable Marriage Problem, is an interesting problem that supposedly arose from the need to pair graduating medical school interns with available hospital jobs. I'll be working with Felicia Hopperstad, and hopefully we'll get an early start on it and knock it out a week early.

Looking a bit into the future, after project 4, the remaining four projects will be done as a team of 3-5 people. So far, Felicia, Joel, Sam Kinard, and myself are grouped up. I'm not sure if another group member or two will be added, but either way, I think we'll have quite a productive group. As required by the spec, our projects will be hosted at code.google.com. Speaking of Google's project hosting, Raleigh Schickel and I were chatting today in the Taylor basement, and the subject of project hosting came up. We were checking out Google's project hosting, and I was curious if the source code of your project public as soon as it's hosted in Google's repository (seems like it would since number 7 on Google's Corporate Philosophy is: "7. There's always more information out there."). Well, it turns out, that a read-only copy of your source code is, in fact available to anyone with internet access. A quick search pulls up three hosted projects, and by the user names, I'm almost certain the projects are fellow members of this class. Seeing as academic dishonesty is a very serious matter, and we are explicitly told "You may not share code in any way with your fellow students," I would be very wary of hosting these first four projects through Google, because a fellow student who just can't crack that tough algorithm an hour before the next project is due might just give in and attempt to use yours. You didn't directly give it to them, but you made yourself liable by hosting your project in a way that it's fair game to anyone.

No comments:

Post a Comment