# Roles within Kubernetes Dashboard community

This document describes the set of roles individuals may have within the Kubernetes Dashboard community.

<table>
  <tr>
    <td>Name</td>
    <td>Description</td>
    <td>People</td>
  </tr>
  
  <tr>
    <td>Owner</td>
    <td>Takes part in strategic discussions. Involves only when needed.</td>
    <td><a href="https://github.com/bryk">@bryk</a></td>
    </tr>
  
  <tr>
    <td>Administrator</td>
    <td>Takes care of repository settings, manages permissions and plugins.</td>
    <td><a href="https://github.com/floreks">@floreks</a></td>
  </tr>
  
  <tr>
    <td>Lead</td>
    <td>Responsible for design, plannings, roadmaps etc. Works on project recognition.</td>
    <td>
      <a href="https://github.com/floreks">@floreks</a>
      <a href="https://github.com/jeefy">@jeefy</a>
      <a href="https://github.com/maciaszczykm">@maciaszczykm</a>
    </td>
  </tr>
   
  <tr>
    <td>Tech lead</td>
    <td>Takes care of technical side of the project. Resolves technical issues and decisions.</td>
    <td>
      <a href="https://github.com/floreks">@floreks</a>
      <a href="https://github.com/maciaszczykm">@maciaszczykm</a>
    </td>
  </tr>
  
  <tr>
    <td>SIG-UI lead</td>
    <td>Leads weekly meetings with the community. Integrates new members into community.</td>
    <td>
      <a href="https://github.com/floreks">@floreks</a>
      <a href="https://github.com/jeefy">@jeefy</a>
      <a href="https://github.com/maciaszczykm">@maciaszczykm</a>
    </td>
  </tr>

</table>

### Rules

- Members should remain active and responsive in their roles.
