I was thinking of the same thing about adding a dedicated channel for the daily performance micro bench.
I was even thinking of asking volunteers to watch for the daily performance micro bench. Roman and I are drafting instructions on how to monitor performance regression right now. But I think this is a different topic and I will start a new thread to discuss this once the details are finalized. So, +1 for a dedicated channel for the daily performance micro bench notice. Best, Yuan On Wed, Jun 8, 2022 at 11:38 AM Xingbo Huang <hxbks...@gmail.com> wrote: > Thanks everyone for the great effort driving this. > > +1 for building a dedicated channel for CI builds. > > Best, > Xingbo > > Martijn Visser <martijnvis...@apache.org> 于2022年6月8日周三 01:32写道： > > > Hi Matthias, > > > > I've only thought about it, but I absolutely would +1 this. Making this > > information available in dedicated channels will only improve things. > > > > Best regards, > > > > Martijn > > > > Op di 7 jun. 2022 om 18:12 schreef Matthias Pohl <map...@apache.org>: > > > > > Thanks for driving the Slack channel efforts and setting everything up. > > :-) > > > > > > I'm wondering whether we should extend the Slack space to also have a > > > channel dedicated for CI builds to enable the release managers to > monitor > > > CI builds on master and the release branches through the Apache Flink > > Slack > > > workspace. It might help us in being more transparent with the release > > > process. The same goes for the Flink performance tests [1]. > > > > > > Are there plans around that already? I couldn't find anything related > in > > > [2]. Or is it worth opening another thread around that topic. > > > > > > Best, > > > Matthias > > > > > > [1] > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > [2] https://cwiki.apache.org/confluence/display/FLINK/Slack+Management > > > On Tue, Jun 7, 2022 at 10:39 AM Jing Ge <j...@ververica.com> wrote: > > > > > > > got it, thanks Martijn! > > > > > > > > Best regards, > > > > Jing > > > > > > > > > > > > On Tue, Jun 7, 2022 at 10:38 AM Martijn Visser < > > martijnvis...@apache.org > > > > > > > > wrote: > > > > > > > > > Hi Jing, > > > > > > > > > > Yes, since this Flink Community workspace is treated as one > company. > > So > > > > > everyone you want to invite, should considered a 'coworker'. > > > > > > > > > > Best regards, > > > > > > > > > > Martijn > > > > > > > > > > Op za 4 jun. 2022 om 20:02 schreef Jing Ge <j...@ververica.com>: > > > > > > > > > >> Hi Xingtong, > > > > >> > > > > >> While inviting new members, there are two options: "From another > > > > company" > > > > >> vs "Your coworker". In this case, we should always choose "Your > > > > coworker" > > > > >> to add new members to the Apache Flink workspace, right? > > > > >> > > > > >> Best regards, > > > > >> Jing > > > > >> > > > > >> On Fri, Jun 3, 2022 at 1:10 PM Yuan Mei <yuanmei.w...@gmail.com> > > > wrote: > > > > >> > > > > >>> Thanks, Xintong and Jark the great effort driving this, and > > everyone > > > > for > > > > >>> making this possible. > > > > >>> > > > > >>> I've also Twittered this announcement on our Apache Flink Twitter > > > > >>> account. > > > > >>> > > > > >>> Best > > > > >>> > > > > >>> Yuan > > > > >>> > > > > >>> > > > > >>> > > > > >>> On Fri, Jun 3, 2022 at 12:54 AM Jing Ge <j...@ververica.com> > > wrote: > > > > >>> > > > > >>>> Thanks everyone for your effort! > > > > >>>> > > > > >>>> Best regards, > > > > >>>> Jing > > > > >>>> > > > > >>>> On Thu, Jun 2, 2022 at 4:17 PM Martijn Visser < > > > > martijnvis...@apache.org> > > > > >>>> wrote: > > > > >>>> > > > > >>>>> Thanks everyone for joining! It's good to see so many have > joined > > > in > > > > >>>>> such a short time already. I've just refreshed the link which > you > > > can > > > > >>>>> always find on the project website [1] > > > > >>>>> > > > > >>>>> Best regards, Martijn > > > > >>>>> > > > > >>>>> [1] https://flink.apache.org/community.html#slack > > > > >>>>> > > > > >>>>> Op do 2 jun. 2022 om 11:42 schreef Jingsong Li < > > > > jingsongl...@gmail.com > > > > >>>>> >: > > > > >>>>> > > > > >>>>>> Thanks Xingtong, Jark, Martijn and Robert for making this > > > possible! > > > > >>>>>> > > > > >>>>>> Best, > > > > >>>>>> Jingsong > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> On Thu, Jun 2, 2022 at 5:32 PM Jark Wu <imj...@gmail.com> > > wrote: > > > > >>>>>> > > > > >>>>>>> Thank Xingtong for making this possible! > > > > >>>>>>> > > > > >>>>>>> Cheers, > > > > >>>>>>> Jark Wu > > > > >>>>>>> > > > > >>>>>>> On Thu, 2 Jun 2022 at 15:31, Xintong Song < > > tonysong...@gmail.com > > > > > > > > >>>>>>> wrote: > > > > >>>>>>> > > > > >>>>>>> > Hi everyone, > > > > >>>>>>> > > > > > >>>>>>> > I'm very happy to announce that the Apache Flink community > > has > > > > >>>>>>> created a > > > > >>>>>>> > dedicated Slack workspace [1]. Welcome to join us on Slack. > > > > >>>>>>> > > > > > >>>>>>> > ## Join the Slack workspace > > > > >>>>>>> > > > > > >>>>>>> > You can join the Slack workspace by either of the following > > two > > > > >>>>>>> ways: > > > > >>>>>>> > 1. Click the invitation link posted on the project website > > [2]. > > > > >>>>>>> > 2. Ask anyone who already joined the Slack workspace to > > invite > > > > you. > > > > >>>>>>> > > > > > >>>>>>> > We recommend 2), if available. Due to Slack limitations, > the > > > > >>>>>>> invitation > > > > >>>>>>> > link in 1) expires and needs manual updates after every 100 > > > > >>>>>>> invites. If it > > > > >>>>>>> > is expired, please reach out to the dev / user mailing > lists. > > > > >>>>>>> > > > > > >>>>>>> > ## Community rules > > > > >>>>>>> > > > > > >>>>>>> > When using the community Slack workspace, please follow > these > > > > >>>>>>> community > > > > >>>>>>> > rules: > > > > >>>>>>> > * *Be respectful* - This is the most important rule! > > > > >>>>>>> > * All important decisions and conclusions *must be > reflected > > > back > > > > >>>>>>> to the > > > > >>>>>>> > mailing lists*. "If it didn’t happen on a mailing list, it > > > didn’t > > > > >>>>>>> happen." > > > > >>>>>>> > - The Apache Mottos [3] > > > > >>>>>>> > * Use *Slack threads* to keep parallel conversations from > > > > >>>>>>> overwhelming a > > > > >>>>>>> > channel. > > > > >>>>>>> > * Please *do not direct message* people for > troubleshooting, > > > Jira > > > > >>>>>>> assigning > > > > >>>>>>> > and PR review. These should be picked-up voluntarily. > > > > >>>>>>> > > > > > >>>>>>> > > > > > >>>>>>> > ## Maintenance > > > > >>>>>>> > > > > > >>>>>>> > > > > > >>>>>>> > Committers can refer to this wiki page [4] for information > > > needed > > > > >>>>>>> for > > > > >>>>>>> > maintaining the Slack workspace. > > > > >>>>>>> > > > > > >>>>>>> > > > > > >>>>>>> > Thanks Jark, Martijn and Robert for helping setting up the > > > Slack > > > > >>>>>>> workspace. > > > > >>>>>>> > > > > > >>>>>>> > > > > > >>>>>>> > Best, > > > > >>>>>>> > > > > > >>>>>>> > Xintong > > > > >>>>>>> > > > > > >>>>>>> > > > > > >>>>>>> > [1] https://apache-flink.slack.com/ > > > > >>>>>>> > > > > > >>>>>>> > [2] https://flink.apache.org/community.html#slack > > > > >>>>>>> > > > > > >>>>>>> > [3] http://theapacheway.com/on-list/ > > > > >>>>>>> > > > > > >>>>>>> > [4] > > > > >>>>>>> > > > https://cwiki.apache.org/confluence/display/FLINK/Slack+Management > > > > >>>>>>> > > > > > >>>>>>> > > > > >>>>>> > > > > > > > > > >
