The current version of SeqWare is 1.1.1, released on May 1st, 2015. See the release notes for details.

Community

Transition from SourceForge

We are currently transitioning off of SourceForge to GitHub and other services. This is a pretty big task since we have years of content in our current wiki, multiple bug tracking systems, and two mailing lists. Please bear with us while we make this migration. In the mean time you can find our subversion repository and current wiki on SourceForge, see:

Our new site (this one) is hosted on GitHub and we plan on migrating all of our documentation here, the main project web page, our public bug tracker and, of course, our code repository (from subversion to git). The two new sites are:

Mailing Lists

Our user mailing list and our developer mailing list is available on Google Groups. If you want to contribute to SeqWare we encourage you to email the mailing list or Brian O’Connor at briandoconnor at gmail dot com directly.

Issue Tracker

If you encounter bugs or want to make a feature request please email the developer list above (you will need to sign up) and also submit a bug to our issue tracker currently on GitHub.

Wiki

When the transition to GitHub is complete this site will contain all the documentation and we will no longer have a wiki (at least that is the plan). In the mean time you can still use the public wiki on SourceForge which is tailored to developers and is not particularly friendly to new users. This site should be a much better introduction to our project but we are still adding content.

Jenkins and Artifactory

We maintain a Jenkins continuous build server, you can see the status of the project and link to nightly snapshots here. This is really only of interest to developers of SeqWare since we encourage users to download our pre-configured VMs rather than build SeqWare directly.

For those developers building SeqWare we maintain an Artifactory repository for serving and hosting components used in our Maven build process.

Repositories

There are currently two repositories used by the project (see below). The SourceForge repo has all the sub-projects (and several years of cruft) while the GitHub repository has this documentation and the latest SeqWare Query Engine. We will transition from subversion to git as soon as we can. If you want to contribute to SeqWare we encourage you to email the mailing list or Brian O’Connor at briandoconnor at gmail dot com directly.

  • the GitHub git repository for SeqWare
  • the SourceForge subversion repository (Deprecated, please use GitHub)