QIIME 2 Weekly Developer Meeting: 2017.05.12

Developer Discussion
1

This is the thread for the weekly developer discussion meeting on 2017.05.12

Meeting date/time: 2017.05.12, 8pm-9pm UTC +0000.

Note: Meeting times are reported in UTC. Therefore, your local meeting time may shift depending on your timezone’s observance of daylight savings time.

Planned Agenda

Status Updates (1-2 min per person)

  • Caporaso Lab
  • Other attendees

Guided discussion (remainder of scheduled meeting time)

  • This list to be updated prior to the meeting to reflect the questions/discussion points proposed in this forum thread

To help us make the best use of everyone’s time please post any discussion topics to this thread before the developer meeting. This will help us identify and prepare for any questions/topics ahead of the call. Topics or questions of discussion are open to anyone, developers or users, but we ask that these discussion points be limited to thematic QIIME 2 questions (e.g. feature proposal, plugin idea, etc.) — we will not be able to provide technical support during these calls.

The developer meeting will be recorded and posted to YouTube, we will update this post with the streaming video link shortly before the meeting.

YouTube Link: https://www.youtube.com/watch?v=K1w-URHzKqY

If there are no discussion topics posted by 2017.05.11, 11pm UTC +0000, we will announce a meeting cancellation and share our status updates on this thread.

2

I would like to discuss q2-feature-classifier. I filed an issue here that I think is essential to address for the next release, and @Nicholas_Bokulich mentioned that we might want to (at least temporarily) use classify-blast or classify-vsearch in the moving pictures tutorial instead of classify-sklearn, as we have a better understanding of the performance of the former two methods than the latter at the moment.

1 Like
3

I’d like to discuss how we’re going to communicate our (new) internal Scrum process to the larger community (e.g. plugin developers not in the Caporaso lab) so that it’s clear what we’re working on in the lab, what we expect to be included in a release, and what we need help with.

2 Likes