dev meeting agendas

2014-03-12

1. Road to 1.0 update - MRC https://github.com/ged-lab/khmer/issues/321
2. Acceptance testing approach for major releases? Suggest running through protocols with test data. -CTB
3. Naming - MRC https://github.com/ged-lab/khmer/issues/320
4. Branding rules? - CTB/MRC
5. Command line as the API - MRC
6. AMI visibility issues for protocols - LS See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/building-shared-amis.html

#. Outline of must haves for next protocols v0.8.5 release - LS (See https://github.com/ged-lab/khmer-protocols/issues?direction=desc&labels=V+0.8.5&sort=created&state=open)

2014-02-12

1. Memory use bug. https://github.com/ged-lab/khmer/issues/266
2. iPlantCollaborative trip report
3. C++ namespaces (See https://github.com/ged-lab/khmer/pull/285 )
4. Special guest report from the wild by Josh Herr?
5. Input request from on issue assignments/pull request. (Goal: prevent two people from working on same issue)
6. v0.8 release steps. CTB to merge and publish update to ANGUS docs.
7. khmer-protocols v0.8.5 branch FOO

Notes:

1. Titus to work with user
2. MRC to pause on pipeline integration work for now
3. Luiz to merge PR

4. Josh sez: "How to use tools better within his pipeline?

   BioStar Academy: docs & tutorials Docs are poor. Too many scripts. Hard to figure out which ones to use. Old docs confuse users. What is the impact of poor docs? -> leads to people not using the tools.

5. Group agreed that PRs are requests for review, not a presentation of finished work. Issues can be use to indicate what one is working on.
6. CTB will merge. MRC will release v0.8 (this week?)
7. MRC will leave the khmer-protocols-v0.8.5 branch of khmer alone. CTB will make PR when he wants testing.