Difference between revisions of "Telecon (2019-10-02)"
From Earth Science Information Partners (ESIP)
| Line 23: | Line 23: | ||
Create a twitter account for the IMCR. While a hash tag ''#IMcodeRegistry'' already exists, a Twitter account will help distance this resource from EDI and provide a feed of IMCR specific information the community can subscribe to. | Create a twitter account for the IMCR. While a hash tag ''#IMcodeRegistry'' already exists, a Twitter account will help distance this resource from EDI and provide a feed of IMCR specific information the community can subscribe to. | ||
===Revisit USGS, NOAA, and EPA software packages=== | ===Revisit USGS, NOAA, and EPA software packages=== | ||
| + | Lots of great software developed by these agencies. We should harvest what falls into the IMCR scope. | ||
Revision as of 15:27, October 2, 2019
Return to Archive
Attendees
Agenda & Notes
Agenda notes are italicized.
Revisit action item status from August meeting
http://wiki.esipfed.org/index.php/Telecon_(2019-08-07)
More integration
How can IMCR integrate with these resources?
Action items & Notes
More integration
- DataONE - A few of these have been added to the IMCR, but most of them are higher level than the package/library level (and lower) scope IMCR currently emphasizes.
- Tools, tools, tools -
Basic guidelines for new contributors
Draft a brief set of guidelines for new contributors focused on the scope of what IMCR accepts. Create a GitHub.io "Contribute" page linking to the website home page.
Twitter account for IMCR
Create a twitter account for the IMCR. While a hash tag #IMcodeRegistry already exists, a Twitter account will help distance this resource from EDI and provide a feed of IMCR specific information the community can subscribe to.
Revisit USGS, NOAA, and EPA software packages
Lots of great software developed by these agencies. We should harvest what falls into the IMCR scope.
