Confluence Retirement

In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is scheduled for retirement on January 27th, 2023. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact myusgs@usgs.gov. Thank you for your prompt attention to this matter.
Skip to end of metadata
Go to start of metadata

Folks (like Laura DeCicco) are re-working USGS documents on this (FY18 Q1) to have less language distinguishing "interpretable" software, more clear/concrete directions, etc.

There use to be some good guidance from the USGS Bureau Windows Tech Support site (https://bwtst.usgs.gov/open-source) but that seems to be gone.

  • No labels

1 Comment

  1. The December Open Source topic was around code inventories and metadata.

    Eric Martinez has been working on leverage open APIs to aggregate code.json files from individual USGS projects into a software inventory compatible with code.gov. Eric was unavailable at this months call. Alternatively, Cian Dawson volunteered to talk about the Water Mission Area activities and the Software IM.

     Important things to note:

    • The Software IM is currently under heavy revision by the Fundamental Science Practices Advisory Committee and any feedback on the items below are welcome.
      • How to index or inventory Software products. Which repositories? Do we need DOI's? DataCite does have a "software" class which would support software releases. Not clear how to handle frequent software versioning with DOI's
      • Classifying Software to set review and approval requirements. Provisional? Approved? Scientific? What about code written for external customers?
      • Metadata and other documentation for software. code.json, readme, etc.

    These are all topics of interest to the Software Development Cluster

    Additionally, there is a need to get more direction from DOI and the use and compliance with code.gov. We're continuing to follow up with DOI contacts to get guidance.