Re: [DISCUSS] Retire Livy podling

2022-10-14 Thread Bikas Saha
iew/commit the code. Any thoughts on solutions for that? Bikas From: larry mccay Sent: Friday, October 14, 2022 6:51 AM To: general@incubator.apache.org Subject: Re: [DISCUSS] Retire Livy podling I have a simplified proposal nearly ready to send. Since there w

Re: [DISCUSS] Retire Livy podling

2022-10-14 Thread larry mccay
I have a simplified proposal nearly ready to send. Since there weren't any requirements for it provided here it is just declaring the intent and new members from this thread and my employer. If there is anything else you'd like to see in it just let me know. On Fri, Oct 14, 2022, 9:46 AM

Re: [DISCUSS] Retire Livy podling

2022-10-14 Thread Jean-Baptiste Onofré
There's no need to reestablished the podling as it's still running ;) I think we can just update the original proposal, reshape the PPMC and move forward. Thoughts ? Regards JB On Fri, Oct 14, 2022 at 9:55 AM Brahma Reddy Battula wrote: > > Hi Justin, > > Any chance to re-establish podding or

Re: [DISCUSS] Retire Livy podling

2022-10-14 Thread Brahma Reddy Battula
Hi Justin, Any chance to re-establish podding or add some members to existing community so that it can be active ,as we can see so many people are interested to contribute to Livy podling? On Thu, 13 Oct 2022 at 10:02 PM, Justin Mclean wrote: > Hi, > > Just a note, poddlings do not go to the

Re: [DISCUSS] Retire Livy podling

2022-10-13 Thread Justin Mclean
Hi, Just a note, poddlings do not go to the attic, only top level projects do. Most often a podling in this state will continue to live on GitHub as long as there is a community to support it. Kind Regards, Justin - To

Re: [DISCUSS] Retire Livy podling

2022-10-10 Thread 严细浪
Thank you Larry. We are from Shopee, I lead the Spark team here. I have several team members participant in Livy development, but most finished feature are done by me and my colleague Jianzhen, information as follows: Xilang Yan, xilang@gmail.com, Shopee Jianzhen Wu, myjianz...@gmail.com,

Re: [DISCUSS] Retire Livy podling

2022-10-10 Thread larry mccay
Exciting to see interest growing! I think rather than try and gather all of these things now, we follow up the proposal with a roadmap discussion. Just as we often entertain new committers during the proposal consideration we can do that then as well. If you'd like to provide your names and

Re: [DISCUSS] Retire Livy podling

2022-10-10 Thread 严细浪
So glad to see there is new progress on Livy community. We have a huge Livy cluster on our prod environment with nearly one million Spark applications submitted everyday, currently we have to maintain Livy ourselves. Some common features we finished: Livy rest cluster, I engaged in the Livy

Re: [DISCUSS] Retire Livy podling

2022-10-10 Thread Jean-Baptiste Onofré
Hi, If you plan to contribute on Livy, you are welcome to be part of the proposal imho. Regards JB On Mon, Oct 10, 2022 at 7:19 AM Brahma Reddy Battula wrote: > > Hi Larry, > > Nice to hear from you that you are planning propose new features and make > active. > > We do use Livy in our prod

Re: [DISCUSS] Retire Livy podling

2022-10-09 Thread Brahma Reddy Battula
Hi Larry, Nice to hear from you that you are planning propose new features and make active. We do use Livy in our prod clusters, any chance to include us in your proposal so that we can also contribute. On Mon, 10 Oct 2022 at 3:54 AM, larry mccay wrote: > Sure. > Thanks, Craig. > > --larry

Re: [DISCUSS] Retire Livy podling

2022-10-09 Thread larry mccay
Sure. Thanks, Craig. --larry On Sun, Oct 9, 2022, 5:38 PM Craig Russell wrote: > Hi Larry, > > > On Oct 8, 2022, at 10:30, larry mccay wrote: > > > > Good to hear, Jean-Baptiste! > > We will send the proposal both here and to the Livy private list, I > guess. > > Once we come to an agreement

Re: [DISCUSS] Retire Livy podling

2022-10-09 Thread Craig Russell
Hi Larry, > On Oct 8, 2022, at 10:30, larry mccay wrote: > > Good to hear, Jean-Baptiste! > We will send the proposal both here and to the Livy private list, I guess. > Once we come to an agreement and direction we can share with the dev@ and > user@ lists. I support the effort to revive the

Re: [DISCUSS] Retire Livy podling

2022-10-08 Thread larry mccay
Good to hear, Jean-Baptiste! We will send the proposal both here and to the Livy private list, I guess. Once we come to an agreement and direction we can share with the dev@ and user@ lists. Thanks again! --larry On Sat, Oct 8, 2022 at 12:49 AM Jean-Baptiste Onofré wrote: > Hi Larry, > >

Re: [DISCUSS] Retire Livy podling

2022-10-07 Thread Jean-Baptiste Onofré
Hi Larry, Agree with Claude: if we can have concrete proposal (in terms of community and roadmap), it's OK. We are not in a rush, if we can have this in the commit weeks, it's fine. I would sent this on the Livy mailing list. Again, I would be more than happy to help and contribute on Livy.

Re: [DISCUSS] Retire Livy podling

2022-10-07 Thread larry mccay
I was hoping that we could bring a set of contributors as: * mentors - 1 or 2 plus whoever wants to remain * PPMC/Committers - 2 or 3 plus whoever wants to remain * election of a PPMC chair if needed Also open it up for folks to ask to join (as well as go emeritus) as I know there are others

Re: [DISCUSS] Retire Livy podling

2022-10-07 Thread Claude Warren, Jr
Larry et.al. I think we need concrete steps. So if Larry produced a list of new committers could we get them added to the list and see if development starts again? Mentors / Champion does that work for you? Larry, can you produce such a list? Is there an objection to proceeding along these

Re: [DISCUSS] Retire Livy podling

2022-10-07 Thread Jean-Baptiste Onofré
Hi Larry, I tried maybe 3 times to get Livy back to active, without success. I was a volunteer to contribute, but not alone, we need a community around Livy. I don't remember having seen new active contributions on the mailing list, and very limited on source code. If you really think we can

Re: [DISCUSS] Retire Livy podling

2022-10-06 Thread larry mccay
Folks, As I mentioned in a previous thread [1], I would like to help avoid sending a well regarded, actively consumed and mature product to the attic. There have been discussions internally at my employer and we have also struggled getting our contributions committed. The original group of

Re: [DISCUSS] Retire Livy podling

2022-10-06 Thread Luciano Resende
Based on the failed attempts to resurrect a community, +1 for retirement. On Wed, Oct 5, 2022 at 07:26 Jean-Baptiste Onofré wrote: > Hi guys, > > After several attempts, we are struggling to execute Livy podling: the > activity is pretty low, and even after a couple of calls for action, > we

Re: [DISCUSS] Retire Livy podling

2022-10-06 Thread david zollo
hi, There are no activities for the Livy community. +1 for the retire Best Regards --- Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC David Linkedin: https://www.linkedin.com/in/davidzollo Twitter: @WorkflowEasy --- On

Re: [DISCUSS] Retire Livy podling

2022-10-05 Thread Calvin Kirs
Hi. The project has been depressed since 2021, with basically no commits since, no activity on the mailing list, and a lot of missed reports, despite JB's attempts to revive the community, but to no avail. So I think it's time for Livy to retire. On Wed, Oct 5, 2022 at 8:26 PM Jean-Baptiste

[DISCUSS] Retire Livy podling

2022-10-05 Thread Jean-Baptiste Onofré
Hi guys, After several attempts, we are struggling to execute Livy podling: the activity is pretty low, and even after a couple of calls for action, we don't have a clear sign of community around Livy. I would like to discuss/propose to retire the Livy podling. Thoughts ? Regards JB