(Bugzilla -> Redmine)
|Line 49:||Line 49:|
== Enhancement list ==
== Enhancement list ==
Maintaining software involves incremental improvements for new format changes and removal of bugs. Please see our [http://
Maintaining software involves incremental improvements for new format changes and removal of bugs. Please see our [http://.open-bio.org/] page for a current list. Post to the developer mailing list if you are interested in tackling any open issues.
Revision as of 16:32, 10 October 2011
This page provides a central location to collect references to active projects. This is a good place to start if you are interested in contributing to Biopython and want to find larger projects in progress. For developers, use this to reference git branches or other projects which you will be working on for an extended period of time. Please keep it up to date as projects are finished and integrated into Biopython.
(GSOC 2010) Extending Bio.PDB
João Rodrigues's Summer of Code project aims to introduce several new features to the Bio.PDB structural biology module. It will include functions for adding polar hydrogens to structures, probing for SS bridges based on structural information and annotations, renumbering residues, coarse-graining a structure, etc. A more comprehensive layout of the project is available on this wiki, and the code is on a GitHub branch.
Population Genetics development
Giovanni and Tiago are working on expanding population genetics code in Biopython. See the PopGen development page for more details.
Brad is working on a Biopython GFF parser. Source code is available from git hub. Documentation is in progress at GFF Parsing. See blog posts on the initial implementation and MapReduce parallel version.
Bio.Phylo, a new, mostly-stable module for working with phylogenetic trees, was released with Biopython 1.54. Eric is currently working on NeXML support and bringing the Tree object methods to parity with Bio.Nexus. New features appear on GitHub branches first.
Nick Matzke developed a biogeography module for BioPython as a Google Summer of Code project through NESCent's Phyloinformatics Summer of Code 2009. See the project proposal at: Biogeographical Phylogenetics for BioPython. The mentors were Stephen Smith (primary), Brad Chapman, and David Kidd. The new module is documented on this wiki as BioGeography.
Several branches for working with RNA data have been made available by Kristian Rother. They can be used mainly for parsing RNA secondary structures  and working with Bio.Sequence objects that represent modified RNA nucleotides .
Open Enhancement Bugs
This Bugzilla Search will list all open enhancement bugs (any filed by core developers are fairly likely to be integrated, some are just wish list entries).
Branches on github.com
The Biopython network diagram at github.com will show all public branches of our repository on github, and will therefore let you see things that are being worked on.
Please add any ideas or proposals for new additions to Biopython. Bugs and enhancements for current code should be discussed though our bugzilla interface.
- Build a general tool to filter sequences containing ambiguous or low quality bases. Chris Fields from BioPerl is interested in coordinating the BioPerl/Biopython implementations. See these threads on the mailing lists for discussion: http://lists.open-bio.org/pipermail/biopython/2009-July/005355.html, http://lists.open-bio.org/pipermail/biopython/2009-July/005342.html
- Use SQLAlchemy, an object relational mapper, for BioSQL internals. This would add an additional external dependency to Biopython, but provides ready support for additional databases like SQLite. It also would provide a raw object interface to BioSQL databases when the SeqRecord-like interface is not sufficient. Brad and Kyle have some initial code for this.
- Revamp the GEO SOFT parser, drawing on the ideas used in Sean Davis' GEOquery parser in R/Bioconductor. See also this page.
Maintaining software involves incremental improvements for new format changes and removal of bugs. Please see our Issue Tracker page for a current list. Post to the developer mailing list if you are interested in tackling any open issues.