Question About Contributing Features and Merge Process

[ssliman]

First, I want to thank you for the incredible work you've done.

I am interested in contributing a feature to the project. Before proceeding, I wanted to ask about your general approach to feature contributions:

1. How open is the project to new features, provided they align with the project's guidelines and overall roadmap?
2. If a pull request follows the contribution guidelines, includes relevant tests, and passes checks, how long does it typically take for the maintainers to review and potentially merge it?

I’d greatly appreciate any insights you can share to help me align my contributions with the project's needs and processes.

Thank you for your time.

[GoshaDo]

Hi, thanks for contributing back.

How open is the project to new features, provided they align with the project's guidelines and overall roadmap?
Everything is open to discussion; it would be great to hear what you have in mind.

If a pull request follows the contribution guidelines, includes relevant tests, and passes checks, how long does it typically take for the maintainers to review and potentially merge it?
I'd say a few days, depending on the holidays. :)

I have few thoughts with this project, but I want to gain some community validation of that :

1. Should we support another orechstetion tools such as Tekton ?
2. Should we mask the syntax of such tools with Piper syntax or to use the "native" ? It can us be much more lean.
3. Maybe to write a controller to piper, and move GitProvider to a CRD ? Not sure about that, but it can give a native controller ..
4. I am sure that we need to approve docs with examples, and explanations on git providers triggers..