You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by tan zhongyi <zh...@gmail.com> on 2022/04/22 00:37:49 UTC
答复: May 2022 Podling Reporting Timeline
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 <ms...@apache.org>
日期: 星期五, 2022年4月22日 上午2:00
收件人: general@incubator.apache.org <ge...@incubator.apache.org>, dev@teaclave.apache.org <de...@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 <jo...@apache.org> wrote:
>
> Hi Christofer
>
> On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz <ch...@c-ware.de>
> 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 <ch...@c-ware.de>
> > 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 <jo...@apache.org>
> > Sent: Mittwoch, 20. April 2022 18:24
> > To: general <ge...@incubator.apache.org>
> > 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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: May 2022 Podling Reporting Timeline
Posted by John McCane-Whitney <jo...@qredo.com.INVALID>.
Hi,
Milagro too - we will also add ours to the May report.
Regards,
John McCane-Whitney
> -----Original Message-----
> From: Eason Chen <ch...@apache.org>
> Sent: 22 April 2022 04:04
> To: general <ge...@incubator.apache.org>
> Cc: dev@eventmesh.apache.org
> Subject: Re: May 2022 Podling Reporting Timeline
>
> EventMesh also missed for not receiving reminder email, we will add it later.
>
> On Fri, Apr 22, 2022 at 8:38 AM tan zhongyi <zh...@gmail.com>
> 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 <ms...@apache.org>
> > 日期: 星期五, 2022年4月22日 上午2:00
> > 收件人: general@incubator.apache.org <ge...@incubator.apache.org>,
> > dev@teaclave.apache.org <de...@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
> <jo...@apache.org> wrote:
> > >
> > > Hi Christofer
> > >
> > > On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz
> > > <ch...@c-ware.de>
> > > 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 <ch...@c-ware.de>
> > > > 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 <jo...@apache.org>
> > > > Sent: Mittwoch, 20. April 2022 18:24
> > > > To: general <ge...@incubator.apache.org>
> > > > 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-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
RE: May 2022 Podling Reporting Timeline
Posted by John McCane-Whitney <jo...@qredo.com.INVALID>.
Hi,
Milagro too - we will also add ours to the May report.
Regards,
John McCane-Whitney
> -----Original Message-----
> From: Eason Chen <ch...@apache.org>
> Sent: 22 April 2022 04:04
> To: general <ge...@incubator.apache.org>
> Cc: dev@eventmesh.apache.org
> Subject: Re: May 2022 Podling Reporting Timeline
>
> EventMesh also missed for not receiving reminder email, we will add it later.
>
> On Fri, Apr 22, 2022 at 8:38 AM tan zhongyi <zh...@gmail.com>
> 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 <ms...@apache.org>
> > 日期: 星期五, 2022年4月22日 上午2:00
> > 收件人: general@incubator.apache.org <ge...@incubator.apache.org>,
> > dev@teaclave.apache.org <de...@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
> <jo...@apache.org> wrote:
> > >
> > > Hi Christofer
> > >
> > > On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz
> > > <ch...@c-ware.de>
> > > 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 <ch...@c-ware.de>
> > > > 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 <jo...@apache.org>
> > > > Sent: Mittwoch, 20. April 2022 18:24
> > > > To: general <ge...@incubator.apache.org>
> > > > 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-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
Re: May 2022 Podling Reporting Timeline
Posted by Eason Chen <ch...@apache.org>.
EventMesh also missed for not receiving reminder email, we will add it later.
On Fri, Apr 22, 2022 at 8:38 AM tan zhongyi <zh...@gmail.com> 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 <ms...@apache.org>
> 日期: 星期五, 2022年4月22日 上午2:00
> 收件人: general@incubator.apache.org <ge...@incubator.apache.org>, dev@teaclave.apache.org <de...@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 <jo...@apache.org> wrote:
> >
> > Hi Christofer
> >
> > On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz <ch...@c-ware.de>
> > 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 <ch...@c-ware.de>
> > > 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 <jo...@apache.org>
> > > Sent: Mittwoch, 20. April 2022 18:24
> > > To: general <ge...@incubator.apache.org>
> > > 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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
Re: May 2022 Podling Reporting Timeline
Posted by Eason Chen <ch...@apache.org>.
EventMesh also missed for not receiving reminder email, we will add it later.
On Fri, Apr 22, 2022 at 8:38 AM tan zhongyi <zh...@gmail.com> 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 <ms...@apache.org>
> 日期: 星期五, 2022年4月22日 上午2:00
> 收件人: general@incubator.apache.org <ge...@incubator.apache.org>, dev@teaclave.apache.org <de...@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 <jo...@apache.org> wrote:
> >
> > Hi Christofer
> >
> > On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz <ch...@c-ware.de>
> > 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 <ch...@c-ware.de>
> > > 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 <jo...@apache.org>
> > > Sent: Mittwoch, 20. April 2022 18:24
> > > To: general <ge...@incubator.apache.org>
> > > 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-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org