hendrik/lens
1
0
Fork 0
mirror of https://github.com/lensapp/lens.git synced 2025-05-20 05:10:56 +00:00
Code Issues Projects Releases Wiki Activity
ff6d3492de
lens/docs/contributing/maintainers.md
Roman ff6d3492de Rebasing branch before pushing to remote 
PageRegistration / PageMenuRegistration fixes & more simplification (#1386)

* PageRegistration & PageMenuRegistration fixes & more simplification, fix #1383

Signed-off-by: Roman <ixrock@gmail.com>

* clean up test, deprecate page.routePath

Signed-off-by: Roman <ixrock@gmail.com>

* fix: proper `isActive` state matching for page-menu-target to page considering current document location

Signed-off-by: Roman <ixrock@gmail.com>

set "allowJs" to false in tsconfig (#1377)

- None of the .ts files include any of the .js files

- All .js files are either passed to electron-builder or used as config
  files for other programs.

Signed-off-by: Sebastian Malton <sebastian@malton.name>

cleanup main side of metrics route for readability (#988)

* cleanup main side of metrics route for readability

* split out ??= for headers

Signed-off-by: Sebastian Malton <sebastian@malton.name>

Release v4.0.0-beta.3 (#1395)

Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>

Removed Advanced Topics bullet from Extension Development > Overview. Reworked content in Extension Development > Extension Capabilities, Extension Development > Testing and Publishing, and Contributing sections. Improved consistency throughout docs.

Signed-off-by: Paul Williams <pawilliams@mirantis.com>
2020-11-16 16:15:55 -08:00

1003 B
Raw Blame History

Maintainers

We are looking for community maintainers for the Lens project. Maintainers will be added to a special team with write permissions. These permissions consist of opening, closing, tagging, and editing issues and pull requests, as well as creating and deleting non-protected branches.

The responsibilities of a community maintainer are listed below.

Issues Triage

  • Labeling Issues: Label issues accordingly.
  • Finding Duplicates: Finding and closing duplicate issues.
  • Doing First Level Contact: Getting more information on the issues (like version number or asking for clarification) if needed.
  • Closing Irrelevant Issues: Closing issues that are determined irrelevant, no longer needed, not relevant to the project and/or don't follow the issues guidelines.

Help with Contributions

  • Help Manage Pull Requests: Help the author of the pull request with any problems.
  • Contributing: Create pull requests to help maintain and drive the project forward.