Skip to content

Conversation

@gmfrasca
Copy link
Member

@gmfrasca gmfrasca commented Nov 6, 2025

No description provided.

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign james-jwu for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Signed-off-by: Giulio Frasca <gfrasca@redhat.com>
Signed-off-by: Giulio Frasca <gfrasca@redhat.com>
Copy link
Contributor

@hbelmiro hbelmiro left a comment

Choose a reason for hiding this comment

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

I left some comments.
Besides that, I think it will be easier for both contributors and maintainers if we keep the content of TESTING.md and ONBOARDING.md all in CONTRIBUTING.md.
We already have some duplicates between them.

Comment on lines 131 to 133
- **Role**: Strategic decisions and governance
- **Members**: 5-7 senior community members
- **Term**: 2 years, staggered
Copy link
Contributor

Choose a reason for hiding this comment

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

Comment on lines 32 to 51
*Get your development environment ready in just a few commands.*

```bash
# Fork and clone
git clone https://github.com/YOUR_USERNAME/pipeline-components.git
cd pipeline-components
git remote add upstream https://github.com/kubeflow/pipeline-components.git

# Set up environment
uv venv
source .venv/bin/activate
uv pip install -r requirements-dev.txt

# Install pre-commit hooks
pre-commit install

# Verify setup
./scripts/lint.sh
pytest
```
Copy link
Contributor

Choose a reason for hiding this comment

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

This duplicates the instructions from CONTRIBUTING.md. How about adding a link here?

Copy link
Member Author

@gmfrasca gmfrasca Nov 8, 2025

Choose a reason for hiding this comment

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

Good idea, but opposite: ONBOARDING.md is the developer setup guide, so this section should still live here, and CONTRIBUTING.md (guide on contribution patterns such as PR naming conventions, etc) should link to it

pytest
```

## Development Workflow
Copy link
Contributor

Choose a reason for hiding this comment

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

This also duplicates what we already have in CONTRIBUTING.md.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants