Quick question: preferred contribution workflow for community PRs?

[jlacour-git]

Hey Daniel!

Quick question about contribution workflow. I've submitted a handful of PRs over the past week (#727, #742, #762, #763, #780) and noticed the open PR count is growing across the board. Not a criticism at all! I get that reviewing community PRs takes real time, especially with the pace of development right now.

I just want to make sure I'm contributing in the way that's most useful to you. A few questions:

1. Are PRs the right channel? Or would you prefer issues with detailed proposals that you implement yourself?
2. Any preferences on PR size? Some of mine are tiny 2-line fixes, others are more substantial. Happy to adjust.
3. Is there a better time or cadence for submissions? I don't want to add noise during a big push like the 3.1 work.

I'm genuinely enjoying working with PAI and want to give back in whatever form actually helps. Just point me in the right direction!

[chrisglick]

Great question and timing @jlacour-git

I've been modifying PAI since 2.5 (which was what, 4 weeks ago? Daniel's release cadence is PAItastic!) to work on Windows, in parallel with @p4gs. After going through the time/tokens to port PAI to a different OS, we want to also contribute those improvements to this wonderful project. KAI (Danial's DA) replied to a few of the PRs, but it's been radio silence since. I too understand wanting to iterate on core algorithm/features as this is such a green field project and following your excitement is a core mission of this project.

Your 3 questions are the crux of it, and I hope to hear @danielmiessler thoughts too!

As for now, I'm going to keep building on my local PAI while waiting for a green-light on submitting more PR's.

[MarvinDontPanic]

+1 — been running PAI since v2.5 (now on v4.0.2) with a pretty heavy custom layer on top. We've submitted a few PRs too (#648, #668, #718, #750) and had the same experience: initial KAI feedback on one, silence on the rest.

Your three questions nail it. Even a quick "PRs welcome on X, hold off on Y" would go a long way.

Happy to help however's useful — we've solved a bunch of integration and upgrade challenges and would love to contribute back if there's a good channel for it.