Re: [MENTORS] Podling reports due June 1st

2022-05-22 Thread justin
Hi, A report is due from Devlake but due to an issue with their entry in podlings.xml they are not included in this list or in the reminder that was sent out. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@i

Re: [HELP WANTED] Creating the next board report

2022-05-22 Thread Justin Mclean
Hi, > After the board meeting: > - Update podlings.xml to mark podling that did not report, ones whose report > was missing but reported and podlings at the end of their monthly reporting > period > - assign podling shepherds using assign_shepherds.py > - run clutch script (./clutch2.sh) and gen

Re: [MENTORS] Incubator reminder script minor issue

2022-05-22 Thread Justin Mclean
Hi, The issue was the future assuagement of shepherds, so I fixed that and I’ll resend the reminders. This may mean that a couple of podlings got a reminder when they don’t need to report. If you are not listed in the wiki there no need to submit a report. Kind Regards, Justin

[MENTORS] Incubator reminder script minor issue

2022-05-22 Thread Justin Mclean
HI, Look like there's a small issue with the Incubator reminder script and it send out some reminders to the wrong podlings. What was listed in the wiki is correct. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubsc

[MENTORS] Podling reports due June 1st

2022-05-22 Thread Justin Mclean
Hi, Please submit your podling reports here [1] Reporting timeline is: Wed June 1st -- Podling reports due by end of day Sun June 5th -- Shepherd reviews due by end of day Sun June 5th -- Summary due by end of day Tue June 7th -- Mentor signoff due by end of day Wed June 8th -

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-22 Thread Saisai Shao
I see, thanks Justin and Daniel for your inputs. Best regards, Jerry Daniel Widdis 于2022年5月23日周一 11:32写道: > Adding onto this, even if there may be no legal trademark issue, there is > other software by this name which makes it less than desirable. Quoted > from [1] > > > Avoiding search-result

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-22 Thread Daniel Widdis
Adding onto this, even if there may be no legal trademark issue, there is other software by this name which makes it less than desirable. Quoted from [1] > Avoiding search-results confusion is important for another reason. Apache > projects are often very quickly highly ranked. An Apache projec

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-22 Thread Justin Mclean
HI, > According to the trademarks@ current cursory feedback, looks like project > name "Firestorm" is OK. I don’t this that is the case. Trademark checked “FlameStorm”, and said that if Firestorm was as issue then FlameStorm would also be an issue. I don’t believe they have checked FireStorm.

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-22 Thread Jerry Shao
Hi all, Thanks for your feedbacks. According to the trademarks@ current cursory feedback, looks like project name "Firestorm" is OK. After a quick search of registered US trademarks I don't see anything > that would give me cause for concern. > > Note that if FIRESTORM was infringing, then I wou

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread Jerry Shao
+1 binding. Good luck to Inlong project. Best Jerry guo jiwei 于2022年5月23日周一 09:22写道: > +1 (non-binding). good luck > > > Regards > Jiwei Guo (Tboy) > > > On Mon, May 23, 2022 at 8:46 AM Xiangdong Huang > wrote: > > > +1 binding. Good luck. > > --- > > Xiangdong

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread guo jiwei
+1 (non-binding). good luck Regards Jiwei Guo (Tboy) On Mon, May 23, 2022 at 8:46 AM Xiangdong Huang wrote: > +1 binding. Good luck. > --- > Xiangdong Huang > > > > Liu Ted 于2022年5月22日周日 23:41写道: > > > +1 (binding). Good luck! > > > > Ted Liu > > > > 2022 年

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread Xiangdong Huang
+1 binding. Good luck. --- Xiangdong Huang Liu Ted 于2022年5月22日周日 23:41写道: > +1 (binding). Good luck! > > Ted Liu > > 2022 年 5 月 22 日周日 22:09,俊平堵 写道: +1 (binding). > Good luck to InLong! > > Thanks, > > Junping > > Charles Zhang 于2022年5月19日周四 17:10写道: > > >

回复:Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread Liu Ted
+1 (binding). Good luck! Ted Liu 2022 年 5 月 22 日周日 22:09,俊平堵 写道: +1 (binding). Good luck to InLong! Thanks, Junping Charles Zhang 于2022年5月19日周四 17:10写道: > Dear Apache Incubator Community, > > > The InLong Project has been incubating since 2019-11-03. In the past two > and a half years

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread 俊平堵
+1 (binding). Good luck to InLong! Thanks, Junping Charles Zhang 于2022年5月19日周四 17:10写道: > Dear Apache Incubator Community, > > > The InLong Project has been incubating since 2019-11-03. In the past two > and a half years, the project has been renamed from TubeMQ to InLong, and > expanded its s

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread 张家峰
1,good luck! Zirui Peng 于2022年5月22日 周日20:02写道: > +1, all the best, great work ! > > On 2022/05/21 05:03:39 Aloys Zhang wrote: > > +1, good luck > > > > Liang Chen 于2022年5月21日周六 00:04写道: > > > > > +1, good luck. > > > > > > Regards > > > Liang > > > > > > tison 于2022年5月20日周五 18:13写道: > > > > > >

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

2022-05-22 Thread Zirui Peng
+1, all the best, great work ! On 2022/05/21 05:03:39 Aloys Zhang wrote: > +1, good luck > > Liang Chen 于2022年5月21日周六 00:04写道: > > > +1, good luck. > > > > Regards > > Liang > > > > tison 于2022年5月20日周五 18:13写道: > > > > > +1 good luck > > > > > > Young Seung Andrew Ko 于2022年5月20日 > > 周五17:36写道:

Re: [VOTE] Release Apache Linkis (Incubating) 1.1.1-RC2

2022-05-22 Thread Zhen Wang
+1 (non-binding) I checked: [OK] Download links are valid. [OK] Checksums and PGP signatures are valid. [OK] Source code distributions have correct names matching the current release. [OK] LICENSE and NOTICE files are correct for each Linkis repo. [OK] All files have license headers if necessary.