Feature Overview (aka. Goal Summary)  

Improve the new version, v2, of oc-mirror tool, based on feedback from the field. 

NAPS team is planning to have hack-a-thon on oc-mirror v2 to help improve the tool and documentation.

Goals (aka. expected user outcomes)

• Address the bugs raised during the hackathon. Ideally in 4.21 timeframe
• Address gaps in documentation resulted from the hackathon 
• Review and consider the RFEs raised from the hackathon

Background

According to the feedback from the field, in particular NAPS, with the release of oc-mirror v2 there are some gaps to be addressed in the tool from both functionality and documentation point of view. This hackathon comes to help the field to learn the new version of the tool and to provide direct feedback to the team on where the improvements need to be made.

https://docs.google.com/document/d/16ADTm829atCwwmeN6tjKKYc97UNkfzfAxotgqerkN9A/edit?tab=t.0#heading=h.66y4kqbj468a 

Requirements (aka. Acceptance Criteria):

• Ideally, ensure that the code used for hackathon is 4.20
• Review the issues reported to OCPBUGS and RFE projects for oc-mirror component with the label naps-hackathon
• Prioritize the bugs in 4.21 work
• Work with documentation to ensure all the feedback is included in 4.21
• Consider where the RFEs fit in the roadmap. Are those really RFEs or incorrect use of the product?

Documentation Considerations

• oc-mirror v2 documentation will be updated as a result of this Jira