Re: May 2022 Podling Reporting Timeline
If most podlings are OK submitting a report and the board will be OK reading such a long report I see no issue requesting every podling to report, and just marking those that fail as monthly until they do (with a caveat that other than marking them monthly there's no problem with them failing to report). It saves me time trying to sort out who should and shouldn't be reporting. John On Fri, Apr 22, 2022 at 8:01 AM Willem Jiang wrote: > +1 for projects to send their reports. > We may need to add more Shepherds to highlight the information of > podling reports. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Apr 22, 2022 at 1:19 PM Christofer Dutz > wrote: > > > > 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<https://aka.ms/AAb9ysg> > > ____________ > > 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 < > christofer.d...@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 > > > 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 > > >
Re: May 2022 Podling Reporting Timeline
+1 for projects to send their reports. We may need to add more Shepherds to highlight the information of podling reports. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Apr 22, 2022 at 1:19 PM Christofer Dutz wrote: > > 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<https://aka.ms/AAb9ysg> > > 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 > > - 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
Hi, Milagro too - we will also add ours to the May report. Regards, John McCane-Whitney > -Original Message- > From: Eason Chen > Sent: 22 April 2022 04:04 > To: general > Cc: d...@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 > 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: > > >
Re: May 2022 Podling Reporting Timeline
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<https://aka.ms/AAb9ysg> 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: 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 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: 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
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
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
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
