Tutorial Management

This repository has two main purposes:

• To provide a home for issues that are not specific to one of the other repositories.
• To provide documentation for the whole tutorial process. Where appropriate, detailed documentation will be provided in other locations, but linked here.

Structure and Organization

The following information is not part of the tutorial process per se, but discusses the various repositories (also Google Drive) that are part of the BSSw tutorial ecosystem, how they relate to each other, and how they are kept in sync.

• Github organization structure and management

High-Level Tutorial Workflow

1) Preparing a tutorial proposal 2) Post-acceptance finalization (Tasks that should be done soon after receiving notification of acceptance of the tutorial)

• Add a milestone for the event to master-labels-milestones.json and synchronize repositories
• Add an issue for the event to the bssw-tutorial/tutorial-management issue tracker
• Add an issue for the event to the ideas-productivity/project-management issue tracker
• If appropriate, add it to the upcoming events list on the main page and Events pages of https://ideas-productivity.org/
• Finalize agenda, preferably using the spreadsheet.
• Finalize plans for hands-on as part of the tutorial.
• Finalize staffing (presenters as well as helpers).
• Finalize plans for any specific enhancements or changes for the tutorial.
• Start building the event page in the tutorial website. 3) Preparation
• Follow up on venue requirmeents
  • Publicity information: bios, head shots, etc.
  • Consent forms
  • Travel/honorarium paperwork
  • Advance deadlines for delivery of presentations, recordings, etc.
• Update presentations
• Continue building the event page in the tutorial web site.
  • Transition to scheduled event once schedule is finalized
  • Fill out the event page as the information is available. 5) Publication of tutorial assets
• Upload presentations to FigShare and publish
• Create hands-on code repository for the event (as appropriate)
• Update artifacts on website 4) Delivering the tutorial (including advance recordings) 5) Post-delivery

Additional Documentation

Most of the information above has been presented from the workflow perspective. The process-level documentation may refer to (parts of) other documentation that is worth making visible as whole documents as well.

• bssw-tutorial.github.io website documentation: https://github.com/bssw-tutorial/bssw-tutorial.github.io/blob/main/README.md
• Using the Agenda Spreadsheet
• BSSw Tutorial Presentations