This page captures all flow of information in the community, with hopes of directing members to the right places. Also documents, how/what Slack data is collected towards bookkeeping on the ASF infrastructure. 




This outlines a process to streamline communication, and provide users and devs with a few choices for receiving community discussions, JIRA ticket activity and wiki updates. hudi-bot is an application that currently posts comments on pull requests, around CI jobs.

In this regard, we have the following new communication processes lined up, with a few still in active development.

  1. As you are aware, we have 2 mailing lists: dev and users. To make it easier for users to get these updates on a single platform (slack), we have enhanced hudi-bot to mirror the emails from the 2 mailing lists and post them into respective slack channels (#dev and #users). The sync will happen in near-real-time (a few mins). To ease readability, an email thread will be synced as a single slack thread, i.e., the replies on an email will be synced as replies on the slack channel to the original post.
  2. It is often hard to catch up on historical slack messages. To ease catching up on slack messages (#general) in the past few days, we will further extend the functionality of the hudi bot to read all the slack messages of a day, format them, and send them as a single email digest to the dev mailing list.
  3. Any updates to the cWiki pages, including new pages or modifications to existing pages, will be sent as messages on slack channel #cwiki.
  4. All github activity is already being mirrored to #github slack channel.
  5. Finally, we also plan to ease tracking JIRA tickets. So in near future, the hudi-bot will post slack messages to the channel #jira for few critical updates to JIRA tickets, such as new JIRA tickets created, new comment on the JIRA ticket, etc. We plan to post a single slack thread for a single JIRA ticket.


  • No labels