CBIIT Open Source Development Initiative,

Community Projects, and Community Code Resource Directory

March 14, 2012

– OSDI– Community Projects– Community Code Resource Directory– Review

2

Agenda

– Definition: • CBIIT initiative which facilitates and directs the transition of existing

CBIIT development projects to public forums and code repositories

– Purpose:• Better facilitate the acceptance and incorporation of code from the

community into existing projects• Allow the future direction of projects to be defined and managed by

the community

– Submit a project• N/A

3

Open Source Development Initiative (OSDI)

– Definition: • CBIIT initiative which seeks out and funds community members that

identify a bona fide need within the cancer community and show the means to fulfill that need

– Purpose:• Identify and fill capability gaps within the cancer community that are

not currently being address by existing CBIIT projects

– Submit a project:• Contact your workspace facilitator for more information:

Imaging: Angela Nicholas - nicholasac@nih.gov

Clinical Trials Management Systems: Ken Wiley - ken.wiley@nih.gov

Integrated Cancer Research: Mervi Heiskanen - heiskame@mail.nih.gov

Tissue Banks and Pathology Tools: Lynn Martin - martinlp@mail.nih.gov

Architecture: Reechik Chatterjee – chatterjee_reechik@bah.com

Vocabularies and Common Data Elements: Brian Davis davisbp@nih.gov

4

Community Projects

Community Code Resource Directory

– Definition: • Webpage hosted at NCI which acts as a ‘phonebook’ for Open

Source projects available to support the cancer community

– Purpose:• Promote the exchange of community-developed digital capabilities to

support cancer research

– Submit a project:• Email: ‘opensource@nci.nih.gov’• Include in your request:

– The URL for where the code is located– A description of the license attached to

the code– Any publications / presentations of the

resource

5

Criteria for Addition to the Community Code Resource Directory Webpage

• Publically available source code– It is preferred, but not required, for the code to be in a code

versioning system like GitHub, SourceForge, or GoogleCode

• An open source license• Basic user instructions, installation instructions, and system

requirements• It is preferable but not required that the resource should

have been publicly presented at a scientific meeting or published in a journal and have some relation to the caBIG program.– Examples include but are not limited to : integration with or

extension of a caBIG tool; use of a caBIG data standard; analysis of a data set obtained through the caBIG infrastructure.   

Review – Which Initiative applies?

• I have a project in my lab that I feel could be used by the larger cancer community. Which initiative? – Community Code Resource Directory

• I have identified a gap within the cancer community that I need assistance (financial or other) to fulfill. Which initiative? – Community Projects

• I have a project in my lab that I feel could be used by the larger cancer community but needs some further development. Which initiative? – Community Code Resource Directory– Community Project

Questions

8