2008/12/3 James Taylor <james.taylor(a)emory.edu>:
> At the moment, the main repo is maintained by the galaxy team,
and
> that is fine and makes sense. However, I'm sure there is a lot of
> duplicated work between the users when adding other tools in. For
> example, there was a conversation the other day about adding in awk.
> Someone had already done this, so the best idea would be if I could
> pull in that definition and enable it with minimum effort. I have
> already added tools (exonerate, restriction mapper, etc, etc) that may
> be of use to other people. Not sure the best way to go about this,
> but if my understanding of mercurial is right, we can simply offer
> another repo for people to pull changes from.
This is something we're very interested in facilitating. For the long term,
we're hoping to provide a structured / wiki environment for people to share
tools and suites of tools, as well as providing more support in the
application for adding self-contained tool suites to a Galaxy instance,
injecting local configuration into tools and tool suites, et cetera.
However, we'd also be very happy to see the mailing list used for this at
the moment, and might even be able to open up a section of the wiki for
users to list the tools they are making available.
Can we send attachments to the mailing list? I would have thought the
easiest way would be to give some trac permissions (ticket create,
wiki edit) to list members. It's easier to work with than a mailing
list. I would also prefer filing bugs on trac than mailing them to a
list.
All in all, why not allow others to use your issue tracking and wiki?
Requires little effort from you except handing out accounts.
cheers,
James