openebs/community issues and pull requests

#167 - Refactor Maintainers file format and cross-reference CNCF CoC

Pull Request - State: closed - Opened by tiagolobocastro about 2 months ago - 2 comments

#166 - chore: fix typo in GOVERNANCE.md

Pull Request - State: closed - Opened by niladrih about 2 months ago

#164 - doc: remove duplicate maintainers' lists

Pull Request - State: closed - Opened by niladrih 2 months ago

#163 - chore: community updates

Pull Request - State: closed - Opened by tiagolobocastro 2 months ago

#161 - Complete a joint assessment from TAG Security

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#161 - Complete a joint assessment from TAG Security

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#160 - Complete a Governance Review from TAG Contributor Strategy

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#160 - Complete a Governance Review from TAG Contributor Strategy

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#159 - Complete a General Technical Review from TAG Storage

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#159 - Complete a General Technical Review from TAG Storage

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#158 - Additional information

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#158 - Additional information

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#157 - [Required] Clearly documented integrations and/or compatibility with other CNCF projects as well as non-CNCF projects.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#156 - [Required] TOC verification of adopters.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#155 - [Required] Used in appropriate capacity by at least 3 independent + indirect/direct adopters, (these are not required to be in the publicly documented list of adopters)

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#154 - [Required] Publicly documented list of adopters, which may indicate their adoption level (dev/trialing, prod, etc.)

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#154 - [Required] Publicly documented list of adopters, which may indicate their adoption level (dev/trialing, prod, etc.)

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#153 - [Required] Achieve the Open Source Security Foundation (OpenSSF) Best Practices passing badge.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#152 - [Required] Document Security Self-Assessment.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#152 - [Required] Document Security Self-Assessment.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#151 - [Required] Document assignment of security response roles and how reports are handled.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#151 - [Required] Document assignment of security response roles and how reports are handled.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#150 - [Required] Enforcing Access Control Rules to secure the code base against attacks (Example: two factor authentication enforcement, and/or use of ACL tools.)

Issue - State: open - Opened by avishnu 3 months ago - 1 comment
Labels: Incubation-partial-compliance

#149 - [Required] Clearly defined and discoverable process to report security issues.

Issue - State: open - Opened by avishnu 3 months ago - 2 comments
Labels: Incubation-no-compliance

#148 - [Required] Document the project's release process.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#147 - [Required] Document overview of project architecture and software design that demonstrates viable cloud native use cases, as part of the project's documentation. This can also be satisfied by completing a General Technical Review and capturing the output in the project's documentation.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#146 - [Required] Document and maintain a public roadmap or other forward looking planning document or tracking mechanism.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#145 - [Required] Document what the project does, and why it does it - including viable cloud native use cases. This can also be satisfied by completing a General Technical Review.

Issue - State: open - Opened by avishnu 3 months ago - 1 comment
Labels: Incubation-partial-compliance

#144 - [Required] Document project goals and objectives that illustrate the project’s differentiation in the Cloud Native landscape as well as outlines how this project fulfills an outstanding need and/or solves a problem differently. This can also be satisfied by completing a General Technical Review.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#143 - [Suggested] History of regular, quality releases.

Issue - State: closed - Opened by avishnu 3 months ago - 1 comment
Labels: Incubation-full-compliance

#142 - [Suggested] Roadmap change process is documented.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#141 - [Required] Demonstrate contributor activity and recruitment.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#140 - [Required] Documentation of how to contribute, with increasing detail as the project matures.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#139 - [Required] Up-to-date public meeting schedulers and/or integration with CNCF calendar.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#138 - [Required] List and document all project communication channels, including subprojects (mail list/slack/etc.). List any non-public communications channels and what their special purpose is.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#137 - [Required] Project must have, and document, at least one public communications channel for users and/or contributors.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#136 - [Required] Clearly defined and discoverable process to submit issues or changes.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#135 - [Suggested] Contributor ladder with multiple roles for contributors.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#135 - [Suggested] Contributor ladder with multiple roles for contributors.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#134 - [Required] All subprojects, if any, are listed.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#133 - [Required] CNCF Code of Conduct is cross-linked from other governance documents.

Issue - State: closed - Opened by avishnu 3 months ago - 1 comment
Labels: Incubation-no-compliance

#132 - [Required] Document agreement that project will adopt CNCF Code of Conduct.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#131 - [Required] Code and Doc ownership in Github and elsewhere matches documented governance roles.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#130 - [Required] A number of active maintainers which is appropriate to the size and scope of the project.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#129 - [Required] Document complete list of current maintainers, including names, contact information, domain of responsibility, and affiliation.

Issue - State: open - Opened by avishnu 3 months ago - 5 comments
Labels: Incubation-partial-compliance

#128 - [Suggested] If the project has subprojects: subproject leadership, contribution, maturity status documented, including add/remove process.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#128 - [Suggested] If the project has subprojects: subproject leadership, contribution, maturity status documented, including add/remove process.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#127 - [Suggested] Demonstrate usage of the maintainer lifecycle with outcomes, either through the addition or replacement of maintainers as project events have required.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#127 - [Suggested] Demonstrate usage of the maintainer lifecycle with outcomes, either through the addition or replacement of maintainers as project events have required.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#126 - [Suggested] Document a complete maintainer lifecycle process (including roles, onboarding, offboarding, and emeritus status).

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#126 - [Suggested] Document a complete maintainer lifecycle process (including roles, onboarding, offboarding, and emeritus status).

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#125 - [Suggested] Document how role, function-based members, or sub-teams are assigned, onboarded, and removed for specific teams (example: Security Response Committee).

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#125 - [Suggested] Document how role, function-based members, or sub-teams are assigned, onboarded, and removed for specific teams (example: Security Response Committee).

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#124 - [Suggested] Document how the project makes decisions on leadership, contribution acceptance, requests to the CNCF, and changes to governance or project goals.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#124 - [Suggested] Document how the project makes decisions on leadership, contribution acceptance, requests to the CNCF, and changes to governance or project goals.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#123 - [Suggested] Governance clearly documents vendor-neutrality of project direction.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#123 - [Suggested] Governance clearly documents vendor-neutrality of project direction.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#122 - [Suggested] Governance is up to date with actual project activities, including any meetings, elections, leadership, or approval processes.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#122 - [Suggested] Governance is up to date with actual project activities, including any meetings, elections, leadership, or approval processes.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#121 - [Suggested] Governance has continuously been iterated upon by the project as a result of their experience applying it, with the governance history demonstrating evolution of maturity alongside the project's maturity evolution.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-full-compliance

#120 - [Suggested] Clear and discoverable project governance documentation.

Issue - State: closed - Opened by avishnu 3 months ago - 1 comment
Labels: Incubation-full-compliance

#119 - (Post Incubation only) Book a meeting with CNCF staff to understand project benefits and event resources.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#119 - (Post Incubation only) Book a meeting with CNCF staff to understand project benefits and event resources.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#118 - Adoption Assertion

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#118 - Adoption Assertion

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#117 - Application Level Assertion

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#117 - Application Level Assertion

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#116 - Draft application for OpenEBS incubation

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#116 - Draft application for OpenEBS incubation

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#115 - [Required] Additional documentation as appropriate for project type, e.g.: installation documentation, end user documentation, reference implementation and/or code samples.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-partial-compliance

#114 - [Required] Due Diligence Review.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#113 - [Required] Review and acknowledgement of expectations for Sandbox projects and requirements for moving forward through the CNCF Maturity levels.

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#112 - [Required] All project metadata and resources are vendor-neutral.

Issue - State: open - Opened by avishnu 3 months ago - 1 comment
Labels: Incubation-full-compliance

#111 - [Required] TAG provides insight/recommendation of the project in the context of the landscape

Issue - State: open - Opened by avishnu 3 months ago
Labels: Incubation-no-compliance

#110 - [Required] Engage with the domain specific TAG(s) to increase awareness through a presentation or completing a General Technical Review.

Issue - State: open - Opened by avishnu 3 months ago - 2 comments
Labels: Incubation-no-compliance

GitHub / openebs/community issues and pull requests