Taverna Mailing Lists
There are two mailing lists available for the Taverna project, these are hosted by sourceforge and the links below allow you to subscribe and view the mail list archives. Please be aware that both developer and user lists are public. We suggest that users should join the user list at least - this allows us to notify you of any critical issues or upcoming changes and allows you to have a say in the future development of Taverna. Anyone seriously contemplating using the Taverna APIs in their own code would be well advised to join both lists.
Please do not email the individual developers - you are much less likely to get a response, we’re all on the mailing lists! e-mail support is available at support@mygrid.org.uk
Before sending a message to a mailing list, please make sure the question is not answered in the Taverna Tutorials or Taverna Documentation.
Browse and search archives
You can browse all Taverna lists at once, or do a search in all our lists using the form below:
Taverna users list
Intended for everyone else, if you’re using any of the code from the Taverna project we’d be very interested in your feedback, this list would be a good place to put it.
- Subscribe to the list
- View the list archives at markmail.org
Taverna hackers list
Intended for those actively developing the Taverna project, this list is used to record problems, design decisions and general code and architecture prodding.
- Subscribe to the list
- View the list archives at markmail.org
Feature request and bug tracking
You can browse the current issues and features that have been reported in our issue tracker Jira. The software running the issue tracker has been provided to us - as an open source project - free of charge by Atlassian.
We recommend that you report possible bugs and feature requests to one of our mailing lists, and our dedicated support hat person will respond and enter the issue into Jira if required.
Although you might register as a user of our issue tracker, you will by default not have permission to submit new bug reports, the main reason for this is that we received too many spam “reports” and comments, but we might review this policy at a later stage.