Hi Edward - The Livy community has had a couple attempts at reboot over the years. The most recent one is currently working through both: graduation and the 0.9.0 release at the moment. Your dependency upgrade pull request is certainly welcome and I will make sure to check it out.
Please stay engaged at the project level and we will track your continued interest in its success as well as note your interest in committership. thanks! --larry [on-behalf-of the the Livy PPMC] On Thu, Jan 15, 2026 at 6:13 PM PJ Fanning <[email protected]> wrote: > The Incubator PMC has no say in who gets to commit in the Livy project. > It is up to the Livy PPMC. There is no point in continuing to ask the > Incubator PMC to make you a Livy committer. > > There is a question about whether the Livy PPMC is viable but the way > the rules work, the Incubator PMC can only encourage the Livy PPMC or > if the PPMC is unresponsive, we may need to seek to retire the podling > altogether. > > On Thu, 15 Jan 2026 at 22:34, Edward Capriolo <[email protected]> > wrote: > > > > I know all the path to become a committer stuff. and the "meritocracy > > stuff" > > > > https://github.com/apache/incubator-livy/pull/506 > > > > https://github.com/apache/incubator-livy/pull/505 > > > > https://github.com/apache/incubator-livy/pull/476/files > > > > https://github.com/apache/incubator-livy/pull/475/files > > > > > https://issues.apache.org/jira/projects/LIVY/issues/LIVY-1028?filter=allopenissues&orderby=assignee+ASC%2C+priority+DESC%2C+updated+DESC > > > > > > > > > > ^ This is just some of my attempts. I have gone about 1-7. When i have > time > > the build bot is broken, when I have time the build bot works, no one > seems > > to be around to merge. I mean at this point 5 years in the incubator. It > is > > all very difficult, I cant figure out. The crew have spoke to me at times > > or merge some of my issues, but the problem of sending PR and I never > know > > if someone wans to engage doesnt help me "scratch the itch" > > > > > > https://github.com/apache/incubator-livy/graphs/code-frequency > > > > The code fequence is dropping off to nothing. I*'m an able body that > wants > > to review and merge things. * > > > > On Wed, Jan 14, 2026 at 2:55 PM PJ Fanning <[email protected]> wrote: > > > > > I've added [email protected]. The Livy PPMC are the ones who decide > > > on who gets added as a committer to their project. > > > Generally, you don't need to be a committer to raise PRs and comment > > > on issues. Being made a committer usually follows later and requires > > > the team to discuss and vote on the candidate - and this typically > > > involves analysing their previous contributions to that project. > > > The standard practice is described here: > > > https://community.apache.org/pmc/adding-committers.html > > > > > > On Wed, 14 Jan 2026 at 20:37, Edward Capriolo <[email protected]> > > > wrote: > > > > > > > > Hello all, > > > > > > > > I run lots of apache open source on environments where there is > intense > > > > scrutiny on "OSS vulnerabilities' . While "remediating oss > > > vulnerabilities" > > > > sounds really sophisticated it is usually nothing more than updating > a > > > > version in a pom and fixing whatever breaks as a result. > > > > > > > > https://livy.apache.org/ has been in the incubator since I would > suppose > > > > > > > > Copyright © 2017 The Apache Software Foundation < > http://www.apache.org>. > > > > > > > > I am a hive committer ages ago, and I am actively doing Hadoop stuff > > > > > > > > https://issues.apache.org/jira/browse/HADOOP-19758 > > > > > > > > I dont claim to know everything about livy, but as i mentioned I am > smart > > > > enough to change poms and get the vulnerabilities patched up > > > > > > > > https://issues.apache.org/jira/browse/LIVY-1029 > > > > > > > > I will also review and help others where my skill allows. Can you > > > consider > > > > adding me the the committer role so I can punch through some basic > stuff. > > > > > > > > Thanks, > > > > Edward > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
