-
Notifications
You must be signed in to change notification settings - Fork 2
Tools
##Language Java 6 (specifically 1.6_14 or higher). We considered 1.7, however it’s newness and lack of full cross-platform support (e.g. not yet available on Mac OS X) led us to chose Java 1.6. We also considered using .NET, however team familiarity was highest with Java.
##Libraries
##IDE Eclipse Indigo - Selected due to team familiarity. Free. Netbeans was considered, only long enough to be rejected, though we may revisit this for UI work. JetBrain’s IntelliJ was also considered. However, the free version is limited. We have collected several tips for setting up Eclipse to work in our environment.
##VCS Github - Selected due to team familiarity with Git. Successful use in previous projects. No other options were seriously considered.
##License MIT - Selected due to its brevity. Also because it is one of the most liberal licenses. With the target audience being the aerospace industry, we wanted to make the code as accessible as possible.
##Continuous Integration TeamCity (via Codebetter.com)
- Scott: sgriffinusa
- Mike: SQUIDwarrior
- Liron: lyahdav
- Ryan: lone.squirrely
- Brandon: brandons
Project website We chose TeamCity because several of our members have direct experience with the tool and have found it to be far superior in usability and features to other options such as Hudson or CruiseControl. There is also a free TeamCity server hosted by Codebetter.com that is available for OSS projects. We also considered Heroku, but that is more targeted to hosting websites.
##Issue/task tracker ###Planning and tracking - Pivotal Tracker Pivotal is one of the best online tools for planning and tracking Agile projects. All team members are familiar with Pivotal through our CMU coursework or in our jobs. It is also free to use for OSS projects. Project site
###Bugs/tickets: Github Issues Because our project is hosted on Github, utilizing the Github issue tracking system is a natural choice. One of our members has used this system before and had a good experience. We also considered Codebetter’s YouTrack server, but that does not integrate as closely with Github. Project site
##Builder:
Team familiarity. Interest in learning Maven from those who have experience with Ant.
##Unit test Initially we decided to use JUnit. However, Chris recommended looking at TestNG. No one had experience with it, but since it is built on JUnit, the learning curve should be light. We decided to use TestNG to gain exposure to the tool.
In order to run tests easily from Eclipse, it is useful to install the TestNG plugin. Instructions are here: http://testng.org/doc/download.html
##Documentation: OpenOffice or MS Office (undecided at this point). Is there any restriction on using Microsoft office in an open source project?
##Collaboration Tools Since we are a remote team, we need good collaboration tools to maintain our productivity. We decided to use Mikogo for screen sharing purposes, due to it’s excellent performance record. We also will be using Skype for both audio and video conferencing. We have used Adobe Connect in the past, but it tends to be unstable and the performance is often unacceptable.
##Hex Editor Chris told us that Notepad++ has a hex editor plugin that is very useful when editing and creating binary files.