Uploaded image for project: 'OpenShift Authentication'
  1. OpenShift Authentication
  2. AUTH-57

Auth Upstream involvement

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • Auth Upstream
    • False
    • False
    • To Do
    • Impediment
    • 100
    • 100% 100%
    • undefined

    Description

      Currently, in Auth team, we have not enough visibility in sig-auth upstream and in Kubernetes generally.

      We reserve time and effort to increase upstream involvement and become active in issue triaging, bug fixing, KEP reviews, and sig meetings.

      To accomplish goals we should reserve, on average, 30% of our working time for upstream involvement.

      Attachments

        Issue Links

          is cloned by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. AUTH-327 Auth Upstream Involvement

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • In Progress
          1.
          		 Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          		 QE Tracker Sub-task Closed Undefined Xingxing Xia
          3.
          		 TE Tracker Sub-task Closed Undefined Unassigned

          Activity

            People

              kostrows@redhat.com Krzysztof Ostrowski
              surbania Sergiusz Urbaniak (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: