Update docs and add maciaszczykm@ to sig-ui-leads (#3269)

* Update contribution guidelines

* Add maciaszczykm to sig-ui-leads

* Add doc describing roles

.github/CONTRIBUTING.md

-Want to contribute? Great! First, read this page.
-
-### Before you contribute
-Before we can use your code, you must sign the
-[Cloud Native Computing Foundation Contributor License Agreement](https://github.com/kubernetes/community/blob/master/CLA.md)
-(CLA). The CLA is necessary mainly because you own the
-copyright to your changes, even after your contribution becomes part of our
-codebase, so we need your permission to use and distribute your code. We also
-need to be sure of various other things—for instance, that you'll tell us if you
-know that your code infringes on other people's patents. You don't have to sign
-the CLA until after you've submitted your code for review and a member has
-approved it, but you must do it before we can put your code into our codebase.
-Before you start working on a larger contribution, you should get in touch with
-us first through the issue tracker with your idea so that we can help out and
-possibly guide you. Coordinating up front makes it much easier to avoid
-frustration later on.
-
-### Code reviews
-All submissions, including submissions by project members, require review. We
-use [pull requests](https://help.github.com/articles/about-pull-requests/) for this purpose.
+# Contributing Guidelines
+All the contributions are done via GitHub. Please also read the Kubernetes contributors guide:
 
+https://github.com/kubernetes/community/blob/master/contributors/guide/README.md
+
+### Get familiar
+To learn more about the project, please read through the following documents:
+
+- https://github.com/kubernetes/dashboard/wiki
+- https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/
+
+### Sign the CLA
+Kubernetes projects require that you sign a Contributor License Agreement before we can accept your pull requests. Please see following document for more info:
+
+https://github.com/kubernetes/community/blob/master/CLA.md
+
+### Create a patch
+
+1. Submit an issue by describing your proposed change to the repo in question.
+2. The repo owners will respond to your issue rapidly.
+3. Fork the repo make your changes and test it.
+4. Submit a pull request.
+
+### Get through review process
+
+All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose.

CONTRIBUTING.md

-# Contributing Guidelines
-The Kubernetes Dashboard Project is a web-based UI for Kubernetes clusters. It allows users to manage the cluster as well as applications running in the cluster. All the contribution is done via GitHub. Please also read the contributors guide:
-https://github.com/kubernetes/community/blob/master/contributors/guide/README.md
-
-### Sign the CLA
-Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests. Please see https://github.com/kubernetes/community/blob/master/CLA.md for more info
-
-### Learn a bit about the Kubernetes Dashboard
-To learn more about the Kubernetes Dashboard project, please read through the user documentation:
-https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/
-
-### Contributing A Patch
-
-1. Submit an issue by describing your proposed change to the repo in question.
-2. The repo owners will respond to your issue rapidly.
-3. Fork the repo make your changes and test it.
-4. Submit a PR.
-
-### Code reviews
-
-All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose.
-
-

OWNERS_ALIASES

@@ -3,6 +3,7 @@ aliases:
   sig-ui-leads:
     - danielromlein
     - floreks
+    - maciaszczykm
   dashboard-maintainers:
     - konryd
     - ianlewis

ROLES.md

+# 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/danielromlein">@danielromlein</a>
+      <a href="https://github.com/floreks">@floreks</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>UX/UI lead</td>
+    <td>Takes care of application look and feel. Resolves UX/UI issues and decisions.</td>
+    <td><a href="https://github.com/danielromlein">@danielromlein</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/danielromlein">@danielromlein</a>
+      <a href="https://github.com/floreks">@floreks</a>
+      <a href="https://github.com/maciaszczykm">@maciaszczykm</a>
+    </td>
+  </tr>
+
+</table>
+
+### Rules
+
+- Members should remain active and responsive in their roles.

SECURITY_CONTACTS

@@ -13,3 +13,4 @@
 danielromlein
 floreks
 bryk
+maciaszczykm