Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-242

Structure COO code so it can be splitted among responsible teams

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 1.2.0 RC
    • None
    • None
    • Structure COO code so it can be splitted among responsible teams
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 0% To Do, 100% In Progress, 0% Done
    • 75% (Medium)
    • 5

      Context

      In order have a clear ownership over the COO components, the code should be organized in a way that each responsible team can be assigned for reviews and a component clearly states which team is owner.

      Outcome:

      • Each component is owned by a team.
      • Each component should have a Jira component.
      • Each team should have a OWNERS_ALIASES so that subdirectories can be assigned to them via an OWNERS file.

          1.
          		 Organize COO components in subdirectories Sub-task To Do Undefined Gabriel Bernal
          2.
          		 Create a OWNERS_ALIASES file and OWNERS file per component subfolder Sub-task To Do Undefined Gabriel Bernal

              gbernal@redhat.com Gabriel Bernal
              gbernal@redhat.com Gabriel Bernal
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: