The StormWind Project was created to provide tools for the .NET community by Bernardo Heynemann and Claudio Figueiredo in mid 2007.

It is now home to several projects which can be viewed on our project page .

There are several tools that we use on the StormWind project which have helped to make the development of our projects significantly easier:

Fisheye for Source Control Information

Fisheye is an amazing tool to give insight into Source Control Repositories. We at the Stormwind Project are always keen on trying new tools that help us get more information on our own projects.

So, each project that is under active development features a repository in http://fisheye.stormwindproject.org. Ok, but what can I get out of this information.

Well, I'm sure that one of the things you ask yourself when choosing an open source project to use in your company is: How active this project is?

Since we, at Stormwind Project, believe in maximum transparency, we enable anonymous access to all our tools. That means you can check on whatever we are doing at all times, without ever as much as mentioning to us. Fisheye is one of those tools. It will give you detailed reports on the activity in each of our projects, thus enabling you to make a better decision on whether you want to commit your company's resources to one of our projects.

ThoughtWorks Mingle for Project Management

Confirming our affirmative above on maximum transparency, our tool of choice for project management (ThoughtWorks Mingle) will also allow users to check on what stories we'll be playing in each iteration, what's next and what we've already achieved in each project.

We are in the process of setting this infrastructure up, so you'll get more and more information about how our projects are managed.

JIRA for Bug Tracking

So, after using one of our projects, you found a bug. That's ok, we acknowledge that there's no such thing as perfect software. We can have perfect relationship with our community, though. If you find a bug, there are two courses of action that you can choose.

The first one is to raise the bug and wait for prioritising by the Committers, and subsequent fix.

The second one, which is faster, is to fix the bug yourself and commit a patch to the project.

We'd like to make a point here that we're not saying that you MUST choose either way, as we're committed to fix any bugs that our users find in one of our projects. We're just trying to get some help, and the best way to helps us help you is to contribute.

Now, to raise a new bug, all you have to do is find in the project page here in the portal, the link for the JIRA page responsible for tracking issues with that project. After raising the issue, if you want to contribute a patch to it, just attach the patch to the issue and our committers will look into it asap. You can find the main JIRA application at http://jira.stormwindproject.org .

Build Server for Continuous Integration

A build server is an integral part of open source projects, since we must have an efficient versioning system, and a way for our users to know whether the software they are getting is being developer under maximum caution. Right now, we are short of a build server that satisfies all our needs, but we are working to change that.

You can expect news soon.