CDI Software Development Cluster

Meeting Notes

January 25, 2018

GSTalk - online collaboration : https://gstalk.usgs.gov/529776   meeting ID: 529776

Phone : passcode 529776

x4848 From the Reston National Center

703-648-4848 From other DOI locations. The Networx voice contract provides reduced long- distance charges.

1-855-547-8255 (855-5GS-TALK) From non-DOI locations including cell phones

Meeting Notes in Google Drive: Shared Google Drive Folder: https://drive.google.com/open?id=0B101UEJHbXWYUzlaNGl5U2JBMHc

Attendees : Michelle Guy, Eric Everman, Mary Bucknell

Updated location:

https://docs.google.com/document/d/1ygbbZ2Jmyq-_GZkHgLinh0AECzKTR8JAIl9dYwrZdrM/edit#

 

Focus

       Example software release  (slides) https://docs.google.com/presentation/d/1ymmHsy-CFRfwkoHLW2hW2Vnlb9YayAWVNoC03IwwUEY/edit?usp=sharing

       Michelle’s Shared Summary of USGS HPC/HTC Workshop January 2018

       Core sciences HPC (Yeti) https://www2.usgs.gov/core_science_systems/csas/arc/index.html

https://gitlab.cr.usgs.gov/hpc-arc/yeti-user-docs/wikis/home

       Advanced Computing Cooperative (Janice Gordon janicegordon@usgs.gov )

      Last working group meeting notes: https://docs.google.com/document/d/1xDB8ZTuXWJPBPAJQ3JDa8V1G5jwSQHxq4G_mpRljhN8/edit?usp=sharing

       USGS EDGE (Equipment and Development Grade Evaluation) program

       https://www2.usgs.gov/humancapital/hr/rgeg.html (Exhibit B-*)

       https://www2.usgs.gov/humancapital/hr/documents/rgeg-edgeexhibitb-3.pdf

       Open mic, what do you want to talk about?

       Future topics????

 

Discussion/Notes

 

 

 

 


 

No meeting in December 2017

November 30, 2017

Webex: https://usgs.webex.com/usgs/j.phpMTID=m6a36eb4a958149b5cbffa6b3584239bc

Phone: passcode 17803786

x4848 From the Reston National Center

703-648-4848 From other DOI locations. The Networx voice contract provides reduced long- distance charges.

1-855-547-8255 (855-5GS-TALK) From non-DOI locations including cell phones

 

Attendees:

Michelle Guy

Blake Draper

Rob Miller

Leslie Hsu

 

Goals to help guide how this group might collaborate and benefit from each other , (in order of priority and likelihood):

   + Share awareness of what is going on (software efforts, tool exploration, best practices, metadata standards)

   + Share lessons learned

   + Share configurations (software, tools, architectures, ...)

   + Share data, services, and/or maybe even code

 

Scope/Context (?)

       Practices (e.g. agile, mvp, …)

       Tools (e.g. github, jenkins, puppet, postgres, containers, …)

       Developed Software (e.g. mapping library, data distribution, time series data processing, time series data rendering, algorithms, web services, database schemas,

       Cloud integration

       Request for skills/developer time

 

Topics:

      Drupal

      Practices (e.g. version control, development workflow, reproducibility (CI\CD), containers (e.g. docker), …)

      Show your work (spread awareness, get feedback)

      Cloud

      USGS Software Release Process

 

 

CDI Software Development Cluster

Meeting Notes

 

September 28, 2017

Attendee’s: Michelle Guy ( mguy@usgs.gov );

Madison Langseth (mlangseth@usgs.gov)

Andy Stauffer

Matt Gabriel

Karen Blaney

Leslie Hsu

Eric Martinez ( emartinez@usgs.gov )

Blake Draper (bdraper@usgs.gov)

Scott Whitaker ( swhit@usgs.gov )

Robert Djurasaj ( rdjurasaj@usgs.gov )

Rob Miller ( rfmiller@usgs.gov )

Joseph Pantoga ( jpantoga@usgs.gov )

 

 

Webex: https://usgs.webex.com/join/mguy

 

Phone: passcode 17803786

x4848 From the Reston National Center

703-648-4848 From other DOI locations.

1-855-547-8255 (855-5GS-TALK) From non-DOI locations including cell phones

 

Meeting Notes in Google Docs: https://docs.google.com/document/d/10I5JsCDqyp-yxABbhgrFN_XBQ9ORmV_F5tsWy_GYmCU/edit

 

 

Topics:

      Welcome

      Our CDI page: https://my.usgs.gov/confluence/display/cdi/Software+Development+Cluster

      Software repository requirements and recommendations

      Disclaimer https://github.com/usgs/best-practices/blob/master/DISCLAIMER.md

      License https://github.com/usgs/best-practices/blob/master/LICENSE.md

      Metadata https://github.com/usgs/best-practices/blob/master/software/metadata.md

      Contributing https://github.com/usgs/best-practices/blob/master/CONTRIBUTING.md

      Code of conduct https://github.com/usgs/best-practices/blob/master/CODE_OF_CONDUCT.md

      Software releases and DOI’s https://github.com/usgs/best-practices/blob/dede3aa417b83e48a32ca3ad1a0eec5f23d3f483/doi.md

      What to point a DOI at? only at release on a “tag” version?

      Credit for original authors, especially as we work in public domain? We can request, encourage, we cannot enforce.

      Seek help from office of Science Quality and Integrity

      Provide a recommended citation for users of our software.

     Where should we put this in our repositories? Maybe in Readme, and/or disclaimer, or contributing.md or codeofconduct.md, include DOI of reviewed release, but what about of master/head (commit hash?), On release tags you can put comments, maybe include citations/DOI’s; Maybe DOI + commit hash or tag+commit hash

     Educate our community; Open source coffee talks with Cassandra Ladino on CDI; Research data alliance meeting talked about citations ( Software Source Code Interest Group , notes from meeting last week , Leslie is on their email list and will try to make the useful connections between groups); What else is community doing? Cut a tag and site the tag. Look at github themselves

     Do citations yourself

     Follow examples where relevant, if possible: https://guides.github.com/activities/citable-code/ (Digital Object Identifier process may vary for USGS model, but this may provide a template)

     Tracking downstream use of software products efficiently may also be worth considering. ( https://blog.datacite.org/software-citation-workflows/ , https://github.com/force11/force11-sciwg/issues/14 )

     There are many ways to get a DOI for software, there’s a Github best-practices page about this: ( https://github.com/usgs/best-practices/blob/master/doi.md )

     Varies per software project

      Should github.com/usgs/best-practices be moved to code.usgs.gov? Who has “authority” to answer?

      Code.usgs.gov (Eric Martinez)

      soon to migrate to CHS (cloud hosting services) which aside from small downtime will be seamless to users

      Unauthenticated users can only see “public” projects which will be publicly released projects

      Reviewed/Released projects with DOI’s will be sync’d from github.com/usgs (this does not include projects under “individual” accounts on github)

      Can do internal projects (AD authentication to USGS) - default

      Can do private projects with access list essentially

      Establishing a governing body - if you want to help email emartinez@usgs.gov

 

CDI Software Development Cluster

Meeting Notes

 

November 2, 2017

 

Webex: https://usgs.webex.com/join/mguy

 

Phone: passcode 17803786

x4848 From the Reston National Center

703-648-4848 From other DOI locations.

1-855-547-8255 (855-5GS-TALK) From non-DOI locations including cell phones

 

Meeting Notes in Google Docs: https://docs.google.com/document/d/10I5JsCDqyp-yxABbhgrFN_XBQ9ORmV_F5tsWy_GYmCU/edit

 


Attendees:

Michelle Guy

Blake Draper

Eric Martinez
Hans Vraga ( hvraga@usgs.gov )

Curt Tamanaha
Joseph Pantoga
Rob Miller

Brandon

Rhonda

Topics:

      Gitlab discussion (Eric) - https://code.usgs.gov/ghsc/hazdev/demo

      Slides - https://docs.google.com/a/doi.gov/presentation/d/1DffbwwJ8gjLO_f0JdvQULIeIIVc_I5brAVsLG1GxPIQ/edit?usp=sharing