[ https://issues.apache.org/jira/browse/LUCENE-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529735#comment-17529735 ]
Tomoko Uchida edited comment on LUCENE-10543 at 4/29/22 6:36 AM: ----------------------------------------------------------------- I opened [LUCENE-10545] and a PR for it. Can you please take a look? It does not aim to replace Jira with GitHub, but relaxes the requirement for Jira account/issue for contributors who are ready to start the conversation with a working PR. This would make some progress I think. For the future, we could consider replacing Jira with Github issue - I'm not against it and it may be technically possible, I think we'd need some additional discussion (also with ASF, maybe?) for the big transition. I have no personal opinion about the migration to GitHub - Jira works well for me so far and I'm already accustomed to concurrent use of Jira and GitHub. was (Author: tomoko uchida): I opened [LUCENE-10545] and a PR for it. Can you please take a look? > 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 > > 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: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org