[
https://issues.apache.org/jira/browse/HUDI-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430073#comment-17430073
]
Raymond Xu commented on HUDI-2575:
----------------------------------
from [~codope]
{quote}c) Apart from what you have already listed, may I also suggest a
[cc-bot|https://github.com/pytorch/pytorch/issues/24422] by which not just
PMC/committers but anyone in the community interested in following some story
gets tagged on the issue automatically.
PyTorch is a really big open source project. I found the following two posts a
good-read for maintaining such big projects in general.More on
principles/philosophy:
[https://soumith.ch/posts/2021/02/growing-opensource/]More on scaling
operationally: [http://blog.ezyang.com/2021/01/pytorch-open-source-process/]
{quote}
> [UMBRELLA] Revamp CI bot
> -------------------------
>
> Key: HUDI-2575
> URL: https://issues.apache.org/jira/browse/HUDI-2575
> Project: Apache Hudi
> Issue Type: New Feature
> Components: Testing
> Reporter: Raymond Xu
> Priority: Major
>
> Improvement ideas
> * it should periodically scan GH issues and auto close upon some condition
> (e.g. “block on user” and no response from last comment in 30 days)
> * it should help auto close or follow up on JIRAs upon some condition (yet
> to define)
> * PR test build is a pull model by periodic scanning PRs; better to use a
> push model to react to PR updates immediately like to trigger a build. Reduce
> a few min wait time
> * for every new commit, it should append a comment show new report
> “pending”; it should also update the same comment to show report results once
> build is done
> * a new commit or a force push should cancel previous build job and start a
> new job
> * users don’t need to use {{@hudi-bot run azure}}
> * it can also report back codecov reports once integrate with codecov in the
> mirror repo
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
