When we last left off the team had divvied up duties on enhancing the Obsidian project, and had started to populate our Issue Tracker on Google Code in honest. As we worked and issues popped up, we would log them and move on with our lives. As of writing this, our Issues tracker has 18 total issues, a few of which are our entries for enhancements to the projects, and 4 of which are bugs that we have already fixed.
It was kind of heartening to see progress being visibly made on the project, but the enhancements themselves were very slow going. Most of us are still rather unfamiliar with Obsidian, so coming up with ways to implement the changes without breaking the whole thing was rather difficult. Although last time I said that creating class diagrams of the code had vastly improved my understanding of it, it was apparently not improved enough. Hunter however had no problems with talking out these problems and helping us along with our parts. He also made somewhat stunning progress on his own code, and refactored an integral class to be a bit more generic and better structured.
The delivery date we set for ourselves for this first pass of enhancements was this Wednesday, but when we had our meeting today it was apparent that we were probably not going to make that. Apparently, despite Hunter's valiant efforts, we were still to unfamiliar with this project to be of this much use to it. So, we reexamined our strategy and changed our plans. We decided that Hunter would be in charge of added the enhancements we had discussed to Obsidian, while the rest of us would take more of a supporting role on the project and fix up the bugs that we had found, and that were sure to pop up in the future. We distributed bugs to the group members and made a plan to meet with Hunter to discuss them in depth in the next two days.
The reason we decided to change the duties around this way was mainly to speed up the project. This is because we hope to speak to some of the organizers of POSSCON about possibly getting a table or booth to show off our project. We feel that we can reach a large audience this way, and that would really help our project take off. With this in mind, we have to have all of our documentation, code, and cursory information online by March 27. We are of course shooting about a week ahead of that so that we have a buffer period to finish any unfinished items.
One other small victory that we won was obtaining the Google Code URL for just obsidian. We had previously been at obsidian-unit-test-generator, which was much more of a mouthful. Hunter contacted the owner of the Obsidian Game engine project and he agreed to give us his URL, as his project had not taken off the way that he wanted it. This makes us much easier to find and will hopefully prove useful in the future.
No comments:
Post a Comment