How to deal with package pinning service failing to pin package manifest or assets?

[davesque]

Note: I'm not sure if this is the right repo in which to record this thought. Let's move this issue ticket once we figure that out.

What's wrong?

It seems possible that our pinning service, which will be listening for registry events and is supposed to pin package manifests and assets, might be down or not able to pin resources for some reason. In the event that the service misses the opportunity to pin a required resource, the package author would want or need to re-publish the package and associated resources.

How can we address this?

We need to make sure that authors have a way to rectify this kind of situation or have a way of telling if their package was successfully published and pinned. Maybe some features such as the following would be useful:

• The service should have some kind of view that shows if a package is fully pinned.
• Perhaps the registry API should include some kind of contact information for package owners? This could allow registry supervisor services such as ours to notify authors if any issues come up with their packages.