Need to curate registry

[ilsaloving]

SDK version

...

Use-cases

When trying to find providers, modules, etc, it is often necessary to wade through a large quantity of junk, including:

• Forks of other providers that have no changes, or changes that are not documented
• Providers that have zero documentation at all

A good example of this is when you search the providers for "docker". It is impossible to tell which are usable or reliable.

Besides being unable to find what you need, it also gives the impression that the registry is nothing more than a dumping ground for anything and everything, quality be damned. It also raises the concern that malware can be easily added to the registry since nobody seems to care what goes in there.

Attempted Solutions

• Manually examining the repos of each variant for newness, similarity, etc.

Proposal

• In the registry, include any fork details with a provider
• Providers must have unique names
• When searching for providers, the results list should have more details including age and fork status
• Providers with no documentation, or that are completely unchanged from the parent codebase, should not be permitted in the registry at all.
• Unregister providers that have not been maintained for X years
• Introduce automated quality and behavioural analysis checks on code being added to the registry
• Have a curator perform spotchecks on the registry for quality issues

References

[opslivia]

@ilsaloving, we really appreciate your feedback. Thank you for taking the time to write this request. Having it helps us advocate for a higher quality registry experience as we build out next year's roadmap. If you're up for it, I'd love for us to chat. You can throw a meeting on my calendar any time by using this link.