Goal Summary

on an ongoing basis, the operator-framework team is called upon to help catalog/pipeline publishing teams address challenges. These can range from detailed Q&A, working with those teams to document their process in a way that avoids common pitfalls, or detailed evangelizing of pipeline principles (including but not limited to proofs of concept).

Load varies, and is not in regular intervals, but when it comes it represents a priority to our operator community and operator customer base, and can preempt/delay other work as a result.

This feature will attempt to make the time/type of engagement transparent.

Some time after the initiation of a consulting/support conversation, a team member will add/update a comment about the nature of the interaction, any action items, and an approximate duration spent.

If we create any epics/stories/tasks related to the operator-framework team effort, we will link them here.

If we need to constrain this feature to an OCP release then we can create additional features to contain them.