Details
-
Task
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Needs Assessment
Description
README link: [github](https://github.com/HewlettPackard/oneview-puppet/blob/master/README.md)
- Link to CI: [travis](https://travis-ci.org/HewlettPackard/oneview-puppet)
- Link to CHANGELOG: [changelog](https://github.com/HewlettPackard/oneview-puppet/blob/master/CHANGELOG.md)
Sorry if this is not filed in the correct place, I could only find that I was supposed to open this ticked here through the link (https://forge.puppet.com/approved).
I'm one of the main contributors to the hewlettpackard/oneview module, and it is actively developed by multiple engineers at HPE and integrated with our solution 'HPE Oneview'.
We've followed several best practices and are currently using rspec-puppet to unit test and integration test all the ruby code in the module, plus we have examples for its usage.
We're using SemVer and our metadata score has been at 5 for the past releases.
How could we request for the module to become Puppet Approved, or what is missing so that we can focus on achieving that eventually?
Best Regards,
Felipe Bulsoni.