Skip to content

Instantly share code, notes, and snippets.

@gregcaporaso
Created October 15, 2012 21:53
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gregcaporaso/3895804 to your computer and use it in GitHub Desktop.
Save gregcaporaso/3895804 to your computer and use it in GitHub Desktop.
code sprint notes

some other information.

QIIME code sprint (15-16 October 2012)

15 October goals

Introduction to GitHub

  • why we're switching, resources, and best practices
  • brach/merge: qp-factor repository
  • pull requests: Greg's IPython pull request; Joey's biom-format pull request
  • close the SF repository for commits
  • port the QIIME website to GitHub pages
  • create qiime-developers team with all qiime contributors
  • define a strategy for developer support for GitHub as we're all learning the system

Introduction to Gist

QIIME issues list

  • update all tickets to contain milestone (where applicable) and owner
  • integrate feature requests and bug report from Sourceforge tracking system

Discuss plans for 16 October

  • Introduction to the qiime_test_data repository
  • /Users/caporaso/Dropbox/presentations/code_review_june2012_script_interface_testing/JGCaporaso.pptx
  • https://github.com/qiime/qiime_test_data
  • Introduction to the cmd-abstraction repository and goals
  • https://github.com/qiime/cmd-abstraction
  • Develop list of scripts which need test data entries
  • Google Doc URL:
  • Define a document describing how to define QIIME script usage examples and test data

16 October goals

Review all scripts without example data:

  • develop test data; commit to the qiime_test_data repo via a pull request
  • review script usage examples and define in the context of the associated test data; commit to the qiime repo via a pull request
  • fix/update script documentation as necessary

Time permitting, team-effort to improve the script auto-generation in the cmd-abstraction repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment