Hi Lari,

Thanks for launching this discussion. There's a lot to do to improve
contributor experience, esp for newcomers I think.
One of the pain points is obviously the CI flakyness and I believe we are
all aware of that.
Related to that, we have the pulsarbot to relaunch the tests that failed
but:
* when you're new to Pulsar, you don't even know it exists
* when you know it exists, you never (I never) remember what the command
is. So you try to find an issue somewhere that has it in its comments and
you copy/paste. But the comment has the wrong syntax and you copy/paste
"/pulsar-bot rerun-failure-checks" (notice the -). And you don't understand
why the CI isn't relaunched. You feel miserable and want to rage quit.
* the command only works when the workflow is

Some things that could be done:
* Describe the pulsarbot commands somewhere to make it visible and a ref to
copy/paste. In the README, but also in the PR template bc that's something
you read carefully on your first PR.
* Indicate that you can save replies in GitHub. Very nice tips I got from
Nicolo (thanks!).
* Have the pulsarbot comment that it received the command and will relaunch
the CI
* Accept /pulsar-bot command as it's a common typo.

Best regards.

Christophe

Le jeu. 1 sept. 2022 à 10:11, Lari Hotari <lhot...@apache.org> a écrit :

> 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"
>

Reply via email to