We need your help!
There are a handful of outstanding bug fixes and minor enhancements that we would really like to include in the upcoming 2018.4 release (slated for the last week of April).
If you are interested, here is a curated list of some of the issues that we would love to get some help with (for the sake of brevity, only links to the issues are listed here, please visit a link to learn more about the specific task):
Bug fixes
- https://github.com/qiime2/q2-types/issues/165
- https://github.com/qiime2/q2-quality-filter/issues/46 (closed)
- https://github.com/qiime2/q2-diversity/issues/176
- https://github.com/qiime2/q2-taxa/issues/95
- https://github.com/qiime2/q2-vsearch/issues/24
- https://github.com/qiime2/q2-feature-table/issues/166
- https://github.com/qiime2/q2-gneiss/issues/25
- https://github.com/qiime2/q2-cutadapt/issues/18
- https://github.com/qiime2/q2-demux/issues/79 (closed)
Enhancements
- https://github.com/qiime2/q2-types/issues/140
- https://github.com/qiime2/q2cli/issues/153
- https://github.com/qiime2/docs/issues/292 (closed)
Documentation/tutorials
These could also be written up as Community tutorials.
If you are interested in working on one or more of these issues, please reply to this post and let us know which one(s) you are interested in - that way other folks interested in helping know which issues are off the table. We are available to help point people in the right direction (we are still working on detailed developer docs, so your best bet for help right now is to post a question to Developer discussion).
To get a QIIME 2 development environment set up, please check out this draft document. We use GitHub to coordinate our development effort, if you have never worked with GitHub before, please check out their docs for info on how to do things (e.g. open a pull request).
For a good example of what this development process will look like, check out this great thread from @patthehat033. @patthehat033 is currently helping us out with adding “copy-to-clipboard” buttons to all the command blocks on the QIIME 2 docs (sweet!). The original GitHub issue can be seen here - we encouraged @patthehat033 to ask questions and get feedback on how to solve this issue on the forum, rather than on GitHub (the audience on the forum is much larger, we figured this would be a great way to share the development process with others). Once we were done discussing on the forum, @patthehat033 opened up a Pull Request on GitHub (it can be seen here) on the relevant repository (the same one that the issue was filed under). We are currently in the process of going back-and-forth on review and addressing those review comments, then once we are done, one of us on the core QIIME 2 team will merge @patthehat033’s new code, then, that code will be available in the next release of QIIME 2 (2018.4)! Thanks @patthehat033!
If you made it this far, thanks for sticking with it! Even if you aren’t available to contribute a code patch, we still thank you for your help - QIIME 2 really is a community effort, and we can’t do it without you!
Keep on QIIMEing! 