Difference between revisions of "R Hackathon 1/Teleconferences"

From Phyloinformatics
Jump to: navigation, search
m (1st Teleconference 11/16/2007)
Line 1: Line 1:
== 1st Teleconference 11/16/2007 ==
== 1st Teleconference 11/16/2007 ==
Please note the [[R Hackathon 1/Planning Steps|planning steps page]] for addition information on specific items.
Please note the [[R Hackathon 1/Planning Steps|planning steps page]] for additional information on specific items.

Revision as of 18:33, 15 November 2007

1st Teleconference 11/16/2007

Please note the planning steps page for additional information on specific items.


Note for participants: all of the items following the first two are topics posed for discussion, rather than decisions already made. We encourage you to voice any and all feedback, including that pursuing the topic is not desirable (if that is what you feel).

  1. Welcome, review of purpose and general objectives (TJV)
  2. Outline of planning schedule ahead (HL)
  3. Introductions (everyone)
  4. Priorities and subgroups (SK, BCO) (5mins)
    • Goals summarized from participants' answers to the questions in the invitation - emphases, priority suggestions?
    • Emerging groups - organizing these on the wiki
  5. Preparations by participants (HL) (25mins)
    • Presentations
      • Lightning (< 5-10mins) talks - purpose(s), topics, and presenters
      • Needs for full-length (> 15min) talks?
      • Brainstorming current or future challenges - useful topics, presenters?
    • Bootcamps - purpose, needs, and presenters
    • Compiling package-specific information on the wiki - e.g., overview, relevant programming info, future goals
    • Tabulating metadata across packages (as started by Brian O'Meara) - methods, supported formats and analysis methods, visualization capabilities
    • Describing internal representation of data from test files in each package on the wiki
    • Reading list - suggestions (both for possible gaps and for recommended reading)
    • Other preparations we or others can facilitate or help with?
  6. Documentation & testing (SP, SK) (5mins)
    • R vignette writing - who has experience, and would be willing to help train the users? Examples to draw from?
    • Collection of data for testing and validation (such as tree files for testing)
  7. Source code repository (or repositories) (HL) (5mins)
    • Survey of current source code repository and versioning setup for participating packages
    • Assessing need for help with publicly accessible repository
    • Assessing need(s) for NESCent-run repository
    • Code branching needs
    • Other source code-related preparation needs
  8. IT logistics (HL)
    • Computers - will we need loaners?
    • Network access - will anyone need wired network?
    • File share needs
  9. Other homework? (5mins)
  10. Q & A (10mins)


Action Items: