Plan overall timeline

Tasks and Timeline

1. 2/20 - Make data accessible: Publish input, intermediate, and final data in a public shared repository (e.g., FigShare), and cite it in the article.
2. 3/6 - Ensure software is usable: Gather all the software used in the article, including data preparation codes, pre-processing software, visualization software, and any scripts used. Check that all software runs with input data and generates the results as expected.

MARCH 11-13, 2015: F2F MEETING: TRAINING AND DETAILED PLANNING

1. 3/20 - Sketch the overall workflow: Describe the data flow across software components. Define clearly for each piece of software used in the article what are the inputs and outputs and their data types.
2. 4/3 - Make software executable: Ensure that software can be run by others.
3. 4/17 - Software attribution: Document creators, authors, contributors of the software. Cite the software as appropriate in the paper.
4. 5/1 - Make software accessible: Publish software in a public repository (e.g., GitHub), use a license, and cite it in the article. Make it easy to track updates and new versions of the software.
5. 5/29 -
6. 5/15 - Document domain characteristics: Describe domain data and constraints that help others understand the software.
7. 5/29 - Preparing the article for publication: Documenting the methods section, the figures, and the references. Submitting the article to the journal.