Skip to content

Instantly share code, notes, and snippets.

@brianzelip
Last active August 28, 2017 19:40
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 brianzelip/34c7ae7fae90122c45d624fb20aa670b to your computer and use it in GitHub Desktop.
Save brianzelip/34c7ae7fae90122c45d624fb20aa670b to your computer and use it in GitHub Desktop.
Marketing checklist for NCBI hackathons

NCBI hackathon product checklist

In order to maintain the online list of products created at NCBI hackathons, each shipped product's repo should include the following:

  • Title (required) - the proper display title for the product, with no unnecessary underscores/hyphens/lack of whitespace/etc., e.g., "NCBI Computational Cookbook", not "NCBIComputationalCookbook" or "NCBI_Computational_Cookbook"; achieve this via one of two methods:
    1. the repo name itself, ONLY IF it is the string of the ideal product name for display purposes, or,
    2. an issue titled title, with a label titled metadata, and the body of which should contain only the human readable title string for display purposes; see NCBI-Hackathons/ncbi-hackathons.github.io#5
  • Description (required) - the proper display description for the product, with proper grammer/punctuation/capitalization/etc.; achieve this via one of two methods:
    1. the repo description as input on the repo's homepage, above the list of repo files itself, ONLY IF this is the string of the ideal product description for display purposes, or
    2. an issue titled description, with a label titled metadata, and the body of which should contain only the ideal product description for display purposes; see NCBI-Hackathons/PubRunner#2
  • MVP? (required) - if a minimum viable product has shipped, create an issue titled mvp, with a label titled metadata, and the body of which should be only the string true (this makes the repo listed on the NCBI-Hackathons website list of software products); eg, NCBI-Hackathons/ncbi-hackathons.github.io#6
  • Manuscript? (optional) - if a manuscript exists for the product, create an issue titled manuscript, with a label titled metadata, and the body of which should be only a string containing the URL to the manuscript; eg, NCBI-Hackathons/ncbi-hackathons.github.io#4

As long as the above three requirements are met, the repo will be included on the NCBI Hackathons list of hackathon products.

For details on how the above data is fetched and used, see https://able-viper.glitch.me/, and https://github.com/brianzelip/ncbi-hackathons/blob/master/test.html#L119.

For the design work in progress using this data, see https://github.com/brianzelip/ncbi-hackathons/.

Questions? Contact @brianzelip.

@DCGenomics
Copy link

I vote that we make a 'for attendees' section of the run an ncbi hackathons repo and put this there!

@brianzelip
Copy link
Author

Sounds good

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