Re: Podling Warble Report Reminder - December 2019
+1 On 1/5/20 9:23 PM, Chris Lambertus wrote: It is the mentor’s recommendation that the Warble project be shelved due to lack of interest and momentum. The code will revert to infrastructure and the podling removed. If there is renewed interest at some point in the future, Infra will return the code to the podling. I’ll leave this topic open for 7 days (until 12 Jan) for comment. If there are no dissenting opinions, I’ll notify the incubator of the cessation of warble as a podling at that time. On Dec 12, 2019, at 5:56 PM, Justin Mclean wrote: Hi, we are effectively on hold while we figure out priorities. I understand that but the incubator (and board) expects quarterly reports from all podlings. I guess I could ask for an exception from you. So that way you don't have to report next month. Or you could just move this to GitHub and come back when you ready? Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org
Re: Podling Warble Report Reminder - December 2019
It is the mentor’s recommendation that the Warble project be shelved due to lack of interest and momentum. The code will revert to infrastructure and the podling removed. If there is renewed interest at some point in the future, Infra will return the code to the podling. I’ll leave this topic open for 7 days (until 12 Jan) for comment. If there are no dissenting opinions, I’ll notify the incubator of the cessation of warble as a podling at that time. > On Dec 12, 2019, at 5:56 PM, Justin Mclean wrote: > > Hi, > >> we are effectively on hold while we figure out priorities. > > I understand that but the incubator (and board) expects quarterly reports > from all podlings. I guess I could ask for an exception from you. So that way > you don't have to report next month. > > Or you could just move this to GitHub and come back when you ready? > > Thanks, > Justin > > - > To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org > For additional commands, e-mail: dev-h...@warble.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org
Re: Podling Warble Report Reminder - December 2019
Hi, > we are effectively on hold while we figure out priorities. I understand that but the incubator (and board) expects quarterly reports from all podlings. I guess I could ask for an exception from you. So that way you don't have to report next month. Or you could just move this to GitHub and come back when you ready? Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org
Re: Podling Warble Report Reminder - December 2019
Hi Justin, we are effectively on hold while we figure out priorities. Just not enough cycles as is. On 02/12/2019 22.16, Justin Mclean wrote: Hi, Given the lack of activity in the project perhaps it best to put the project on hold or retire it? Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org
Re: Podling Warble Report Reminder - December 2019
Hi, Given the lack of activity in the project perhaps it best to put the project on hold or retire it? Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@warble.apache.org For additional commands, e-mail: dev-h...@warble.apache.org
