Hi Lari, Thanks for raising this up! May I know your thoughts on these questions?
~~~~~~~~~~~~ # 1 For pure doc PRs (only update .md files), do they run the same tests as code PRs? If so, can we set them to run only doc-related tests and skip code tests (since they're easily failed)? In this way, docs can be iterated faster. ~~~~~~~~~~~~ # 2 Does it make sense to add instructions for tests to the Pulsar Contribution Guide? For example, * For users: - How to resolve test issues (common test failure reasons and solutions) - Who can ask for help if users are blocked and can not resolve problems themselves - How to report test bugs * For developers: - How do tests work? (mechanism, Apache rules, etc) - How can I add/update tests? (quotas [1], limitations, notes, etc) ~~~~~~~~~~~~ [1] https://github.com/apache/pulsar/issues/16439#issuecomment-1182832309 ~~~~~~~~~~~~ Thank you! On Thu, Sep 1, 2022 at 4:11 PM Lari Hotari <lhot...@apache.org> wrote: > Hi, > > I think that we would need to improve the experience for contributors. > It's currently a big challenge to get a PR to the state where tests pass, > mainly because of the large amount of flaky tests and frequent congestions > in Pulsar CI. We don't tell this to the contributors in the PR template [1] > or the contributors guide [2] and finding this out without anyone > explaining could be a frustrating experience. > > Let's improve our contributor experience. "The hard part isn't solving the > problems, it's identifying the right problems to solve." [3] > > Would someone like to share their Pulsar contribution experience and what > you think that needs improvement? What was painful? > > -Lari > > [1] > https://raw.githubusercontent.com/apache/pulsar/master/.github/PULL_REQUEST_TEMPLATE.md > [2] https://pulsar.apache.org/contributing/ > [3] https://www.youtube.com/watch?v=qqaOpSJKdWc , > https://leanpub.com/ideaflow . Janelle Arty Starr: "Idea Flow: How to > Measure the PAIN in Software Development" >
