[
https://issues.apache.org/jira/browse/LUCENE-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530339#comment-17530339
]
Robert Muir commented on LUCENE-10543:
--------------------------------------
IMO it just creates friction. having to sign-up for an account on anything is a
big hurdle IMO. Signing up for JIRA is something i haven't done in forever, so
I've got a screenshot of what it looks like. You have to solve CAPTCHA, etc:
!Screen_Shot_2022-04-30_at_01.15.00.png!
> Achieve contribution workflow perfection (with progress)
> --------------------------------------------------------
>
> Key: LUCENE-10543
> URL: https://issues.apache.org/jira/browse/LUCENE-10543
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
> Attachments: Screen_Shot_2022-04-30_at_01.15.00.png
>
>
> Inspired by Dawid's build issue which has worked out for us: LUCENE-9871
> He hasn't even linked 10% of the issues/subtasks involved in that work
> either, but we know.
> I think we need a similar approach for the contribution workflow. There has
> been some major improvements recently, a couple that come to mind:
> * Tomoko made a CONTRIBUTING.md file which github recognizes and is way
> better than the wiki stuff
> * Some hazards/error messages/mazes in the build process and so on have
> gotten fixed.
> But there is more to do in my opinion, here is 3 ideas:
> * Creating a PR still has a massive checklist template. But now this template
> links to CONTRIBUTING.md, so why include the other stuff/checklist? Isn't it
> enough to just link to CONTRIBUTING.md and fix that as needed?
> * Creating a PR still requires signing up for Apache JIRA and creating a JIRA
> issue. There is zero value to this additional process. We often end out with
> either JIRAs and/or PRs that have zero content, or maybe conflicting/outdated
> content. This is just an unnecessary dance, can we use github issues instead?
> * Haven't dug into the github actions or configs very deeply. Maybe there's
> simple stuff we can do such as give useful notifications if checks fail. Try
> to guide the user to run ./gradlew check and fix it. It sucks to have to
> review, look at logs, and manually add comments to do this stuff.
> So let's have an issue to improve this area.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
