Hi Paul,

Fixes or enhancements to individual tools might be a good place to start -
and you won't need to know as much about the Galaxy internals.

The Galaxy development team look after a lot of tools/wrappers, but of
course there are even more on the Tool Shed written and maintained by other
groups. Fixing a non-core Galaxy tool may not be quite what your lecturer
had in mind, so do check ;)


On Wednesday, February 6, 2013, Matthew Paul wrote:

> Dear Galaxy Project community,
>             I am working with a group of students at College of Charleston
> of South Carolina. Being interested in bioinformatics and software
> engineering, we chose to work on Galaxy for our open source class project.
> We are subscribed to the appropriate mailing list, have been accessing
> Trello and are becoming familiar with the Galaxy architecture. Our first
> assignment is to identify and fix a bug, but unfortunately the bugs
> reported seem to be going right over our heads.Where would be a good place
> to start, so that we may be able to contribute to your system
> (documentation, etc)? We are looking forward to your response.
> Thank you,
> Matt Paul
> ---------- Forwarded message ----------
> From: Matthew Paul <mrp...@g.cofc.edu <javascript:_e({}, 'cvml',
> 'mrp...@g.cofc.edu');>>
> Date: Tue, Feb 5, 2013 at 8:10 PM
> Subject: Desire to contribute
> To: galaxy-dev@lists.bx.psu.edu <javascript:_e({}, 'cvml',
> 'galaxy-dev@lists.bx.psu.edu');>
> Dear Galaxy Project community,
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:


Reply via email to