REQUEST: New membership for pchila #102
Description
GitHub Username
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)
- 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
- I have filed a PR to add myself as project maintainer 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
- feat(core): support imagePullPolicy for tasks(#127) keptn-contrib/job-executor-service#135
- refactor: reload prometheus configuration without deleting pods keptn-contrib/prometheus-service#252
- feat: only add prometheus alerts if remediation.yaml is defined for the stage keptn-contrib/prometheus-service#255
- ci: Use helm chart for release keptn-sandbox/keptn-service-template-go#92
- ci: Use helm charts for release keptn-contrib/argo-service#42
- fix: clean-up pods when deleting kubernetes jobs (#154) keptn-contrib/job-executor-service#155
- refactor: publish cloud automation extension keptn-sandbox/keptn-azure-devops-extension#65
- build: introduce repository init action keptn-sandbox/keptn-service-template-go#98
- Issues created
- Jmeter-service sends two sh.keptn.event.test.finished events when the endpoint is not reachable keptn#6778
- Provide a way to apply the correct rolebinding in prometheus namespace as part of helm install keptn-contrib/prometheus-service#261
- Wait for Keptn Event
deliverywaits on wrong event type keptn-sandbox/keptn-azure-devops-extension#69 - Evaluation failed because of missing dynatrace.conf makes WaitForKeptnEvent step pass keptn-sandbox/keptn-azure-devops-extension#68
- RFE: Support specifying git upstream for keptn/cloud automation keptn-sandbox/keptn-azure-devops-extension#67
- Do not use clusterAdmin role for argo-service keptn-contrib/argo-service#44
- Report prometheus service errors using appropriate events keptn-contrib/prometheus-service#256
- Use Prometheus client library to get SLI values keptn-contrib/prometheus-service#250
- Issues responded to
- SIG projects I am involved with
- N/A