Build template for the sessions

[mbjones]

Build template for the sessions, ask for session length, products (Michael Stealey). This is likely to be a Wiki page, one per session, with an initial link to the bug tracker entry for that session. During the meta-session, we will decide how sessions get merged, combined, etc., and will need to record these changes in the templates. The template should include:

• Session title
• Session short name
• Session organizers
• Session participants
• Session github repository
• Session IRC channel
• Session Etherpad link or GDoc link
• Session proposal github ticket link
• ...

[mjstealey]

open-science-codefest-2014 session template

Basics

• Title
• Short name
• Organizers
• Github (or other) repository
• IRC channel
• Etherpad link or GDoc link
• Session proposal github ticket link

Defining Goals

• Write one paragraph description of overall session/project goal.
• optional: Define “base” and “reach” goals for this particular event.

Project Setup

• In README, document:
  • How to contact maintainers/project community
  • Basic project structure
  • How to set up the development environment
  • Preparing the computer/installing dependencies
  • Downloading the project
  • Viewing/testing changes
  • How to contribute changes
  • Verify that your documentation is clear for at least one of: Mac, Windows & Linux

Defining Tasks

• Define tasks for contributors to work on, including for each:
  • a brief summary
  • where to make changes
  • skills and tools needed
  • estimate of time the task will take
  • optional: priority of task
  • optional: dependencies
• Create a resource such as a Github issues / wiki for displaying and tracking the tasks

Follow Up

• Provide your contact information for participants interested in following up

Use of template

Each proposed session leader would complete the template to the best of their ability.

Any sessions that make use of a public repository such as Github should provide the link to their site for us to link to from the open-science-codefest Github repository.

Upon the collection of the templates we would be able to provide a brief description of the session/project with a link to their public site. For sessions that do not yet have a public site, a placeholder Github repository could be established to get them started. A readily identifiable shorthand notation for each session should be established for use within other portions of the agenda.

Above template is inspired by The Open Source Project Guide: Hackathon/Sprint version

Miscellany

Session short names should be easily identifiable and short enough to use in the full-day schedule grid. For example:

• [RHESSys] - Creating a RHESSys HydroShare Resource Typecoding
• [Pathogens] - Taming Pathogens
• [LiveOpenSci] - Improved Toolsets for Live Open Science
• [EcoNicheModel] - Building an Ecological Niche Modeling tool in R with a GUI that includes Ensemble models
• [CRAN4Data] - CRAN for Data
• [DRAT] - Run Distributed Release Audit Tool (DRAT) on all codefest generated code and report out on license statistic
• [DataCrawl] - Crawl and prepare NSF ACADIS, NASA AMD and NSIDC Arctic Data Explorer datasets with Apache Tika, Nutch, Solr, and OODT
• [MetaFeedback] - Adding user feedback to metadata records
• [Moneybee] - Moneybee: browser-based educational ecology game
• [PythonData1] - Create a native Python package for accessing DataONE
• [GameEco] - Gamification of ecological data collection (Real life Pokémon)
• [AutoMeta] - Automated metadata extraction
• [MachineLearn] - Machine learning on images: Combining passive microwave and optical data to estimate snow water equivalent
• [DataWebSrv] - Distributing Data via Web Services
• [CrwdSrc4EM] - Crowdsourcing for natural hazards and emergency management
• [Pangea] - Pangaea R client
• [MultiTool] - How to make multi-tool workflows reproducible
• [ProvenanceR] - Enable provenance capture in R
• [SptlAnalysis] - Spatial Analysis: filling the gaps in open source GIS tools
• [MetaProv&Un] - Metadata, provenance, and characterizing uncertainty
• [RData1] - Create a native R package for accessing DataONE
• [SOLRMeta] - Develop a Common SOLR Index Schema for Cataloging Science Metadata
• [RepoStruct] - Create guidelines for file based data repository structures
• [Zotero] - Build a generic RDFa importer for Zotero
• [BRSync] - Create a scalable, resilient data sharing network using BTSync
• [Synology] - Create a turnkey, open source data repository using Synology NAS Disk Station Manager
• [DataLifeCycle] - Open Science Software in Support of the Data Life Cycle
• [VizSciData] - Techniques and Technologies for Visualizing Scientific Data on the Web
• [MetaSemantics] - Techniques for adding semantics to your metadata

[mbjones]

Thanks, @mjstealey . I'm going to go ahead and start creating stubs for these for each of the sessions in the wiki so that they are available for others to use. So, I'll be moving your template over to the wiki as well for people to copy if new sessions arise.

[mjstealey]

You're welcome @mbjones . I've added the "how to use this template" blurb at the top of the https://github.com/NCEAS/open-science-codefest/wiki/OS-Codefest-Project-Template wiki content. It's format as a comment, so it doesn't appear when rendered for viewing, but does appear at the top when session representatives go to edit their content in Write mode. This is for copy/paste purposes when stubbing out the session wiki pages.

Once stubbed out the idea would be to link the session ShortName to the relevant wiki page. i.e. [[DataWebSrv]()] ---LandsYouOn--> Distributing Data via Web Services - wiki page

Also, the session ShortNames should be able to fit into the gridded view of the agenda once room assignments are made. We can pre-populate the link structures ahead of time at the top of the agenda as comments so they are easy to copy/paste on the fly during the sessions, but don't display in the standard view.

[mjstealey]

@mbjones - Stubbed out session wiki pages for existing 31 sessions by their short name, and linked back to the wiki Home page.

Added session schedule placeholder to top of each template for quick reference. Session schedule info to be added by open-science-codefest team once schedules are determined.

Re-ordered sessions alphabetically by short name on Home wiki page.

[mbjones]

Added links to all session tickets to their associated wikis. Need to add additional session wiki pages for any new sessions arising tomorrow.