The community from keptn

REQUEST: Membership member for thisthat

GitHub Username

Membership level

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

REQUEST: Membership approver for @mowies

GitHub Username

@mowies

Membership level

Approver

Requirements (for approver, if applicable)

I am a reviewer of the codebase for at least 1 month
I am a reviewer for/or author of substantial PRs to the codebase, with the definition of substantial subject to the maintainer's discretion (e.g., refactors/adds new functionality rather than one-line changes).
I have spoken to 2 sponsors (maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

Grant @oleg-nenashev triage permissions in this repo

Hello, I would like to help with community management and contributor onboarding for Keptn. To do so, it would be nice to have Triage or Write permissions so that I could manage this repository and gradually extend it. In particular, I would like to introduce the community roadmap including topics like governance, community management, events, etc., etc. This roadmap would complement the technical roadmap for the project.

Stakeholders / sponsors

REQUEST: Membership member for RealAnna

GitHub Username

@RealAnna

Membership level

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

-https://github.com/keptn/keptn/issues?q=commenter%3ARealAnna+sort%3Aupdated-desc+
-https://github.com/keptn/keptn/pulls?q=author%3ARealAnna+sort%3Aupdated-desc+

REQUEST: Membership mantainer for RealAnna

GitHub Username

@RealAnna

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

maintainer

Requirements (for maintainer, if applicable)

I have a deep understanding of the technical goals and direction of the subproject
I have a deep understanding of the technical domain (specifically the language) of the subproject
I did sustain contributions to design and direction by doing all of:
- I am authoring and reviewing proposals
- I am initiating, contributing, and resolving discussions (e-mails, GitHub issues, meetings)
- I am identifying subtle or complex issues in the designs and implementation PRs
I am directly contributing to the subproject through implementation and / or review
I am aligning with the overall project goals, specifications, and design principles. I am bringing general questions and requests to the discussions as part of the specifications project.
I have spoken to 2 sponsors (maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored
- https://github.com/keptn/keptn/pulls?q=is%3Apr+author%3ARealAnna+sort%3Aupdated-desc+
Issues responded to
- https://github.com/keptn/keptn/issues?q=is%3Aissue+sort%3Aupdated-desc+involves%3ARealAnna

Community Ladder for Non-code contributors

Currently https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md is heavily focused on Code contributions. This is not correct, because other kinds of contributions are as valuable as Code ones, e.g. documentation, design, advocacy&outreach, reviews, etc. In addition to #82, I believe we should update the community chatter to allow onboarding non-code contributors and promoting them up to the official leading roles in the community.

Basically it implies splitting the "Maintainer" and "Community Leader" roles which are currently equivalents in the community

Maintainer sponsors

RFE: Shareable / Prepackaged Keptn Sequences

Proposal

An ability for Keptn users to package up their sequences as "best practices templates" that can then be reshared and applied to a Keptn instance.

This could encourage software / tool vendors to interact with Keptn as they

Imagine I decide that the following is a "best practice" sequence for releasing my application. In other words, as the vendor, I'm telling you this is the best "way" to deploy my appliction:

sequence:
  - name: deploy-appA
    tasks:
    - name: security
    - name: deploy
    - name: test
    - evaluate
    - approve

Workflow

I package this up and provide via a public repository
A user "applies" this sequence to Keptn
Keptn asks "which stage(s) should this sequence apply to?" (eg. dev
For each task, Keptn asks "which tool should respond to the dev.security.triggered task?"
A user picks from a presented set of options (perhaps pulled from ArtifactHub)?

In the end, the user has a well configured Keptn + tool integration chain which follows a vendors best practices.

Users can also re-share knowledge openly - minimising "reinventing the wheel"

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

RFE: Improve and separate membership process for Keptn Core and Keptn Integrations

Pain

The current Membership process is heavily focused on Keptn Core (github.com/keptn), but also mentions keptn-contrib and keptn-sandbox, e.g.:

Proposal

I propose to separate the process, such that we have

an extensive process, as currently given in Membership process for
- Keptn Core / github.com/keptn
- keptn-contrib - here the purpose is that some people need to have super-powers (not necessarily be the same people as for keptn core); it should be possible for people that contribute to multiple repos in keptn-contrib to become somebody with super-powers in keptn-contrib
a moderate process for github.com/keptn-contrib per repository (e.g., how to become a contributor of prometheus-service)
Some sort of process to become a manager for keptn-sandbox (e.g., accept new repositories/contributions) - please note that repositories in keptn-sandbox are always owned by an individual or by a group of people, and organization maintainers should only interfere in consultation with the repository owners

In short, I think that we need to have some groundrules:

Being a keptn core maintainer does NOT NECESSARILY make you a keptn-contrib maintainer (and vice versa)
Being a keptn-contrib organization maintainer could be a very organizational role that is hard to get to (e.g., only after multiple contributions and being a long-term member)
Being an organizational maintainer does not mean that you need to approve PRs, contribute code, etc... - this should be left to the repository owners (e.g., in keptn-contrib)

References

Sponsors

Please add yourself if you want to sponsor this

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

REQUEST: Membership member for TannerGilbert

GitHub Username

TannerGilbert

Membership level

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR (keptn/keptn#5899)

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

REQUEST: Membership mantainer for odubajDT

GitHub Username

odubajDT

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

maintainer

Requirements (for maintainer, if applicable)

I have deep understanding of the technical goals and direction of the subproject
I have deep understanding of the technical domain (specifically the language) of the subproject
I did sustained contributions to design and direction by doing all of:
- I am authoring and reviewing proposals
- I am initiating, contributing, and resolving discussions (e-mails, GitHub issues, meetings)
- I am identifying subtle or complex issues in designs and implementation PRs
I am directly contributing to the subproject through implementation and / or review
I am aligning with the overall project goals, specifications, and design principles. I am bringing general questions and requests to the discussions as part of the specifications project.
I have spoken to 2 sponsors (maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored
-- https://github.com/keptn/keptn/pulls?q=is%3Apr+author%3AodubajDT+sort%3Aupdated-desc+
Issues responded to
-- https://github.com/keptn/keptn/issues?q=is%3Aissue+sort%3Aupdated-desc+involves%3AodubajDT

Document Keptn Project Infrastructure

Proposal

Currently we do not have much documentation about the project infrastructure used by the Keptn project. We have a bunch of services beyond GitHub, e.g. DockerHub, NPM, Google Accounts and Channels, Twitter, LinkedIn, GCP, etc. It would be nice to have them documented so that Keptn contributors could...

Discover what services are offered by the Keptn community. E.g. I discovered NPM only after 2 months
Discover who has access to the account
Submit requests to get access or to have something implemented on the infrastructure
Contribute to project infrastructure

Suggested implementation

A new section in https://github.com/keptn/community, with README, infrastructure map and contributing guidelines
A new GitHub Issue template for infrastructure and permission management
Updated Keptn contributing guidelines that reference participating in the infrastructure

References

Slack conversation: https://keptn.slack.com/archives/CFH319TPE/p1641303177263400
Example: Jenkins Infrastructure sub-project: https://www.jenkins.io/projects/infrastructure

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

Add @oleg-nenashev to keptn-contrib

It would be great to be added to https://github.com/keptn-contrib as organization member so that my reviews could be requested and so that I could probably help with GitHub organization management.

GitHub Username

@oleg-nenashev

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR

Sponsors

Adopt LFX EasyCLA as alternative to DCO

DCO is not legally enforceable and it requires contributors to do force pushes to fix their commits. It does not help the user experience. I propose to migrate to the EasyCLA service that adds CLA with proper user experience.

To be reviewed at one of the Keptn meetings

Restore access to the keptn organization on NPM

There is a @keptn account on NPM which includes a few old projects, e.g. npmjs.com/package/@keptn/pitometer . It was created around 2 years ago, and Daniel Khan is the last one to upload a new package there. I assume Daniel is an owner though not 100% sure.

Now @thschue needs it to deploy a few packages for a Keptn Sandbox project. We should regain access

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

Keptn User Group meeting (around Kubecon in May 2022)

We would like to host a Keptn end user summit at Kubecon in Valencia. It is yet to be confirmed whether it will be in-person or remote one

REQUEST: New membership maintainer for @johannes-b (Johannes Bräuer)

Johannes Bräuer

@johannes-b (already maintainer)

This is for bookkeeping purposes.

Requirements

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

Bookkeeping purposes, no sponsor needed

List of contributions to the Keptn project

Johannes is a long term member of the Keptn project and has maintained Keptn from Day Zero.

REQUEST: New membership maintainer for @Kirdock (Klaus Strießnig)

Klaus Strießnig

@Kirdock (currently approver)

Requirements

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

Klaus is one of the core contributors to Keptn Bridge, and has touched several parts of the product already for more than 6 months.

90+ Commits: https://github.com/keptn/keptn/commits?author=Kirdock
47+ merged PRs: https://github.com/keptn/keptn/pulls?q=is%3Apr+author%3AKirdock+is%3Aclosed
24+ Issues created: https://github.com/keptn/keptn/issues/created_by/Kirdock

REQUEST: New membership for @warber @christian-kreuzberger-dtx @laneli @ermin-muratovic @bacherfl

Multi-request for Keptn core developer team

Please note, that these people are already maintainers. This issue is created for bookkeeping purposes.

Bernd Warmuth @warber
Christian Kreuzberger @christian-kreuzberger-dtx
Elisabeth Lang @laneli
Ermin Muratovic @ermin-muratovic
Florian Bacher @bacherfl

Requirements

We have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
We have enabled 2FA on my GitHub account. See https://github.com/settings/security
We have subscribed to the Keptn Slack channel
We are actively contributing to 1 or more Keptn subprojects
We have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

The aforementioned members have been actively contributing to the Keptn project (multiple repos) for several months, some of them even more than a year. They are also listed as top contributors: https://github.com/keptn/keptn/graphs/contributors

Introduce the community roadmap

It would be nice to create a GitHub project that provides a non-technical community roadmap

Acceptance criteria

Key community issues are created in the repositories
There is a GitHub project that allows navigating the roadmap: https://github.com/orgs/keptn/projects/1
Community roadmap is referenced in ROADMAP.md files where relevant
Community roadmap is reviewed at Keptn community meetings and signed off there
There is a public announcement

Keptn Incubation Status in the CNCF

In June the Keptn project applied for the incubation status in the CNCF. The application is pending, this is a counterpart ticket on the Keptn Community side

References

Pull request with the proposal: cncf/toc#670
Due diligence document: https://docs.google.com/document/d/14qFAc6kxhWX_JLMUKddgELcymaRw6jmhsq0OYxrHtc0/edit#

Definition

Responsibilities of a steering committee member should include

Own the overall charter, vision, and direction of the project
Promote broad adoption of the overall project
Provide guidance for the project maintainers
Approving and prioritizing new Keptn integrations
Archiving integrations or repositories of the Keptn organization and the ecosystem repositories
Manage membership of Keptn organization
Actively participate in the steering committee meetings

The process to build the steering committee can be aligned to other CNCF projects, such as the Steering Committee definition of Crossplane, or others.

Seats

Steering committee seats should be limited, granted only for a period of time, and spread across multiple organizations.

Election Process

Initial voting for steering committee members is should be open to all project maintainers. Nomination criteria have to be defined.

#113 (comment)

Create an artwork repository for Keptn artwork

It would be nice to have a general-purpose repository for Keptn artwork. We could also use https://github.com/keptn/community for this purpose if this is a preference by others

Examples of what we could use it for:

Storage of vector and PNG images, under the Creative Commons license
Guidelines for artwork contributors
References to external artwork

REQUEST: Membership member for vadasambar

GitHub Username

(at)vadasambar

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored
keptn/keptn#5290
keptn/keptn#5046
Issues responded to
keptn/keptn#5218
SIG projects I am involved with

Unconsistency between Keptn maintainer lists

The Keptn community uses https://github.com/keptn/keptn/blob/master/MAINTAINERS as a source of truth for maintainers. At the same time the CNCF uses https://github.com/cncf/foundation/blob/master/project-maintainers.csv#L506 which does not include recently added maintainers.

It would be great to fix the listing on the CNCF side

APAC friendly Community meetings

Proposal

It would be nice to have Community meetings in an APAC friendly time slot. Currently the meetings happen at 4:00 p.m. UTC, and it's not convenient for all contributors.

As discussed in slack, it would be nice to have regular meetings, for example at 8:00 or 9:00 a.m. UTC so that APAC and EMEA could participate

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

RFE: Adopt a Community analytics tool in the project

Proposal

It wpould be nice to adopt LFX Insights as a source of community metrics. There is a project here: https://insights.lfx.linuxfoundation.org/projects/cncf%2Fkeptn/dashboard , but currently it is disabled. We need to take ownership of it and re-enable

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

Transfer ownership of Keptn projects on LFX Mentorship to @oleg-nenashev

Proposal

There are 5 projects on https://crowdfunding.lfx.linuxfoundation.org/?cursor=&filter=Keptn#projects . I would love to get ownership of these accounts so that we could use them in the community programs

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

Create a new #keptn channel on the Kubernetes Slack

Proposal

Many end users are present in Kubernetes Slack workspace and do not want to join project-specific Slack workspace. It would be nice if we go directly to our end users and create a Slack channel on Kubernetes. Likely just #keptn for anything about Keptn, or #keptn-users and #keptn-dev for user and developer communities

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

🛣️ Community Roadmap

In addition to the project's technical roadmap, there is also roadmap for growing the Keptn user and developer community. It is a part of the main Keptn Roadmap. Use this filter to access only the community related items.

P.S: This is a placeholder issues.

REQUEST: Membership maintainer for thschue

I want to request maintainer status for Keptn. I have been contributing and working for keptn since 2020 and am currently involved in defining the GitOps approach for keptn and raising awareness for keptn in the community. Furthermore, I initially created some PoCs and reference implementations (remote execution plane, helm charts for services), which are an integral part of keptn today.

GitHub Username

thschue

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

maintainer

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR

Requirements (for maintainer, if applicable)

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored
Issues responded to
Other contributions to keptn
- Helped @didiladi to design the job-executor service
- Initial PoC for the Remote Execution Plane
- Different GitOps approaches (https://github.com/keptn-sandbox/keptn-git-toolbox, https://github.com/keptn-sandbox/keptn-gitops-operator)
- Initial author of keptn-on-k3s (https://github.com/keptn-sandbox/keptn-on-k3s)
SIG projects I am involved with
- CNCF: TAG App Delivery

Keptn Public Demo 2.0

Proposal

Keptn Public Demo was shut down on Dec 23. (https://keptn.public.demo.keptn.sh/). Apart from Log4J, there are other issues including the corrupted database and general security concerns about the instance until KEP-60 "RBAC for Keptn" is implemented (see keptn/enhancement-proposals#60 ). The instance will remain shut down over the Christmas break.

TODOs:

- Update the documentation and tutorials accordingly
- Start a new repository for a new Demo Keptn setup, fully managed -as-code via GitOps
- Rollout the new demo cluster
- Update the documentation

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

REQUEST: New membership approver for checkelmann

Christian Heckelmann

@checkelmann

Requirements

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

https://github.com/keptn/keptn/commits?author=checkelmann
https://github.com/keptn/keptn/pulls?q=is%3Apr+author%3Acheckelmann+is%3Aclosed
https://github.com/keptn/go-utils/commits?author=checkelmann
https://github.com/keptn-sandbox/gitlab-service
https://github.com/keptn-sandbox/keptn-report
https://github.com/keptn-sandbox/dynatrace-synthetic-service

Create a .github repository for org-wide configuration management

It would be nice to have a .github repository so that we could create content similar to https://github.com/keptn-sandbox/.github . I'd like to also use the repo for the following:

Modify the Keptn organization profile page
Add global CONTRIBUTING, CONDUCT and SECURITY metadata
TBD - move issue and pull request templates to the repo

Stakeholders

@johannes-b @thisthat

Improve non-code contributing guidelines

Currently the non-code contributions are rather a second class citizen in the documentation. It would be great to provide better contributing guidelines to those who want to contribute to other areas, e.g. documentation or artwork.

Scope

https://keptn.sh/community/contributing/ is updated to include non-code contributions. keptn/keptn.github.io#989
Documentation contributor guidelines are updated for the key repositories -
There is a default issue template for documentation available in the repositories
There is a repository for artwork contributions - #65

REQUEST: Membership member for oleg-nenashev

Submitting this application as aspiring Keptn community member. I do not have much code/issue contributions at the moment but I am working on it.

GitHub Username

@oleg-nenashev

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR

Requirements (for approver, if applicable)

I am a reviewer of the codebase for at least 1 month
I am a reviewer for/or author of substantial PRs to the codebase, with the definition of substantial subject to the maintainer's discretion (e.g., refactors/adds new functionality rather than one-line changes).
I have spoken to 2 sponsors (maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project approver and referenced this issue in the PR

Requirements (for maintainer, if applicable)

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored:
- GitHub org metadata, now in Sandbox for review: https://github.com/keptn-sandbox/.github
Issues responded to
- Issues created by me: https://github.com/search?q=is%3Aissue+org%3Akeptn+author%3Aoleg-nenashev
SIG projects I am involved with: CD SIG Events and CD Events (CDF Upstream specification, includes Keptn Events)

Keptn in Google Summer of Code 2022

It would be nice to have Keptn participating in Google Summer of Code 2022 so that we could have a few students working on new Keptn integrations or some core features that do not stand on the critical path of the Keptn roadmap. It is good for community bonding, and hopefully for new contributor onboarding too.

Project applications will start in mid-January

Potential project ideas

This list is based on the discussions with Keptn users and contributors. Please feel free to propose your ideas in the comments!

Better GitHub Integration in Keptn
- Use-cases: GitHub App Authentication, Reporting to Checks and Deployment API, GitHub Actions executor service
Integration service for k6
- Use-case: Performance testing as a part of Keptn Quality Gates, similar to the existing JMeter service
Jenkinsfile Executor Service for Keptn
- Executing Jenkins Pipelines as a service in Keptn. Based on Jenkinsfile Runner
- Potential mentor(s): Oleg Nenashev
Keptn Plugin for Backstage
- See keptn/integrations#19
- Potential mentor(s): Oleg Nenashev
GitOps for Keptn
- See keptn/enhancement-proposals#67
// Add your ideas in the comments!

References

https://summerofcode.withgoogle.com/

REQUEST: Maintainer status for @oleg-nenashev

I would like to request the maintainer status in Keptn. I have been an active contributor since July 2021, and currently I am helping with community management and Keptn growth. I do not contribute much to the Keptn production codebase but I focus on other areas: public roadmap, issue backlog, documentation and tutorials, Keptn adoption, contributor guidelines, community marketing, etc. All of that is an important part of the Keptn community!

My main use-cases for the maintainer status are:

GitHub org and repository administration so that I can help other maintainers with processing requests and improving the community
Access to the CNCF support portal o that I can handle CNCF interaction on my own for the ecosystem, e.g. community.cncf.io, Maintainer List, LFX Mentorship, LFX Insights, Slack, Core Infrastructure Initiative, etc.
Representing the Keptn project officially in the CNCF and other communities/organizations, e.g. for Keptn incubation or technical partnerships

GitHub Username

@oleg-nenashev

Membership level

maintainer

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR

Requirements (for approver, if applicable)

I am a reviewer of the codebase for at least 1 month
I am a reviewer for/or author of substantial PRs to the codebase, with the definition of substantial subject to the maintainer's discretion (e.g., refactors/adds new functionality rather than one-line changes).
I have spoken to 2 sponsors (maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project approver and referenced this issue in the PR

Requirements (for maintainer, if applicable)

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored
- Filed pull requests: https://github.com/search?q=org%3Akeptn+org%3Akeptn-sandbox+org%3Akeptn-integrations+is%3Apr+author%3Aoleg-nenashev&type=issues . Key authored ones:
- Reviewed PRs: https://github.com/search?q=org%3Akeptn+org%3Akeptn-sandbox+org%3Akeptn-integrations+is%3Apr+reviewed-by%3Aoleg-nenashev&type=issues
Issues responded to
- Keptn RFEs relevant to the community feedback and requests
- Keptn community roadmap on https://github.com/keptn/community/issues
- User support in the #help channel
SIG projects I am involved with
- CDF: Events SIG (Keptn Events is a part of it), Interoperability SIG, TOC, Governing Board
- CNCF: TAG App Delivery
- Many Jenkins SIGs

Keptn Community Day at Kubecon Valencia

Proposal

As discussed in the chats, it would be great to have a Keptn focused event during Kubecon in Valencia, May 2022. The idea is to make it a user-focused event so that we leverage the proximity of Kubecon and the potential Keptn Adopters there

Full-day or half-day event, preferably in person in Valencia.
Target audience: Current and potential Keptn adopters. Up to 50/100 visitors or whatever the local COVID rules / venue capacity are.
The event is community focused and vendor neutral. It would be great to have multiple company/information sponsors
The main goal is to discuss/present Keptn for users, including success stories, case studies, and the project roadmap
It would be nice to have a panel session with maintainers and user advisory board at this event
There could be a collocated Keptn intro workshop for newcomers. We did such for Jenkins summits, and it was a nice format
Of course some kind of Apero and networking is needed. Maybe a happy hour to celebrate Keptn incubation in the CNCF. See #81

References

Overview slidedeck: https://docs.google.com/presentation/d/1SzwJD_1f9ufy_hbHGJD8N6nSKtuj80ysI_Srmx-Or5M/edit?usp=sharing

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

REQUEST: New membership member for @arthurpitman

GitHub Username

@arthurpitman

Requirements

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

List of contributions to the Keptn project

REQUEST: Membership maintainer for thisthat

GitHub Username

@thisthat

Membership level

Membership level according to https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md

maintainer

Requirements (for maintainer, if applicable)

I have a deep understanding of the technical goals and direction of the subproject
I have a deep understanding of the technical domain (specifically the language) of the subproject
I did sustain contributions to design and direction by doing all of:
- I am authoring and reviewing proposals
- I am initiating, contributing, and resolving discussions (e-mails, GitHub issues, meetings)
- I am identifying subtle or complex issues in the designs and implementation PRs
I am directly contributing to the subproject through implementation and / or review
I am aligning with the overall project goals, specifications, and design principles. I am bringing general questions and requests to the discussions as part of the specifications project.
I have spoken to 2 sponsors (maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

Security process improvements

Proposal

Currently the security process is documented here. It borrows a lot from https://kubernetes.io/security/ but at the same time there are some issues in it:

How are the security issues tracked?
How does one join the "Security group"? Currently there 4 Keptn maintainers on the list, but there are no groups or Slack channels for coordination
What are the rules for announcing security vulnerabilities on https://keptn.sh/docs/news/vulnerability_bulletins/ ? Who is expected to prepare them and how do
What is our CNA, and how are CVEs are issued for the project?
Does the project follow best secure software supply chain practices?
Is the security process aligned with Core Infrastructure Initiative requirements (prerequisite for graduation)?

References

Keptn security process: https://github.com/keptn/keptn/blob/master/SECURITY.md
Keptn Security BBulletins: https://keptn.sh/docs/news/vulnerability_bulletins/
https://kubernetes.io/security/
CII Best Practices: https://www.coreinfrastructure.org/programs/best-practices-program/

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

Update Code of Conduct to the new version of Contributor Covernant

Currently the Keptn project uses Contributor Covenant 1.4. This is a version that has limited scope compared to Contributor Covenant 2,21 which focuses on the entire community instead of a project:

References

https://www.contributor-covenant.org/
Changelog with the 2.0 summary: https://github.com/EthicalSource/contributor_covenant/blob/release/changelog

REQUEST: Membership member for robertjahn

GitHub Username

robertjahn

Membership level

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application
I have filed a PR to add myself as project member and referenced this issue in the PR

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

PRs reviewed / authored
Issues responded to
SIG projects I am involved with

Keptn on community.cncf.io

Follow-up to the Zoom account transfer to the CNCF we initiated a couple of weeks ago. I discussed that with the foundation, and their recommendation is to regular switch to the community portal provided by the Linux Foundation as a part of the LFX toolchain. They plan to make this platform GA by February but it's already available for evaluation. We could try using it in Keptn.

This is a new platform based on Bevy that intends to aggregate community events under a single roof, including meetup.com alike portal and Zoom replacement. As with other Linux Foundation services, the final mileage may vary.

Currently it's still possible to request the zoom accounts but it will be a deprecated option soon. So I wonder whether we should give it a try and start building the proof of concept around the new platform. We don't have so many external participants at the moment, and from what I see in the documentation Bevy supports YouTube broadcasts.

Check list

- Request an org. A maintainer needs to submit the request
- Get initial content created: https://community.cncf.io/keptn-community/
- Configure Bevy. Get @oleg-nenashev and Giulia Di Pietro added to the team
- Update the website - keptn/keptn.github.io#990
- Update the Keptn Calendar
- Update the CNCF calendar
- Announce the new platform
- Run a test meetup on the platform

REQUEST: Maintainer membership for @grabnerandi @AloisReitbauer @danielkhan

Multi-request for Keptn maintainer team

Please note, that these people are already maintainers. This issue is created for bookkeeping purposes.

Andreas Grabner @grabnerandi
Alois Reitbauer @AloisReitbauer
Daniel Khan @danielkhan

Requirements

We have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
We have enabled 2FA on my GitHub account. See https://github.com/settings/security
We have subscribed to the Keptn Slack channel
We are actively contributing to 1 or more Keptn subprojects in terms of guiding the direction of the project
We have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization
I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

The aforementioned members have been actively contributing to the Keptn project for several months and are driving the direction of the project. Their contributions range from design decisions, technical guidance, roadmap, and even code contributions to the project.

YouTube Account access issues

Looks like we have an issue with our brand account. CC @jetzlstorfer

TODOs

Fix the issue
Ensure we do not have this issue again

Notes

REQUEST: Membership Member for mowies

GitHub Username

@mowies

Membership level

member

Requirements (for member)

I have reviewed the community membership guidelines (https://github.com/keptn/community/blob/master/COMMUNITY_MEMBERSHIP.md)
I have enabled 2FA on my GitHub account. See https://github.com/settings/security
I have subscribed to the Keptn Slack channel
I am actively contributing to 1 or more Keptn subprojects
I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
I have spoken to 2 sponsors (approvers or maintainers) ahead of this application, and they have agreed to sponsor my application

Sponsors

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the Keptn project

https://github.com/keptn/keptn/commits?author=mowies
https://github.com/keptn/keptn/pulls?q=is%3Apr+author%3Amowies+is%3Aclosed+
https://github.com/keptn/keptn/issues/created_by/mowies

Simplify tracking unanswered user requests in `#help`

Proposal

Currently it's hard to track what it answered and not in #help. It would be nice to add a bot that queries the status and provides some summaries to the participants

References

Sponsors

(at)sponsor-1
(at)sponsor-2

Checklist

The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
Each sponsor should reply to this issue with the comment "I support".

keptn / community Goto Github PK

community's People

Contributors

Stargazers

Watchers

Forkers

community's Issues

GitHub Username

Membership level

Requirements (for member)

Sponsors

List of contributions to the Keptn project

GitHub Username

Membership level

Requirements (for approver, if applicable)

Sponsors

List of contributions to the Keptn project

Stakeholders / sponsors

GitHub Username

Membership level

Requirements (for member)

Sponsors

List of contributions to the Keptn project

GitHub Username

Membership level

Requirements (for maintainer, if applicable)

Sponsors

List of contributions to the Keptn project

Maintainer sponsors

Proposal

Workflow

References

Sponsors

Checklist

Pain

Proposal

References

Sponsors

Checklist

GitHub Username

Membership level

Requirements (for member)

Sponsors

List of contributions to the Keptn project

GitHub Username

Membership level

Requirements (for maintainer, if applicable)

Sponsors

List of contributions to the Keptn project

Proposal

Suggested implementation

References

Sponsors

Checklist

GitHub Username

Membership level

Requirements (for member)

Sponsors

References

Sponsors

Checklist

Johannes Bräuer

Requirements

Sponsors

List of contributions to the Keptn project

Klaus Strießnig

Requirements

Sponsors

List of contributions to the Keptn project

Multi-request for Keptn core developer team

Requirements

Sponsors

List of contributions to the Keptn project

Acceptance criteria

References

Related stories

GitHub Username

Membership level

Requirements (for maintainer, if applicable)

Sponsors