This post will be lackluster compared to the previous posts and future posts of this blog. The purpose of this post is to focus on what bugs, features, documentation, etc. that my team and I selected to work on for the rest of the semester (in regards to Galaxy).
Now, our team has not been able to have a stable meeting due to the inclement weather that has been happening but a few of us were able to maintain slight contact over the web and try to manage issues that way. We have selected a first bug, as mentioned in an earlier post. We, as a team, will be deliberating tomorrow as to what other bugs or features we want to add. It would be much more settling if, as a team, we decide to add a feature as our second task(s) as it is much easier to expand an open source software and work with bugs that we may cause in our feature than it would be to handle other bugs that may be critical to someone else's work (which can result in problems with redundant work and 'being beat to the punch' with regards to completion time). Additionally, implementing a feature also will give us, as a team, a chance to contribute our own documentation to the Galaxy community.
Galaxy has very rigid standards when it comes to coding styles and documentation whenever contributing to their source. I believe this will be an annoyance to us, as a team, but we will be grateful for the experience of coding and documenting in this manner, for obvious reasons. This will give everyone a chance to work with Python, XML, and a documentation framework with which I am unfamiliar. Penultimately, we have created a small timeline of actions, but it merely is stating that we will be working on bug fixes and feature additions over certain time periods without the specificity we would like. Finally, this post will be expounded upon whenever our team meets next and flushes out our final plans.
Music listened to while blogging: Kendrick Lamar
No comments:
Post a Comment