Project Report and Ideas for Contribution

As far as the project report, the ITK site contains detailed descriptions of the project, it's functionality, and history of development, as well as a list of core members.  Writing up the report is as simple as annotating these sections of the website.

After signing up for the ITK development mailing list, I sent out an email to the team introducing myself.  Additionally, I provided background information on the intentions of our Software Engineering Practicum class, and asked for any feedback on ideas for contribution.  Within the day, I had heard back from 3 separate members welcoming us to the community and directing us to their bug tracker and ideas wiki.

The welcoming responses produced a sense of acceptance that I had not experienced in the past working on OpenSource projects.  Although project ITK is still somewhat intimidating of a project, I am now even more glad that our team has chosen this project.

Along with being greeted by these 3 developers, several ideas for contribution were also provided.  The ideas included tackling bugs from the bug tracker, working through some small problems found on their ideas wiki, as well as a larger and more indepth mentored focus idea.  It was suggested that we start off by working through some bugs on the bug tracker so that we can become aquainted with the submission process, as well as allow the community to assess our capabilities.  Several problems on the ideas wiki, specifically the "wish list" and "small problems" section also sound promising for potential focuses.  As far as the specific mentored project, it is great to have someone already volunteering to mentor us, but the application seems to be a lot more intense, and it would behove us to start with smaller tasks first, in my opinion.  Regardless, it is nice to have somewhat of a sense of direction in the project.