date:20220421

Re: May 2022 Podling Reporting Timeline

2022-04-21 Thread Christofer Dutz

But reporting isn't the incubators way of punishing podling. It's the way we 
know how they are doing.

Yes it was our fault for not pinging them in time, but I really would love to 
see reports, that we missed.

But what do the others think?

Chris

Holen Sie sich Outlook für Android

From: John D. Ament 
Sent: Thursday, April 21, 2022 2:29:16 PM
To: general 
Subject: Re: May 2022 Podling Reporting Timeline

Hi Christofer

On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
wrote:

> Hi John,
>
> guess I missed the second part of your email ;-)
>
> Well, I am a bit unsure if we really should skip the ones that for example
> missed to submit last month because nobody reminded them, but I think in
> such a case it would be half a year of information missing. Even if this
> might not be too useful for the board, I think it's useful to the IPMC.
>

Basically, I can't (personally) fault a podling for not reporting when no
reminders were sent out.  We failed to hold up our side of the agreement in
my mind.  It's great that some podlings still did the work to get a report
put together.  Perhaps we review those in the past 3 months of missed
reports and also report them? I'm not sure.

>
> So, I think podlings that missed filling in their parts in the last 3
> months, should still report this time. But that's just my opinion.
>

I agree with you, the problem is that every podling (other than new
podlings possibly) has missed a report (at least from the board's point of
view).  While there's the main review the IPMC takes on the podlings'
reports, the board also reviews them.  Since the IPMC lapsed on maintaining
this, it may end up over burdening the board to put out a report that has
every single podling reporting in it.

>
> Chris
>
> -Original Message-
> From: Christofer Dutz 
> Sent: Donnerstag, 21. April 2022 10:42
> To: general@incubator.apache.org
> Subject: RE: May 2022 Podling Reporting Timeline
>
> I should also add that some projects have failed to submit in the last 3
> months, so I would add to this list:
>
> - brpc
> - Annotator
> - Crail
> - EventMesh
> - Flagon
> - Hivemail
> - InLong
> - Liminal
> - Marvin-AI
> - Milagro
> - Nemo
> - Pony Mail
> - Spot
> - Teaclave
> - Wayang
>
> So, we're also expecting these projects to report this month.
>
> Chris
>
> -Original Message-
> From: John D. Ament 
> Sent: Mittwoch, 20. April 2022 18:24
> To: general 
> Subject: May 2022 Podling Reporting Timeline
>
> Note - I'm sending this a week early per procedure as we have some catch
> up to do.
>
> May 2022 Incubator report timeline:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
>
> Wed May 04 -- Podling reports due by end of day
> Sun May 08 -- Shepherd reviews due by end of day
> Sun May 08 -- Summary due by end of day
> Tue May 10 -- Mentor signoff due by end of day
> Wed May 11 -- Report submitted to Board
> Wed May 18 -- Board meeting
>
> According to podlings.xml, the following podlings are expected to report:
> - Training
> - Heron
> - Tuweni
> - Pagespeed
> - Toree
> - Livy
> - NLPCraft
> - Sedona
> - Doris
> - SDAP
> - Linkis
>
> I'm suggesting that right now we keep the current reporting periods as we
> the Incubator PMC have failed to report to the Board, rather than it
> necessarily being a failing of podlings.  If your podling is on this list
> but isn't present on the confluence page, please add it with the necessary
> sections.  i'll take a look in the next few days and make sure podlings.xml
> represents reality.
>
> - John, your friendly neighborhood Report Manager
>

Re: [DISCUSS] Incubating Proposal of DevLake

2022-04-21 Thread Jean-Baptiste Onofré

Hi Hezheng

Thanks for the details. It helps as well.

If you need help/additional mentor, please let me know. I don't know
go very well but happy to learn and help. However, I think you already
have enough and good mentors on the proposal.

Regards
JB

On Thu, Apr 21, 2022 at 8:18 AM Hezheng Yin  wrote:
>
> Hi JB,
>
> Thanks for your interests in DevLake. One key difference between DevLake and 
> Gobblin/NiFi is that Gobblin/NiFi are domain agnostic general frameworks 
> while DevLake specializes in the domain of software development data. This 
> focus allows DevLake to better “understand” the data that it ingests, 
> cleanses, transforms, analyzes, and visualizes for developers. At the 
> foundation of this understanding is DevLake’s data 
> model 
> built on top of the software development process. We’ll keep expanding this 
> model as DevLake supports new DevOps tools (data sources) requested by the 
> community. If you have any other question or suggestion, please let us know. 
> Any feedback is greatly appreciated!
>
> Best,
> Hezheng
> Maintainer of DevLake
>
> From: Jean-Baptiste Onofré 
> Date: Monday, April 18, 2022 at 7:23 AM
> To: general@incubator.apache.org 
> Subject: Re: [DISCUSS] Incubating Proposal of DevLake
> Thanks, it helps !
>
> Regards
> JB
>
> On Mon, Apr 18, 2022 at 4:14 PM Willem Jiang  wrote:
> >
> > Hi JB
> >
> > You may find the information about the DevOps data collection here[1]
> > There are some domain related entities schema[2] which are built on
> > top of the development process.
> >
> > [1]https://github.com/merico-dev/lake/blob/main/ARCHITECTURE.md
> > [2]https://github.com/merico-dev/lake/wiki/DataModel.Domain-layer-schema
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Apr 17, 2022 at 12:14 AM Jean-Baptiste Onofré  
> > wrote:
> > >
> > > Hi Willem,
> > >
> > > It looks interesting. I took a look on github repo. I don't see the
> > > relation between DevOps and data collection/ETL part mentioned on the
> > > README.
> > >
> > > For the data collection/ETL framework, it sounds similar to
> > > Gobblin/NiFi, etc. The DevOps part is more interesting IMHO. I have to
> > > dig into this.
> > >
> > > Regards
> > > JB
> > >
> > > On Thu, Apr 7, 2022 at 10:20 AM Willem Jiang  
> > > wrote:
> > > >
> > > > We want to propose  DevLake[1]  as a new Apache Incubator project.
> > > >
> > > > DevLake helps developer teams integrate and analyze software
> > > > development data throughout the software development life cycle
> > > > (SDLC).
> > > > Specifically, DevLake provides:
> > > >
> > > > * High-quality connectors that integrate data from various DevOps tools;
> > > > * A comprehensive and unified data model and metrics that enable
> > > > developers to easily query data and answer questions regarding their
> > > > development process;
> > > > * A plugin system that allows customizable data connectors and 
> > > > enrichers;
> > > > * An unified ETL management module that orchestrates data collection
> > > > and analysis.
> > > >
> > > > I'd be happy to be the Champion of this project and many thanks to
> > > > Liang Zhang (zhangliang at apache dot org)，Lidong Dai (lidongdai at 
> > > > apache
> > > > dot org)，Sijie Guo (sijie at apache dot org） for being the mentor of  
> > > > DevLake
> > > > project and helping us to polish the incubating proposal[2].
> > > >
> > > > Looking forward to your feedback and thank you very much.
> > > >
> > > > [1]https://github.com/merico-dev/lake
> > > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Kvrocks into the Apache Incubator

2022-04-21 Thread Eason Chen

+1 (non-binding)

On Fri, Apr 22, 2022 at 11:38 AM Felix Cheung  wrote:
>
> +1
>
> On Thu, Apr 21, 2022 at 7:28 PM Sheng Wu  wrote:
>
> > +1 binding
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Liang Chen  于2022年4月22日周五 09:19写道：
> > >
> > > +1(binding)
> > >
> > > Regards
> > > Liang
> > >
> > > 在 2022年4月20日星期三，Furkan KAMACI  写道：
> > >
> > > > Hi,
> > > >
> > > > +1 (binding)
> > > >
> > > > Kind Regards,
> > > > Furkan KAMACI
> > > >
> > > > On 20 Apr 2022 Wed at 13:49 Calvin Kirs  wrote:
> > > >
> > > > > +1 (binding)
> > > > > Good luck.
> > > > >
> > > > > 张铎(Duo Zhang)  于2022年4月20日周三 18:29写道：
> > > > > >
> > > > > > +1(binding)
> > > > > >
> > > > > > Goson zhang  于2022年4月20日周三 18:27写道：
> > > > > >
> > > > > > > +1 (non-binding)
> > > > > > >
> > > > > > > Good luck!
> > > > > > >
> > > > > > > Willem Jiang  于2022年4月20日周三 14:38写道：
> > > > > > >
> > > > > > > > +1 (binding)
> > > > > > > >
> > > > > > > > Willem Jiang
> > > > > > > >
> > > > > > > > Twitter: willemjiang
> > > > > > > > Weibo: 姜宁willem
> > > > > > > >
> > > > > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen <
> > > > chenliang...@apache.org>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would
> > like to
> > > > > > > > > call a VOTE to accept Kvrocks into the Apache Incubator,
> > please
> > > > > check
> > > > > > > out
> > > > > > > > > the Kvrocks Proposal from the incubator wiki[2].
> > > > > > > > >
> > > > > > > > > Please cast your vote:
> > > > > > > > >
> > > > > > > > > [ ] +1, bring Kvrocks into the Incubator
> > > > > > > > > [ ] +0, I don't care either way
> > > > > > > > > [ ] -1, do not bring Kvrocks into the Incubator, because...
> > > > > > > > >
> > > > > > > > > The vote will open at least for 72 hours, and only votes
> > from the
> > > > > > > > > Incubator PMC are binding, but votes from everyone are
> > welcome.
> > > > > > > > >
> > > > > > > > > [1]
> > > > > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> > > > > > > > > [2]
> > > > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
> > > > > > > > >
> > > > > > > > > Regards
> > > > > > > > > Liang
> > > > > > > >
> > > > > > > > 
> > > > -
> > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best wishes！
> > > > > CalvinKirs
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Kvrocks into the Apache Incubator

2022-04-21 Thread Felix Cheung

+1

On Thu, Apr 21, 2022 at 7:28 PM Sheng Wu  wrote:

> +1 binding
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> Liang Chen  于2022年4月22日周五 09:19写道：
> >
> > +1(binding)
> >
> > Regards
> > Liang
> >
> > 在 2022年4月20日星期三，Furkan KAMACI  写道：
> >
> > > Hi,
> > >
> > > +1 (binding)
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > On 20 Apr 2022 Wed at 13:49 Calvin Kirs  wrote:
> > >
> > > > +1 (binding)
> > > > Good luck.
> > > >
> > > > 张铎(Duo Zhang)  于2022年4月20日周三 18:29写道：
> > > > >
> > > > > +1(binding)
> > > > >
> > > > > Goson zhang  于2022年4月20日周三 18:27写道：
> > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Good luck!
> > > > > >
> > > > > > Willem Jiang  于2022年4月20日周三 14:38写道：
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Willem Jiang
> > > > > > >
> > > > > > > Twitter: willemjiang
> > > > > > > Weibo: 姜宁willem
> > > > > > >
> > > > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen <
> > > chenliang...@apache.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would
> like to
> > > > > > > > call a VOTE to accept Kvrocks into the Apache Incubator,
> please
> > > > check
> > > > > > out
> > > > > > > > the Kvrocks Proposal from the incubator wiki[2].
> > > > > > > >
> > > > > > > > Please cast your vote:
> > > > > > > >
> > > > > > > > [ ] +1, bring Kvrocks into the Incubator
> > > > > > > > [ ] +0, I don't care either way
> > > > > > > > [ ] -1, do not bring Kvrocks into the Incubator, because...
> > > > > > > >
> > > > > > > > The vote will open at least for 72 hours, and only votes
> from the
> > > > > > > > Incubator PMC are binding, but votes from everyone are
> welcome.
> > > > > > > >
> > > > > > > > [1]
> > > > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> > > > > > > > [2]
> > > > > > >
> > > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > Liang
> > > > > > >
> > > > > > > 
> > > -
> > > > > > > To unsubscribe, e-mail:
> general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> general-h...@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best wishes！
> > > > CalvinKirs
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: May 2022 Podling Reporting Timeline

2022-04-21 Thread Eason Chen

EventMesh also missed for not receiving reminder email, we will  add it later.

On Fri, Apr 22, 2022 at 8:38 AM tan zhongyi  wrote:
>
> brpc also missed the pod report of April.
>
> Maybe we are too used to wait for reminder email from Justin.
>
> Anyway,  I will provide pod report in May if needed.
>
> Thanks.
>
>
>
> 发件人: Mingshen Sun 
> 日期: 星期五, 2022年4月22日 上午2:00
> 收件人: general@incubator.apache.org , 
> d...@teaclave.apache.org 
> 主题: Re: May 2022 Podling Reporting Timeline
> Hi all,
>
> I'm from the Teaclave project. I just noticed that we missed April's
> report because of the reminder issue.
>
> Should we add it in May's report also? I see some discussions here but
> no conclusion yet.
>
> For Teaclave, we have no problem with adding an additional report in May.
>
> Mingshen
>
>
> On Thu, Apr 21, 2022 at 5:29 AM John D. Ament  wrote:
> >
> > Hi Christofer
> >
> > On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
> > wrote:
> >
> > > Hi John,
> > >
> > > guess I missed the second part of your email ;-)
> > >
> > > Well, I am a bit unsure if we really should skip the ones that for example
> > > missed to submit last month because nobody reminded them, but I think in
> > > such a case it would be half a year of information missing. Even if this
> > > might not be too useful for the board, I think it's useful to the IPMC.
> > >
> >
> > Basically, I can't (personally) fault a podling for not reporting when no
> > reminders were sent out.  We failed to hold up our side of the agreement in
> > my mind.  It's great that some podlings still did the work to get a report
> > put together.  Perhaps we review those in the past 3 months of missed
> > reports and also report them? I'm not sure.
> >
> >
> > >
> > > So, I think podlings that missed filling in their parts in the last 3
> > > months, should still report this time. But that's just my opinion.
> > >
> >
> > I agree with you, the problem is that every podling (other than new
> > podlings possibly) has missed a report (at least from the board's point of
> > view).  While there's the main review the IPMC takes on the podlings'
> > reports, the board also reviews them.  Since the IPMC lapsed on maintaining
> > this, it may end up over burdening the board to put out a report that has
> > every single podling reporting in it.
> >
> >
> > >
> > > Chris
> > >
> > > -Original Message-
> > > From: Christofer Dutz 
> > > Sent: Donnerstag, 21. April 2022 10:42
> > > To: general@incubator.apache.org
> > > Subject: RE: May 2022 Podling Reporting Timeline
> > >
> > > I should also add that some projects have failed to submit in the last 3
> > > months, so I would add to this list:
> > >
> > > - brpc
> > > - Annotator
> > > - Crail
> > > - EventMesh
> > > - Flagon
> > > - Hivemail
> > > - InLong
> > > - Liminal
> > > - Marvin-AI
> > > - Milagro
> > > - Nemo
> > > - Pony Mail
> > > - Spot
> > > - Teaclave
> > > - Wayang
> > >
> > > So, we're also expecting these projects to report this month.
> > >
> > > Chris
> > >
> > > -Original Message-
> > > From: John D. Ament 
> > > Sent: Mittwoch, 20. April 2022 18:24
> > > To: general 
> > > Subject: May 2022 Podling Reporting Timeline
> > >
> > > Note - I'm sending this a week early per procedure as we have some catch
> > > up to do.
> > >
> > > May 2022 Incubator report timeline:
> > >
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
> > >
> > > Wed May 04 -- Podling reports due by end of day
> > > Sun May 08 -- Shepherd reviews due by end of day
> > > Sun May 08 -- Summary due by end of day
> > > Tue May 10 -- Mentor signoff due by end of day
> > > Wed May 11 -- Report submitted to Board
> > > Wed May 18 -- Board meeting
> > >
> > > According to podlings.xml, the following podlings are expected to report:
> > > - Training
> > > - Heron
> > > - Tuweni
> > > - Pagespeed
> > > - Toree
> > > - Livy
> > > - NLPCraft
> > > - Sedona
> > > - Doris
> > > - SDAP
> > > - Linkis
> > >
> > > I'm suggesting that right now we keep the current reporting periods as we
> > > the Incubator PMC have failed to report to the Board, rather than it
> > > necessarily being a failing of podlings.  If your podling is on this list
> > > but isn't present on the confluence page, please add it with the necessary
> > > sections.  i'll take a look in the next few days and make sure 
> > > podlings.xml
> > > represents reality.
> > >
> > > - John, your friendly neighborhood Report Manager
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Kvrocks into the Apache Incubator

2022-04-21 Thread Sheng Wu

+1 binding

Sheng Wu 吴晟
Twitter, wusheng1108

Liang Chen  于2022年4月22日周五 09:19写道：
>
> +1(binding)
>
> Regards
> Liang
>
> 在 2022年4月20日星期三，Furkan KAMACI  写道：
>
> > Hi,
> >
> > +1 (binding)
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On 20 Apr 2022 Wed at 13:49 Calvin Kirs  wrote:
> >
> > > +1 (binding)
> > > Good luck.
> > >
> > > 张铎(Duo Zhang)  于2022年4月20日周三 18:29写道：
> > > >
> > > > +1(binding)
> > > >
> > > > Goson zhang  于2022年4月20日周三 18:27写道：
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Good luck!
> > > > >
> > > > > Willem Jiang  于2022年4月20日周三 14:38写道：
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > Willem Jiang
> > > > > >
> > > > > > Twitter: willemjiang
> > > > > > Weibo: 姜宁willem
> > > > > >
> > > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen <
> > chenliang...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would like to
> > > > > > > call a VOTE to accept Kvrocks into the Apache Incubator, please
> > > check
> > > > > out
> > > > > > > the Kvrocks Proposal from the incubator wiki[2].
> > > > > > >
> > > > > > > Please cast your vote:
> > > > > > >
> > > > > > > [ ] +1, bring Kvrocks into the Incubator
> > > > > > > [ ] +0, I don't care either way
> > > > > > > [ ] -1, do not bring Kvrocks into the Incubator, because...
> > > > > > >
> > > > > > > The vote will open at least for 72 hours, and only votes from the
> > > > > > > Incubator PMC are binding, but votes from everyone are welcome.
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> > > > > > > [2]
> > > > > >
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
> > > > > > >
> > > > > > > Regards
> > > > > > > Liang
> > > > > >
> > > > > > 
> > -
> > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > > >
> > > > > >
> > > > >
> > >
> > >
> > >
> > > --
> > > Best wishes！
> > > CalvinKirs
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

2022-04-21 Thread 陈明雨

Dear IPMC,
Thanks for all the discussions and suggestions.
At present, everyone's suggestions have been responded to and corrected. If 
there are no other suggestions or comments, I will launch a formal graduation 
vote in these two days.
Thanks again!




--

此致！Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2022-04-20 19:03:42，"Ming Wen"  写道：
>As Doris' mentor, I have seen Doris' efforts in protecting and solving
>brand issues; during the incubation process, Doris released multiple Apache
>releases and attracted many new committers.
>I think Doris is ready to graduate, good luck:)
>
>Thanks,
>Ming Wen, Apache APISIX PMC Chair
>Twitter: _WenMing
>
>
>Juan Pan  于2022年4月20日周三 14:47写道：
>
>> Hello,
>>
>>
>> [1] shows me the efforts and commitments from Doris community. More PMCs,
>> committers, contributors joined; More releases are available under the
>> supervising and guiding of the committee. Hope it’s better and my support
>> for this discussion.
>>
>>
>> [1] https://incubator.apache.org/clutch/doris.html
>>
>> --
>> Trista Pan
>> Twitter & Github: tristaZero
>>
>>
>>
>>
>> On 04/10/2022 23:50，陈明雨 wrote：
>> Dear Incubator Community,
>>
>> After a discussion[1][2] and vote[3] with the community, we believe Apache
>> Doris (Incubating) is ready for graduation to a TLP, and we'd like to make
>> a discussion with the IPMC.
>>
>> Doris is an MPP-based interactive SQL data warehousing for reporting and
>> analysis and entering the incubator in Sep, 2018.
>>
>> The following is a brief overview of the progress of the Doris project and
>> community since entering the incubator:
>>
>> 1. Community
>>
>> - 9 new PPMC members were added, from five different companies, bringing
>> the total number of PPMC members to 22.
>>
>> - 20 new Committers were added (including the new PPMC members), bringing
>> the total number of Committers to 33.
>>
>> - The number of Contributors is now 289 and growing[4].
>>
>> - The dev@doris mailing list currently has 328 subscribers, and all major
>> project discussions are happening in the dev@doris.
>>
>> 2. Project
>>
>> - 7 releases by 6 release managers. All compliance issues have been
>> resolved.
>>
>> - Doris official website[5] is compliant with Apache Foundation
>> requirements[6].
>>
>> - Project maturity model is detailed in [7].
>>
>> - We have also created a pre-graduation Check List[8] following the Apache
>> official website guidelines and are currently moving forward.
>>
>> - See Doris Project Incubation Status[9] for more info
>>
>>
>>
>>
>> [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr
>>
>> [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv
>>
>> [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf
>>
>> [4] https://github.com/apache/incubator-doris
>>
>> [5] http://doris.incubator.apache.org/
>>
>> [6] https://whimsy.apache.org/pods/project/doris
>>
>> [7]
>> https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris
>>
>> [8]
>> https://cwiki.apache.org/confluence/display/DORIS/Graduation+Check+List
>>
>> [9] https://incubator.apache.org/projects/doris.html
>>
>>
>>
>>
>> Please see the proposed board resolution below and let us know what you
>> think.
>>
>> The discussion will remain open for at least 72 hours.
>>
>>
>> -
>>
>> Establish the Apache Doris Project
>>
>>
>>
>>
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>>
>> the Foundation and consistent with the Foundation's purpose to establish
>>
>> a Project Management Committee charged with the creation and maintenance
>>
>> of open-source software, for distribution at no charge to the public,
>>
>> related to a MPP-based interactive SQL data warehousing for reporting
>>
>> and analysis.
>>
>>
>>
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>
>> (PMC), to be known as the "Apache Doris Project", be and hereby is
>>
>> established pursuant to Bylaws of the Foundation; and be it further
>>
>>
>>
>>
>> RESOLVED, that the Apache Doris Project be and hereby is responsible for
>>
>> the creation and maintenance of software related to a MPP-based
>>
>> interactive SQL data warehousing for reporting and analysis; and be it
>>
>> further
>>
>>
>>
>>
>> RESOLVED, that the office of "Vice President, Apache Doris" be and
>>
>> hereby is created, the person holding such office to serve at the
>>
>> direction of the Board of Directors as the chair of the Apache Doris
>>
>> Project, and to have primary responsibility for management of the
>>
>> projects within the scope of responsibility of the Apache Doris Project;
>>
>> and be it further
>>
>>
>>
>>
>> RESOLVED, that the persons listed immediately below be and hereby are
>>
>> appointed to serve as the initial members of the Apache Doris Project:
>>
>>
>>
>>
>> * Bin

[ANNOUNCE] Apache Kyuubi (Incubating) released 1.5.1-incubating

2022-04-21 Thread Fu Chen

Hi all,

The Apache Kyuubi (Incubating) community is pleased to announce that
Apache Kyuubi (Incubating) 1.5.1-incubating has been released!

Apache Kyuubi (Incubating) is a distributed multi-tenant JDBC server for
large-scale data processing and analytics, built on top of Apache Spark
and designed to support more engines like Apache Flink(Beta), Trino(Beta)
and so on.

Kyuubi provides a pure SQL gateway through Thrift JDBC/ODBC interface
for end-users to manipulate large-scale data with pre-programmed and
extensible Spark SQL engines.

We are aiming to make Kyuubi an "out-of-the-box" tool for data warehouses
and data lakes.

This "out-of-the-box" model minimizes the barriers and costs for end-users
to use Spark at the client-side.

At the server-side, Kyuubi server and engine's multi-tenant architecture
provides the administrators a way to achieve computing resource isolation,
data security, high availability, high client concurrency, etc.

The full release notes and download links are available at:
Release notes: https://kyuubi.apache.org/release/1.5.1-incubating.html
Download page: https://kyuubi.apache.org/releases.html

To learn more about Apache Kyuubi (Incubating), please see
https://kyuubi.apache.org/

Kyuubi Resources:
- Issue Tracker: https://kyuubi.apache.org/issue_tracking.html
- Mailing list: https://kyuubi.apache.org/mailing_lists.html

We would like to thank all contributors of the Kyuubi community and
Incubating
community who made this release possible!

Thanks,
On behalf of Apache Kyuubi (Incubating) community

Re: [VOTE] Accept Kvrocks into the Apache Incubator

2022-04-21 Thread Liang Chen

+1(binding)

Regards
Liang

在 2022年4月20日星期三，Furkan KAMACI  写道：

> Hi,
>
> +1 (binding)
>
> Kind Regards,
> Furkan KAMACI
>
> On 20 Apr 2022 Wed at 13:49 Calvin Kirs  wrote:
>
> > +1 (binding)
> > Good luck.
> >
> > 张铎(Duo Zhang)  于2022年4月20日周三 18:29写道：
> > >
> > > +1(binding)
> > >
> > > Goson zhang  于2022年4月20日周三 18:27写道：
> > >
> > > > +1 (non-binding)
> > > >
> > > > Good luck!
> > > >
> > > > Willem Jiang  于2022年4月20日周三 14:38写道：
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > Willem Jiang
> > > > >
> > > > > Twitter: willemjiang
> > > > > Weibo: 姜宁willem
> > > > >
> > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen <
> chenliang...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would like to
> > > > > > call a VOTE to accept Kvrocks into the Apache Incubator, please
> > check
> > > > out
> > > > > > the Kvrocks Proposal from the incubator wiki[2].
> > > > > >
> > > > > > Please cast your vote:
> > > > > >
> > > > > > [ ] +1, bring Kvrocks into the Incubator
> > > > > > [ ] +0, I don't care either way
> > > > > > [ ] -1, do not bring Kvrocks into the Incubator, because...
> > > > > >
> > > > > > The vote will open at least for 72 hours, and only votes from the
> > > > > > Incubator PMC are binding, but votes from everyone are welcome.
> > > > > >
> > > > > > [1]
> > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> > > > > > [2]
> > > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
> > > > > >
> > > > > > Regards
> > > > > > Liang
> > > > >
> > > > > 
> -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> >
> >
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

答复: May 2022 Podling Reporting Timeline

2022-04-21 Thread tan zhongyi

brpc also missed the pod report of April.

Maybe we are too used to wait for reminder email from Justin.

Anyway,  I will provide pod report in May if needed.

Thanks.



发件人: Mingshen Sun 
日期: 星期五, 2022年4月22日 上午2:00
收件人: general@incubator.apache.org , 
d...@teaclave.apache.org 
主题: Re: May 2022 Podling Reporting Timeline
Hi all,

I'm from the Teaclave project. I just noticed that we missed April's
report because of the reminder issue.

Should we add it in May's report also? I see some discussions here but
no conclusion yet.

For Teaclave, we have no problem with adding an additional report in May.

Mingshen


On Thu, Apr 21, 2022 at 5:29 AM John D. Ament  wrote:
>
> Hi Christofer
>
> On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
> wrote:
>
> > Hi John,
> >
> > guess I missed the second part of your email ;-)
> >
> > Well, I am a bit unsure if we really should skip the ones that for example
> > missed to submit last month because nobody reminded them, but I think in
> > such a case it would be half a year of information missing. Even if this
> > might not be too useful for the board, I think it's useful to the IPMC.
> >
>
> Basically, I can't (personally) fault a podling for not reporting when no
> reminders were sent out.  We failed to hold up our side of the agreement in
> my mind.  It's great that some podlings still did the work to get a report
> put together.  Perhaps we review those in the past 3 months of missed
> reports and also report them? I'm not sure.
>
>
> >
> > So, I think podlings that missed filling in their parts in the last 3
> > months, should still report this time. But that's just my opinion.
> >
>
> I agree with you, the problem is that every podling (other than new
> podlings possibly) has missed a report (at least from the board's point of
> view).  While there's the main review the IPMC takes on the podlings'
> reports, the board also reviews them.  Since the IPMC lapsed on maintaining
> this, it may end up over burdening the board to put out a report that has
> every single podling reporting in it.
>
>
> >
> > Chris
> >
> > -Original Message-
> > From: Christofer Dutz 
> > Sent: Donnerstag, 21. April 2022 10:42
> > To: general@incubator.apache.org
> > Subject: RE: May 2022 Podling Reporting Timeline
> >
> > I should also add that some projects have failed to submit in the last 3
> > months, so I would add to this list:
> >
> > - brpc
> > - Annotator
> > - Crail
> > - EventMesh
> > - Flagon
> > - Hivemail
> > - InLong
> > - Liminal
> > - Marvin-AI
> > - Milagro
> > - Nemo
> > - Pony Mail
> > - Spot
> > - Teaclave
> > - Wayang
> >
> > So, we're also expecting these projects to report this month.
> >
> > Chris
> >
> > -Original Message-
> > From: John D. Ament 
> > Sent: Mittwoch, 20. April 2022 18:24
> > To: general 
> > Subject: May 2022 Podling Reporting Timeline
> >
> > Note - I'm sending this a week early per procedure as we have some catch
> > up to do.
> >
> > May 2022 Incubator report timeline:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
> >
> > Wed May 04 -- Podling reports due by end of day
> > Sun May 08 -- Shepherd reviews due by end of day
> > Sun May 08 -- Summary due by end of day
> > Tue May 10 -- Mentor signoff due by end of day
> > Wed May 11 -- Report submitted to Board
> > Wed May 18 -- Board meeting
> >
> > According to podlings.xml, the following podlings are expected to report:
> > - Training
> > - Heron
> > - Tuweni
> > - Pagespeed
> > - Toree
> > - Livy
> > - NLPCraft
> > - Sedona
> > - Doris
> > - SDAP
> > - Linkis
> >
> > I'm suggesting that right now we keep the current reporting periods as we
> > the Incubator PMC have failed to report to the Board, rather than it
> > necessarily being a failing of podlings.  If your podling is on this list
> > but isn't present on the confluence page, please add it with the necessary
> > sections.  i'll take a look in the next few days and make sure podlings.xml
> > represents reality.
> >
> > - John, your friendly neighborhood Report Manager
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: May 2022 Podling Reporting Timeline

2022-04-21 Thread Mingshen Sun

Hi all,

I'm from the Teaclave project. I just noticed that we missed April's
report because of the reminder issue.

Should we add it in May's report also? I see some discussions here but
no conclusion yet.

For Teaclave, we have no problem with adding an additional report in May.

Mingshen


On Thu, Apr 21, 2022 at 5:29 AM John D. Ament  wrote:
>
> Hi Christofer
>
> On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
> wrote:
>
> > Hi John,
> >
> > guess I missed the second part of your email ;-)
> >
> > Well, I am a bit unsure if we really should skip the ones that for example
> > missed to submit last month because nobody reminded them, but I think in
> > such a case it would be half a year of information missing. Even if this
> > might not be too useful for the board, I think it's useful to the IPMC.
> >
>
> Basically, I can't (personally) fault a podling for not reporting when no
> reminders were sent out.  We failed to hold up our side of the agreement in
> my mind.  It's great that some podlings still did the work to get a report
> put together.  Perhaps we review those in the past 3 months of missed
> reports and also report them? I'm not sure.
>
>
> >
> > So, I think podlings that missed filling in their parts in the last 3
> > months, should still report this time. But that's just my opinion.
> >
>
> I agree with you, the problem is that every podling (other than new
> podlings possibly) has missed a report (at least from the board's point of
> view).  While there's the main review the IPMC takes on the podlings'
> reports, the board also reviews them.  Since the IPMC lapsed on maintaining
> this, it may end up over burdening the board to put out a report that has
> every single podling reporting in it.
>
>
> >
> > Chris
> >
> > -Original Message-
> > From: Christofer Dutz 
> > Sent: Donnerstag, 21. April 2022 10:42
> > To: general@incubator.apache.org
> > Subject: RE: May 2022 Podling Reporting Timeline
> >
> > I should also add that some projects have failed to submit in the last 3
> > months, so I would add to this list:
> >
> > - brpc
> > - Annotator
> > - Crail
> > - EventMesh
> > - Flagon
> > - Hivemail
> > - InLong
> > - Liminal
> > - Marvin-AI
> > - Milagro
> > - Nemo
> > - Pony Mail
> > - Spot
> > - Teaclave
> > - Wayang
> >
> > So, we're also expecting these projects to report this month.
> >
> > Chris
> >
> > -Original Message-
> > From: John D. Ament 
> > Sent: Mittwoch, 20. April 2022 18:24
> > To: general 
> > Subject: May 2022 Podling Reporting Timeline
> >
> > Note - I'm sending this a week early per procedure as we have some catch
> > up to do.
> >
> > May 2022 Incubator report timeline:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
> >
> > Wed May 04 -- Podling reports due by end of day
> > Sun May 08 -- Shepherd reviews due by end of day
> > Sun May 08 -- Summary due by end of day
> > Tue May 10 -- Mentor signoff due by end of day
> > Wed May 11 -- Report submitted to Board
> > Wed May 18 -- Board meeting
> >
> > According to podlings.xml, the following podlings are expected to report:
> > - Training
> > - Heron
> > - Tuweni
> > - Pagespeed
> > - Toree
> > - Livy
> > - NLPCraft
> > - Sedona
> > - Doris
> > - SDAP
> > - Linkis
> >
> > I'm suggesting that right now we keep the current reporting periods as we
> > the Incubator PMC have failed to report to the Board, rather than it
> > necessarily being a failing of podlings.  If your podling is on this list
> > but isn't present on the confluence page, please add it with the necessary
> > sections.  i'll take a look in the next few days and make sure podlings.xml
> > represents reality.
> >
> > - John, your friendly neighborhood Report Manager
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache InLong(Incubating) 1.1.0-incubating RC0

2022-04-21 Thread Xun Liu

+1 (binding) from me,

I have checked the following items:
- Incubating in name
- LICENSE and NOTICE are fine
- DISCLAIMER-WIP exists
- All links are valid
- No unexpected binary files
- All ASF files have ASF headers
- Can compile from source
  `mvn clean install`
- Checksums and PGP signatures are valid.

Best regards
Xun Liu

On Thu, Apr 21, 2022 at 2:39 PM Goson zhang  wrote:

> Thanks, @Jean-Baptiste Onofre , we will remove the "-WIP"
> tag in the next version after confirming that there are no other issues
> with this release.
>
> We have checked each dependency package by package. From the current review
> results, no CATEGORY X dependency packages in the project.
>
>
> Jean-Baptiste Onofré  于2022年4月20日周三 13:26写道：
>
> > +1 (binding)
> >
> > I checked:
> > - incubating is in the name
> > - Hash and signature are OK
> > - LICENSE and NOTICE are there and OK (NOTICE could be simplified by
> > just mentioning Apache projects in general, not listing all Apache
> > projects like HBase, etc, but that's OK)
> > - DISCLAIMER-WIP is there (I guess it could be renamed to just
> DISCLAIMER)
> > - No binary found in source artifact
> > - ASF headers are present in all source files
> >
> > Regards
> > JB
> >
> > On Wed, Apr 20, 2022 at 5:23 AM dockerzhang 
> > wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache InLong(Incubating)
> > version
> > > 1.1.0-incubating RC0
> > >
> > > The Apache InLong community has voted on and approved a proposal to
> > > release
> > > Apache InLong(Incubating) version 1.1.0-incubating RC0
> > >
> > > We now kindly request the Incubator PMC members review and vote on
> > this
> > > incubator release.
> > >
> > > InLong community vote thread:
> > > • https://lists.apache.org/thread/mtwxgcf2sh4lgohpdo6vk1gkpnwn5qo5
> > >
> > > Vote result thread:
> > > • https://lists.apache.org/thread/hc9bkb37n0sdwmon6pqnvnntszt0vb0n
> > >
> > > The release candidate:
> > > •
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/inlong/1.1.0-incubating-RC0/
> > >
> > > Git tag for the release:
> > > •
> > >
> >
> https://github.com/apache/incubator-inlong/releases/tag/1.1.0-incubating-RC0
> > >
> > > Release notes:
> > > •
> > >
> >
> https://github.com/apache/incubator-inlong/blob/1.1.0-incubating-RC0/CHANGES.md
> > >
> > > The artifacts signed with PGP key A4D4D578, corresponding to
> > > dockerzh...@apache.org, can be found in the keys file:
> > > • https://downloads.apache.org/incubator/inlong/KEYS
> > >
> > > The vote will be open for at least 72 hours or until a necessary
> > number
> > > of votes is reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > > On behalf of Apache InLong(Incubating) community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: May 2022 Podling Reporting Timeline

2022-04-21 Thread John D. Ament

Hi Christofer

On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
wrote:

> Hi John,
>
> guess I missed the second part of your email ;-)
>
> Well, I am a bit unsure if we really should skip the ones that for example
> missed to submit last month because nobody reminded them, but I think in
> such a case it would be half a year of information missing. Even if this
> might not be too useful for the board, I think it's useful to the IPMC.
>

Basically, I can't (personally) fault a podling for not reporting when no
reminders were sent out.  We failed to hold up our side of the agreement in
my mind.  It's great that some podlings still did the work to get a report
put together.  Perhaps we review those in the past 3 months of missed
reports and also report them? I'm not sure.


>
> So, I think podlings that missed filling in their parts in the last 3
> months, should still report this time. But that's just my opinion.
>

I agree with you, the problem is that every podling (other than new
podlings possibly) has missed a report (at least from the board's point of
view).  While there's the main review the IPMC takes on the podlings'
reports, the board also reviews them.  Since the IPMC lapsed on maintaining
this, it may end up over burdening the board to put out a report that has
every single podling reporting in it.


>
> Chris
>
> -Original Message-
> From: Christofer Dutz 
> Sent: Donnerstag, 21. April 2022 10:42
> To: general@incubator.apache.org
> Subject: RE: May 2022 Podling Reporting Timeline
>
> I should also add that some projects have failed to submit in the last 3
> months, so I would add to this list:
>
> - brpc
> - Annotator
> - Crail
> - EventMesh
> - Flagon
> - Hivemail
> - InLong
> - Liminal
> - Marvin-AI
> - Milagro
> - Nemo
> - Pony Mail
> - Spot
> - Teaclave
> - Wayang
>
> So, we're also expecting these projects to report this month.
>
> Chris
>
> -Original Message-
> From: John D. Ament 
> Sent: Mittwoch, 20. April 2022 18:24
> To: general 
> Subject: May 2022 Podling Reporting Timeline
>
> Note - I'm sending this a week early per procedure as we have some catch
> up to do.
>
> May 2022 Incubator report timeline:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
>
> Wed May 04 -- Podling reports due by end of day
> Sun May 08 -- Shepherd reviews due by end of day
> Sun May 08 -- Summary due by end of day
> Tue May 10 -- Mentor signoff due by end of day
> Wed May 11 -- Report submitted to Board
> Wed May 18 -- Board meeting
>
> According to podlings.xml, the following podlings are expected to report:
> - Training
> - Heron
> - Tuweni
> - Pagespeed
> - Toree
> - Livy
> - NLPCraft
> - Sedona
> - Doris
> - SDAP
> - Linkis
>
> I'm suggesting that right now we keep the current reporting periods as we
> the Incubator PMC have failed to report to the Board, rather than it
> necessarily being a failing of podlings.  If your podling is on this list
> but isn't present on the confluence page, please add it with the necessary
> sections.  i'll take a look in the next few days and make sure podlings.xml
> represents reality.
>
> - John, your friendly neighborhood Report Manager
>

RE: May 2022 Podling Reporting Timeline

2022-04-21 Thread Christofer Dutz

Hi John,

guess I missed the second part of your email ;-)

Well, I am a bit unsure if we really should skip the ones that for example 
missed to submit last month because nobody reminded them, but I think in such a 
case it would be half a year of information missing. Even if this might not be 
too useful for the board, I think it's useful to the IPMC.

So, I think podlings that missed filling in their parts in the last 3 months, 
should still report this time. But that's just my opinion.

Chris

-Original Message-
From: Christofer Dutz  
Sent: Donnerstag, 21. April 2022 10:42
To: general@incubator.apache.org
Subject: RE: May 2022 Podling Reporting Timeline

I should also add that some projects have failed to submit in the last 3 
months, so I would add to this list:

- brpc
- Annotator
- Crail
- EventMesh
- Flagon
- Hivemail
- InLong
- Liminal
- Marvin-AI
- Milagro
- Nemo
- Pony Mail
- Spot
- Teaclave
- Wayang

So, we're also expecting these projects to report this month.

Chris

-Original Message-
From: John D. Ament  
Sent: Mittwoch, 20. April 2022 18:24
To: general 
Subject: May 2022 Podling Reporting Timeline

Note - I'm sending this a week early per procedure as we have some catch up to 
do.

May 2022 Incubator report timeline:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2022

Wed May 04 -- Podling reports due by end of day
Sun May 08 -- Shepherd reviews due by end of day
Sun May 08 -- Summary due by end of day
Tue May 10 -- Mentor signoff due by end of day
Wed May 11 -- Report submitted to Board
Wed May 18 -- Board meeting

According to podlings.xml, the following podlings are expected to report:
- Training
- Heron
- Tuweni
- Pagespeed
- Toree
- Livy
- NLPCraft
- Sedona
- Doris
- SDAP
- Linkis

I'm suggesting that right now we keep the current reporting periods as we the 
Incubator PMC have failed to report to the Board, rather than it necessarily 
being a failing of podlings.  If your podling is on this list but isn't present 
on the confluence page, please add it with the necessary sections.  i'll take a 
look in the next few days and make sure podlings.xml represents reality.

- John, your friendly neighborhood Report Manager

RE: May 2022 Podling Reporting Timeline

2022-04-21 Thread Christofer Dutz

I should also add that some projects have failed to submit in the last 3 
months, so I would add to this list:

- brpc
- Annotator
- Crail
- EventMesh
- Flagon
- Hivemail
- InLong
- Liminal
- Marvin-AI
- Milagro
- Nemo
- Pony Mail
- Spot
- Teaclave
- Wayang

So, we're also expecting these projects to report this month.

Chris

-Original Message-
From: John D. Ament  
Sent: Mittwoch, 20. April 2022 18:24
To: general 
Subject: May 2022 Podling Reporting Timeline

Note - I'm sending this a week early per procedure as we have some catch up to 
do.

May 2022 Incubator report timeline:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2022

Wed May 04 -- Podling reports due by end of day
Sun May 08 -- Shepherd reviews due by end of day
Sun May 08 -- Summary due by end of day
Tue May 10 -- Mentor signoff due by end of day
Wed May 11 -- Report submitted to Board
Wed May 18 -- Board meeting

According to podlings.xml, the following podlings are expected to report:
- Training
- Heron
- Tuweni
- Pagespeed
- Toree
- Livy
- NLPCraft
- Sedona
- Doris
- SDAP
- Linkis

I'm suggesting that right now we keep the current reporting periods as we the 
Incubator PMC have failed to report to the Board, rather than it necessarily 
being a failing of podlings.  If your podling is on this list but isn't present 
on the confluence page, please add it with the necessary sections.  i'll take a 
look in the next few days and make sure podlings.xml represents reality.

- John, your friendly neighborhood Report Manager
--- Begin Message ---
I should also add that some projects have failed to submit in the last 3 
months, so I would add to this list:

-

-Original Message-
From: John D. Ament 
Sent: Mittwoch, 20. April 2022 18:24
To: general 
Subject: May 2022 Podling Reporting Timeline

Note - I'm sending this a week early per procedure as we have some catch up to 
do.

May 2022 Incubator report timeline:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2022

Wed May 04 -- Podling reports due by end of day
Sun May 08 -- Shepherd reviews due by end of day
Sun May 08 -- Summary due by end of day
Tue May 10 -- Mentor signoff due by end of day
Wed May 11 -- Report submitted to Board
Wed May 18 -- Board meeting

According to podlings.xml, the following podlings are expected to report:
- Training
- Heron
- Tuweni
- Pagespeed
- Toree
- Livy
- NLPCraft
- Sedona
- Doris
- SDAP
- Linkis

I'm suggesting that right now we keep the current reporting periods as we the 
Incubator PMC have failed to report to the Board, rather than it necessarily 
being a failing of podlings.  If your podling is on this list but isn't present 
on the confluence page, please add it with the necessary sections.  i'll take a 
look in the next few days and make sure podlings.xml represents reality.

- John, your friendly neighborhood Report Manager
--- End Message ---

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

2022-04-21 Thread Alin Jerpelea

Hi Duo Zhang,
In my initial message I missed the following files

apps/interpreters/ficl/src/nuttx.c
apps/interpreters/ficl/src/nuttx.h
apps/interpreters/minibasic/basic.c
apps/interpreters/minibasic/script.c
apps/include/interpreters/minibasic.h
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L244

apps/include/modbus/mb.h
apps/include/modbus/mb_m.h
apps/include/modbus/mbframe.h
apps/include/modbus/mbfunc.h
apps/include/modbus/mbport.h
apps/include/modbus/mbproto.h
apps/include/modbus/mbutils.h
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L214

apps/include/netutils/dhcpc.h
apps/include/netutils/dhcpd.h
apps/include/netutils/httpd.h
apps/include/netutils/netlib.h
apps/include/netutils/smtp.h
apps/include/netutils/webclient.h
apps/netutils/webserver/httpd.c
apps/netutils/webserver/httpd_cgi.c
apps/netutils/webserver/httpd_fs.c
apps/netutils/webserver/httpd.h
apps/netutils/webserver/httpd_cgi.h
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L205

apps/graphics/nxwidgets/doc/mainpage.h
this file should be ignored

all remaining files are fixed in the following commits
https://github.com/apache/incubator-nuttx-apps/pull/1146

Best regards
Alin


On 2022/04/21 06:57:37 Alin Jerpelea wrote:
> Hi Duo Zhang, 
> 
> thanks for sharing the list of files. Here are several files reported as 
> missing that can be found in the LICENSE file. I will contribute today the 
> missing ones
> 
> apps/canutils/candump/candump.c
> apps/canutils/cansend/cansend.c
> apps/canutils/libcanutils/lib.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L547
> 
> apps/examples/canard/canard_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L748
> 
> apps/examples/chat/chat_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L780
> 
> apps/examples/lis3dsh_reader/lis3dsh_reader_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L839
> 
> apps/examples/mlx90614/mlx90614_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L871
> 
> apps/examples/modbusmaster/mbmaster_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L904
> 
> apps/examples/pppd/pppd_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L310
> 
> apps/examples/telnetd/telnetd.c
> apps/examples/webserver/cgi.c
> apps/examples/webserver/webserver_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L933
> 
> apps/examples/xbc_test/xbc_test_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L964
> 
> apps/examples/xmlrpc/calls.c
> apps/examples/xmlrpc/xmlrpc_main.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L997
> 
> apps/gpsutils/minmea/minmea.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L714
> 
> apps/interpreters/bas/bas_token.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L523
> 
> apps/modbus/mb.c
> apps/modbus/mb_m.c
> apps/modbus/ascii/mbascii.c
> apps/modbus/functions/mbfunccoils.c
> apps/modbus/functions/mbfunccoils_m.c
> apps/modbus/functions/mbfuncdiag.c
> apps/modbus/functions/mbfuncdisc.c
> apps/modbus/functions/mbfuncdisc_m.c
> apps/modbus/functions/mbfuncholding.c
> apps/modbus/functions/mbfuncholding_m.c
> apps/modbus/functions/mbfuncinput.c
> apps/modbus/functions/mbfuncinput_m.c
> apps/modbus/functions/mbfuncother.c
> apps/modbus/functions/mbutils.c
> apps/modbus/nuttx/portevent.c
> apps/modbus/nuttx/portevent_m.c
> apps/modbus/nuttx/portother.c
> apps/modbus/nuttx/portother_m.c
> apps/modbus/nuttx/portserial.c
> apps/modbus/nuttx/portserial_m.c
> apps/modbus/nuttx/porttimer.c
> apps/modbus/nuttx/porttimer_m.c
> apps/modbus/rtu/mbcrc.c
> apps/modbus/rtu/mbrtu.c
> apps/modbus/rtu/mbrtu_m.c
> apps/modbus/tcp/mbtcp.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L214
> 
> 
> apps/netutils/codecs/base64.c
> apps/netutils/codecs/md5.c
> apps/netutils/codecs/urldecode.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1037
> 
> apps/netutils/dhcpc/dhcpc.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1090
> 
> apps/netutils/ftpd/ftpd.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1126
> 
> apps/netutils/netlib/netlib_ethaddrconv.c
> apps/netutils/netlib/netlib_ipv4addrconv.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1164
> 
> apps/netutils/pppd/ahdlc.c
> apps/netutils/pppd/ipcp.c
> apps/netutils/pppd/lcp.c
> apps/netutils/pppd/pap.c
> apps/netutils/pppd/ppp.c
> apps/netutils/pppd/pppd.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L310
> 
> apps/netutils/smtp/smtp.c
> https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1166
> 
> apps/netutils/thttpd/fdwatch.c
> apps/netutils/thttpd/libhttpd.c
> apps/netutils/thttpd/tdate_parse.c
> apps/netutils/thttpd/thttpd.c
>

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

2022-04-21 Thread Alin Jerpelea

Hi Duo Zhang, 

thanks for sharing the list of files. Here are several files reported as 
missing that can be found in the LICENSE file. I will contribute today the 
missing ones

apps/canutils/candump/candump.c
apps/canutils/cansend/cansend.c
apps/canutils/libcanutils/lib.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L547

apps/examples/canard/canard_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L748

apps/examples/chat/chat_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L780

apps/examples/lis3dsh_reader/lis3dsh_reader_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L839

apps/examples/mlx90614/mlx90614_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L871

apps/examples/modbusmaster/mbmaster_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L904

apps/examples/pppd/pppd_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L310

apps/examples/telnetd/telnetd.c
apps/examples/webserver/cgi.c
apps/examples/webserver/webserver_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L933

apps/examples/xbc_test/xbc_test_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L964

apps/examples/xmlrpc/calls.c
apps/examples/xmlrpc/xmlrpc_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L997

apps/gpsutils/minmea/minmea.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L714

apps/interpreters/bas/bas_token.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L523

apps/modbus/mb.c
apps/modbus/mb_m.c
apps/modbus/ascii/mbascii.c
apps/modbus/functions/mbfunccoils.c
apps/modbus/functions/mbfunccoils_m.c
apps/modbus/functions/mbfuncdiag.c
apps/modbus/functions/mbfuncdisc.c
apps/modbus/functions/mbfuncdisc_m.c
apps/modbus/functions/mbfuncholding.c
apps/modbus/functions/mbfuncholding_m.c
apps/modbus/functions/mbfuncinput.c
apps/modbus/functions/mbfuncinput_m.c
apps/modbus/functions/mbfuncother.c
apps/modbus/functions/mbutils.c
apps/modbus/nuttx/portevent.c
apps/modbus/nuttx/portevent_m.c
apps/modbus/nuttx/portother.c
apps/modbus/nuttx/portother_m.c
apps/modbus/nuttx/portserial.c
apps/modbus/nuttx/portserial_m.c
apps/modbus/nuttx/porttimer.c
apps/modbus/nuttx/porttimer_m.c
apps/modbus/rtu/mbcrc.c
apps/modbus/rtu/mbrtu.c
apps/modbus/rtu/mbrtu_m.c
apps/modbus/tcp/mbtcp.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L214


apps/netutils/codecs/base64.c
apps/netutils/codecs/md5.c
apps/netutils/codecs/urldecode.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1037

apps/netutils/dhcpc/dhcpc.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1090

apps/netutils/ftpd/ftpd.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1126

apps/netutils/netlib/netlib_ethaddrconv.c
apps/netutils/netlib/netlib_ipv4addrconv.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1164

apps/netutils/pppd/ahdlc.c
apps/netutils/pppd/ipcp.c
apps/netutils/pppd/lcp.c
apps/netutils/pppd/pap.c
apps/netutils/pppd/ppp.c
apps/netutils/pppd/pppd.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L310

apps/netutils/smtp/smtp.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1166

apps/netutils/thttpd/fdwatch.c
apps/netutils/thttpd/libhttpd.c
apps/netutils/thttpd/tdate_parse.c
apps/netutils/thttpd/thttpd.c
apps/netutils/thttpd/thttpd_cgi.c
apps/netutils/thttpd/thttpd_strings.c
apps/netutils/thttpd/timers.c
apps/netutils/thttpd/cgi-src/phf.c
apps/netutils/thttpd/cgi-src/redirect.c
apps/netutils/thttpd/cgi-src/ssi.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1204

apps/netutils/webclient/webclient.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L1167


apps/netutils/xmlrpc/response.c
apps/netutils/xmlrpc/xmlparser.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L997


apps/system/cu/cu_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L624

apps/system/hexed/src/bfile.c
apps/system/hexed/src/cmdargs.c
apps/system/hexed/src/hexcopy.c
apps/system/hexed/src/hexdump.c
apps/system/hexed/src/hexed.c
apps/system/hexed/src/hexenter.c
apps/system/hexed/src/hexhelp.c
apps/system/hexed/src/hexinsert.c
apps/system/hexed/src/hexmove.c
apps/system/hexed/src/hexremove.c
apps/system/hexed/src/hexword.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L657

apps/system/lzf/lzf_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L688

apps/testing/scanftest/scanftest_main.c
https://github.com/apache/incubator-nuttx-apps/blob/master/LICENSE#L351

apps/wireless/wapi/src/driver_wext.c
apps/wireless/wapi/src/network.c
apps/wireless/wapi/src/util.c
apps/wireless/wapi/src/wapi.c
apps/wireless/wapi/src/wireless.c

Re: [VOTE] Release Apache InLong(Incubating) 1.1.0-incubating RC0

2022-04-21 Thread Goson zhang

Thanks, @Jean-Baptiste Onofre , we will remove the "-WIP"
tag in the next version after confirming that there are no other issues
with this release.

We have checked each dependency package by package. From the current review
results, no CATEGORY X dependency packages in the project.


Jean-Baptiste Onofré  于2022年4月20日周三 13:26写道：

> +1 (binding)
>
> I checked:
> - incubating is in the name
> - Hash and signature are OK
> - LICENSE and NOTICE are there and OK (NOTICE could be simplified by
> just mentioning Apache projects in general, not listing all Apache
> projects like HBase, etc, but that's OK)
> - DISCLAIMER-WIP is there (I guess it could be renamed to just DISCLAIMER)
> - No binary found in source artifact
> - ASF headers are present in all source files
>
> Regards
> JB
>
> On Wed, Apr 20, 2022 at 5:23 AM dockerzhang 
> wrote:
> >
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache InLong(Incubating)
> version
> > 1.1.0-incubating RC0
> >
> > The Apache InLong community has voted on and approved a proposal to
> > release
> > Apache InLong(Incubating) version 1.1.0-incubating RC0
> >
> > We now kindly request the Incubator PMC members review and vote on
> this
> > incubator release.
> >
> > InLong community vote thread:
> > • https://lists.apache.org/thread/mtwxgcf2sh4lgohpdo6vk1gkpnwn5qo5
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/hc9bkb37n0sdwmon6pqnvnntszt0vb0n
> >
> > The release candidate:
> > •
> >
> https://dist.apache.org/repos/dist/dev/incubator/inlong/1.1.0-incubating-RC0/
> >
> > Git tag for the release:
> > •
> >
> https://github.com/apache/incubator-inlong/releases/tag/1.1.0-incubating-RC0
> >
> > Release notes:
> > •
> >
> https://github.com/apache/incubator-inlong/blob/1.1.0-incubating-RC0/CHANGES.md
> >
> > The artifacts signed with PGP key A4D4D578, corresponding to
> > dockerzh...@apache.org, can be found in the keys file:
> > • https://downloads.apache.org/incubator/inlong/KEYS
> >
> > The vote will be open for at least 72 hours or until a necessary
> number
> > of votes is reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache InLong(Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Incubating Proposal of DevLake

2022-04-21 Thread Hezheng Yin

Hi JB,

Thanks for your interests in DevLake. One key difference between DevLake and 
Gobblin/NiFi is that Gobblin/NiFi are domain agnostic general frameworks while 
DevLake specializes in the domain of software development data. This focus 
allows DevLake to better “understand” the data that it ingests, cleanses, 
transforms, analyzes, and visualizes for developers. At the foundation of this 
understanding is DevLake’s data 
model 
built on top of the software development process. We’ll keep expanding this 
model as DevLake supports new DevOps tools (data sources) requested by the 
community. If you have any other question or suggestion, please let us know. 
Any feedback is greatly appreciated!

Best,
Hezheng
Maintainer of DevLake

From: Jean-Baptiste Onofré 
Date: Monday, April 18, 2022 at 7:23 AM
To: general@incubator.apache.org 
Subject: Re: [DISCUSS] Incubating Proposal of DevLake
Thanks, it helps !

Regards
JB

On Mon, Apr 18, 2022 at 4:14 PM Willem Jiang  wrote:
>
> Hi JB
>
> You may find the information about the DevOps data collection here[1]
> There are some domain related entities schema[2] which are built on
> top of the development process.
>
> [1]https://github.com/merico-dev/lake/blob/main/ARCHITECTURE.md
> [2]https://github.com/merico-dev/lake/wiki/DataModel.Domain-layer-schema
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Apr 17, 2022 at 12:14 AM Jean-Baptiste Onofré  
> wrote:
> >
> > Hi Willem,
> >
> > It looks interesting. I took a look on github repo. I don't see the
> > relation between DevOps and data collection/ETL part mentioned on the
> > README.
> >
> > For the data collection/ETL framework, it sounds similar to
> > Gobblin/NiFi, etc. The DevOps part is more interesting IMHO. I have to
> > dig into this.
> >
> > Regards
> > JB
> >
> > On Thu, Apr 7, 2022 at 10:20 AM Willem Jiang  wrote:
> > >
> > > We want to propose  DevLake[1]  as a new Apache Incubator project.
> > >
> > > DevLake helps developer teams integrate and analyze software
> > > development data throughout the software development life cycle
> > > (SDLC).
> > > Specifically, DevLake provides:
> > >
> > > * High-quality connectors that integrate data from various DevOps tools;
> > > * A comprehensive and unified data model and metrics that enable
> > > developers to easily query data and answer questions regarding their
> > > development process;
> > > * A plugin system that allows customizable data connectors and enrichers;
> > > * An unified ETL management module that orchestrates data collection
> > > and analysis.
> > >
> > > I'd be happy to be the Champion of this project and many thanks to
> > > Liang Zhang (zhangliang at apache dot org)，Lidong Dai (lidongdai at apache
> > > dot org)，Sijie Guo (sijie at apache dot org） for being the mentor of  
> > > DevLake
> > > project and helping us to polish the incubating proposal[2].
> > >
> > > Looking forward to your feedback and thank you very much.
> > >
> > > [1]https://github.com/merico-dev/lake
> > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: May 2022 Podling Reporting Timeline

Re: [DISCUSS] Incubating Proposal of DevLake

Re: [VOTE] Accept Kvrocks into the Apache Incubator

Re: [VOTE] Accept Kvrocks into the Apache Incubator

Re: May 2022 Podling Reporting Timeline

Re: [VOTE] Accept Kvrocks into the Apache Incubator

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

[ANNOUNCE] Apache Kyuubi (Incubating) released 1.5.1-incubating

Re: [VOTE] Accept Kvrocks into the Apache Incubator

答复: May 2022 Podling Reporting Timeline

Re: May 2022 Podling Reporting Timeline

Re: [VOTE] Release Apache InLong(Incubating) 1.1.0-incubating RC0

Re: May 2022 Podling Reporting Timeline

RE: May 2022 Podling Reporting Timeline

RE: May 2022 Podling Reporting Timeline

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

Re: [VOTE] Release Apache InLong(Incubating) 1.1.0-incubating RC0

Re: [DISCUSS] Incubating Proposal of DevLake

19 matches

Site Navigation

Mail list logo

Footer information