Today, Team Obsidian met again to further discuss our POSSCON plans. We finished writing up our proposal for the table, and Hunter is going to get criticisms from Dr. Bowring tomorrow morning. This meeting was very short, and the only thing we worked on was the proposal. I hope that this proposal will get us a table so that we can really open up our project to the community at large.
We have also been given some exercises to complete for class tomorrow. Most of these focus on getting further involved with bug fixes for our OSS projects.
6.4
The oldest active bug on the Obsidian project is the request for a better naming algorithm for naming test classes. The current method for creating them can create a bug when test classes have already been created. This bug will be fixed by creating a new method for naming the test classes that will follow the same flow as naming method tests. The way that it is now, there is just a very static procedure for naming test cases. This bug doesn't seem like a very hard fix, so I have chosen to solve it for my first bug fix.
6.5
This exercise was to create an account on the bug tracker for our project, so that we can solve and create bugs in the future. This exercise doesn't really have any impact on our project because we are in charge of making the bug tracker, so we have all already created accounts for our issue tracker.
6.6
The next exercise was to try to reproduce a bug from our project. I accomplished this pretty easily, because the project that we are running Obsidian on, Common Lisp for Java, reproduces the bug I mentioned before very easily. As part of our meetings this week every member of our team met with Hunter to discuss and reproduce our bugs. During my meeting we discussed strategies for solving these bugs, and we also reproduced the ones that I had taken responsibility for.
6.7
Our final exercise had us perform triage on 5 bugs. This is basically laying the groundwork for solving them, and making them easier to solve as a result. Since we are such a tight knit team, most of these are also redundant activities for us. We classified these bugs according to severity and priority when we uploaded them to our issue tracker, and we are all aware of their effects and scope.
I did find it rather helpful information though, because it let me know that the team was on the right track with our meetings and bug discussions. It will also be useful information in the future.
The other thing that I did today was taking a tour of Sparc. Sparc is a local company that predominantly does software design for the government. They have been branching out into more open software recently, and they seem like a pretty fun company to work for.
Our tour basically took us around their office, and we briefly met a few key members of the organization. The whole office is a large open area with lots of pathways between the teams. They follow the agile approach to programming, and seem to focus on their employees a lot. Overall it was a pretty good tour.
No comments:
Post a Comment