Skip to content

Comments

Changes to non-org contribution policies and LFX clarifications #148

Open
npolshakova wants to merge 2 commits intokgateway-dev:mainfrom
npolshakova:community-guidelines-updates
Open

Changes to non-org contribution policies and LFX clarifications #148
npolshakova wants to merge 2 commits intokgateway-dev:mainfrom
npolshakova:community-guidelines-updates

Conversation

@npolshakova
Copy link
Contributor

@npolshakova npolshakova commented Feb 9, 2026

Planning to present these changes at the 2/10/2026 community meeting. These changes should help limit the number of AI-generated, low-quality PRs in kgateway-dev/kgateway and help maintainers have a more manageable load for reviews.

Feedback is welcome!

@npolshakova npolshakova requested a review from a team as a code owner February 9, 2026 16:51
@npolshakova npolshakova added the do-not-merge/work-in-progress The PR is still being worked on label Feb 9, 2026
Signed-off-by: npolshakova <nina.polshakova@solo.io>

Signed-off-by: npolshakova <nina.polshakova@solo.io>
@npolshakova npolshakova force-pushed the community-guidelines-updates branch from 867b792 to 665fb57 Compare February 10, 2026 17:35
@npolshakova npolshakova requested a review from jenshu February 10, 2026 17:35
@npolshakova npolshakova changed the title WIP: Changes to non-org contribution policies and LFX clarifications Changes to non-org contribution policies and LFX clarifications Feb 10, 2026
@npolshakova npolshakova removed the do-not-merge/work-in-progress The PR is still being worked on label Feb 10, 2026
Signed-off-by: npolshakova <nina.polshakova@solo.io>
Copy link
Contributor

@jenshu jenshu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with a few suggestions

for details on roles and how to apply.

3. **Not sure what to work on?**
A great place to start is issues labeled [`good first issue`](https://github.com/kgateway-dev/kgateway/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+First+Issue%22).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe also mention not to grab an issue that's already assigned to someone else (although if it's evident there has been no progress for a while, it would be ok to ask if they are still working on it)


### Guidelines for LFX Mentorship Program Candidates

kgateway has participated in the [Linux Foundation's LFX Mentorship Program](https://lfx.linuxfoundation.org/tools/mentorship) for several cycles.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
kgateway has participated in the [Linux Foundation's LFX Mentorship Program](https://lfx.linuxfoundation.org/tools/mentorship) for several cycles.
Kgateway has participated in the [Linux Foundation's LFX Mentorship Program](https://lfx.linuxfoundation.org/tools/mentorship) for several cycles.

nit / style guide: at start of sentence kgateway is capitalized


- We _strongly_ encourage you to focus on one high-quality PR for an issue you have been assigned instead of opening
multiple PRs simultaneously. This ensures fair review capacity across all applicants.
- Please follow the community guidelines for issue assignment. **Do not self-assign issues.** Many issues require
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would say this bullet point could even go under general guidelines somewhere above, maybe the Find something to work on section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants