Monday, January 28, 2013

Line 5: Subversion Under Control

Our assignment for this week was to install subversion and get it up and running on our machines. We were to play around with it a little bit, and then download our projects and build them. To this end, Team Obsidian, decided to hold a meeting tonight to get all of our members up and running.

In the last week or so, Hunter got Obsidian posted to a subversion repository hosted at the school. We were all given access to our own little branch of the repository where we may look at, and play with his code, but not actually effect it in any way. We will quickly move out of this state, but for now we all agreed it would be safer for us to learn in an environment where we can't destroy the whole project. We made plans for committing bug fixes in the future, which will involve us going through our code with another member of the project in the hopes that this will prevent faulty code from being pushed. We are also planning on having weekly code reviews, to discuss what our efforts should be focused on each week. Overall, I think these are good precautions to take, and will help us to really focus our efforts and make good progress in bug fixes and making the code more robust.

We are all using the subversion plugin in the NetBeans IDE to commit and checkout our code. This was fairly easy to set up, because you can just run it from inside the IDE. After all members had the project downloaded, Hunter gave a short demonstration of Obsidian and then walked us through the code. He did an admirable job, but as this project is a large amount of code to process, I think I will need to really study it more on my own before I truly get the hang of what it is doing.

Since last I wrote in here, we decided to break from the milestone schedule that we had set for ourselves. The duties we had broken down were each of varying difficulties and lengths, and while some might take all 4 milestones to complete, others would barely take one. Instead, we opted to work on our code base exclusively for the first 2 milestones. This allows each of the members to get familiar with Obsidian, and gain a good understanding of how it works. This way, when we start working on documentation of the project, we will each have that understanding to draw from. We hope that this will make the documentation that much better in the long run.

That being said, I am still going to focus some of my efforts on getting the IRC Channel fully up and running in the next few weeks, and the other members will most likely be tinkering with their given assignments as well. We are just not focusing exclusively on them right now.

We ended our meeting with each member having a working copy of the source code, and a basic understanding of how to utilize it. We will be meeting tomorrow morning to discuss what needs to be done in the coming week.

No comments:

Post a Comment