You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hudi.apache.org by Rajesh Mahindra <rm...@gmail.com> on 2021/11/09 17:18:09 UTC
[DISCUSS] Hudi Community Communication Updates
Hi Folks,
We are thinking of improving community communication, and here is a list of
things we propose to do (some of them are already available).
https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
While we have a few things proposed, we plan to prioritize the following
two features to hopefully ease communication. We plan to extend the current
hudi bot (slack app) to implement the features.
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
propose to enhance 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.
Please let us know what you think of this proposal, and feel free to raise
concerns if any.
Thanks,
Rajesh
Re: [DISCUSS] Hudi Community Communication Updates
Posted by Rajesh Mahindra <rm...@gmail.com>.
Hi folks,
We are starting to roll the first feature out. Starting today, all dev
email threads will show up on slack channel #devwork.
Thanks
Rajesh
On Wed, Nov 10, 2021 at 9:33 AM Vinoth Chandar <vi...@apache.org> wrote:
> +1 for this. We will also archive all community activity on ASF
> infrastructure this way!
>
> On Wed, Nov 10, 2021 at 7:14 AM Pratyaksh Sharma <pr...@gmail.com>
> wrote:
>
>> Hi Rajesh,
>>
>> I do not have any strong opinions for/against point #1.
>>
>> Point #2 definitely seems useful to me.
>> I hope messages from #general channel will be formatted as respective
>> threads in either case - if the thread started on the same day or if some
>> reply comes on some ongoing thread.
>>
>> On Tue, Nov 9, 2021 at 10:48 PM Rajesh Mahindra <rm...@gmail.com>
>> wrote:
>>
>> > Hi Folks,
>> >
>> > We are thinking of improving community communication, and here is a
>> list of
>> > things we propose to do (some of them are already available).
>> >
>> >
>> https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
>> >
>> > While we have a few things proposed, we plan to prioritize the following
>> > two features to hopefully ease communication. We plan to extend the
>> current
>> > hudi bot (slack app) to implement the features.
>> >
>> >
>> > 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
>> > propose to enhance 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.
>> >
>> >
>> >
>> > Please let us know what you think of this proposal, and feel free to
>> raise
>> > concerns if any.
>> >
>> > Thanks,
>> > Rajesh
>> >
>>
>
--
Take Care,
Rajesh Mahindra
Re: [DISCUSS] Hudi Community Communication Updates
Posted by Rajesh Mahindra <rm...@gmail.com>.
Hi folks,
We are starting to roll the first feature out. Starting today, all dev
email threads will show up on slack channel #devwork.
Thanks
Rajesh
On Wed, Nov 10, 2021 at 9:33 AM Vinoth Chandar <vi...@apache.org> wrote:
> +1 for this. We will also archive all community activity on ASF
> infrastructure this way!
>
> On Wed, Nov 10, 2021 at 7:14 AM Pratyaksh Sharma <pr...@gmail.com>
> wrote:
>
>> Hi Rajesh,
>>
>> I do not have any strong opinions for/against point #1.
>>
>> Point #2 definitely seems useful to me.
>> I hope messages from #general channel will be formatted as respective
>> threads in either case - if the thread started on the same day or if some
>> reply comes on some ongoing thread.
>>
>> On Tue, Nov 9, 2021 at 10:48 PM Rajesh Mahindra <rm...@gmail.com>
>> wrote:
>>
>> > Hi Folks,
>> >
>> > We are thinking of improving community communication, and here is a
>> list of
>> > things we propose to do (some of them are already available).
>> >
>> >
>> https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
>> >
>> > While we have a few things proposed, we plan to prioritize the following
>> > two features to hopefully ease communication. We plan to extend the
>> current
>> > hudi bot (slack app) to implement the features.
>> >
>> >
>> > 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
>> > propose to enhance 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.
>> >
>> >
>> >
>> > Please let us know what you think of this proposal, and feel free to
>> raise
>> > concerns if any.
>> >
>> > Thanks,
>> > Rajesh
>> >
>>
>
--
Take Care,
Rajesh Mahindra
Re: [DISCUSS] Hudi Community Communication Updates
Posted by Vinoth Chandar <vi...@apache.org>.
+1 for this. We will also archive all community activity on ASF
infrastructure this way!
On Wed, Nov 10, 2021 at 7:14 AM Pratyaksh Sharma <pr...@gmail.com>
wrote:
> Hi Rajesh,
>
> I do not have any strong opinions for/against point #1.
>
> Point #2 definitely seems useful to me.
> I hope messages from #general channel will be formatted as respective
> threads in either case - if the thread started on the same day or if some
> reply comes on some ongoing thread.
>
> On Tue, Nov 9, 2021 at 10:48 PM Rajesh Mahindra <rm...@gmail.com>
> wrote:
>
> > Hi Folks,
> >
> > We are thinking of improving community communication, and here is a list
> of
> > things we propose to do (some of them are already available).
> >
> > https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
> >
> > While we have a few things proposed, we plan to prioritize the following
> > two features to hopefully ease communication. We plan to extend the
> current
> > hudi bot (slack app) to implement the features.
> >
> >
> > 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
> > propose to enhance 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.
> >
> >
> >
> > Please let us know what you think of this proposal, and feel free to
> raise
> > concerns if any.
> >
> > Thanks,
> > Rajesh
> >
>
Re: [DISCUSS] Hudi Community Communication Updates
Posted by Vinoth Chandar <vi...@apache.org>.
+1 for this. We will also archive all community activity on ASF
infrastructure this way!
On Wed, Nov 10, 2021 at 7:14 AM Pratyaksh Sharma <pr...@gmail.com>
wrote:
> Hi Rajesh,
>
> I do not have any strong opinions for/against point #1.
>
> Point #2 definitely seems useful to me.
> I hope messages from #general channel will be formatted as respective
> threads in either case - if the thread started on the same day or if some
> reply comes on some ongoing thread.
>
> On Tue, Nov 9, 2021 at 10:48 PM Rajesh Mahindra <rm...@gmail.com>
> wrote:
>
> > Hi Folks,
> >
> > We are thinking of improving community communication, and here is a list
> of
> > things we propose to do (some of them are already available).
> >
> > https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
> >
> > While we have a few things proposed, we plan to prioritize the following
> > two features to hopefully ease communication. We plan to extend the
> current
> > hudi bot (slack app) to implement the features.
> >
> >
> > 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
> > propose to enhance 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.
> >
> >
> >
> > Please let us know what you think of this proposal, and feel free to
> raise
> > concerns if any.
> >
> > Thanks,
> > Rajesh
> >
>
Re: [DISCUSS] Hudi Community Communication Updates
Posted by Pratyaksh Sharma <pr...@gmail.com>.
Hi Rajesh,
I do not have any strong opinions for/against point #1.
Point #2 definitely seems useful to me.
I hope messages from #general channel will be formatted as respective
threads in either case - if the thread started on the same day or if some
reply comes on some ongoing thread.
On Tue, Nov 9, 2021 at 10:48 PM Rajesh Mahindra <rm...@gmail.com> wrote:
> Hi Folks,
>
> We are thinking of improving community communication, and here is a list of
> things we propose to do (some of them are already available).
>
> https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
>
> While we have a few things proposed, we plan to prioritize the following
> two features to hopefully ease communication. We plan to extend the current
> hudi bot (slack app) to implement the features.
>
>
> 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
> propose to enhance 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.
>
>
>
> Please let us know what you think of this proposal, and feel free to raise
> concerns if any.
>
> Thanks,
> Rajesh
>
Re: [DISCUSS] Hudi Community Communication Updates
Posted by Pratyaksh Sharma <pr...@gmail.com>.
Hi Rajesh,
I do not have any strong opinions for/against point #1.
Point #2 definitely seems useful to me.
I hope messages from #general channel will be formatted as respective
threads in either case - if the thread started on the same day or if some
reply comes on some ongoing thread.
On Tue, Nov 9, 2021 at 10:48 PM Rajesh Mahindra <rm...@gmail.com> wrote:
> Hi Folks,
>
> We are thinking of improving community communication, and here is a list of
> things we propose to do (some of them are already available).
>
> https://cwiki.apache.org/confluence/display/HUDI/Community+Communication
>
> While we have a few things proposed, we plan to prioritize the following
> two features to hopefully ease communication. We plan to extend the current
> hudi bot (slack app) to implement the features.
>
>
> 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
> propose to enhance 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.
>
>
>
> Please let us know what you think of this proposal, and feel free to raise
> concerns if any.
>
> Thanks,
> Rajesh
>