Marine Metadata project transitions from Google Code

While Google Code project is put to bed, MMI moves forward

Today, Google reported that they are cancelling the Google Code project hosting repository. This brings no worries for MMI; we recently migrated from Google Code to our GitHub repository, thanks to our sharp Technical Lead. And Google put some effort into fixing a bug we reported, so we can still access our old repositories on Google Code if needed.

Given the news, this seems like a good opportunity to consider what makes sites last in the Internet era. Every now and then we at MMI hear someone say "the MMI project is ending." This is always surprising (and vexing) for us to hear, as MMI remains the largest collection of metadata resources in the earth science community, with active operational support by TAMU-Corpus Christi, technical and project leadership, and members of its international Steering Committee. What lets MMI remain active and respected, despite periods of limited funding, while projects like Google Code are retired? 

For sure Google had the resources to keep the Google Code repository around as long as they wanted, and goodness knows the site still had plenty of users. But several factors, including abusive activity on the site and the success of other repositories, made them decide to end support. And Google's for-profit status may have been another factor, of course.

So far MMI has managed to block the occasional abuse. And we still surpass any other resources as a source of earth science metadata references. We may be overtaken someday—we just added many more references describing metadata standard repositories and guidance, so you can compare for yourself. (Let us know of any we've missed, please.)  But MMI's big head start, and commitment from its active supporters, leads, and users, have kept us a preferred community resource.

So we're talking to our co-communities, in EarthCube, ESIP Federation, Research Data Alliance, and elsewhere, to see how we can collaborate for the community's benefit. The needs of our organizations' users are not identical, and so neither is our content, but we sill need to pursue how to exchange and expose our resources—ideally while using best practices for open data access!

And if someday we decide that the best way to ensure our knowledge gets to you is to entrust it to another repository that can take even better care of it than we can, we promise that the community's efforts and contributions supporting MMI will never just "come to an end." They will be leveraged and used as the basis of even better products and services down the road. But we hope that day is long in the future.

Thanks for your support,

The MMI Team