Hi I think we are good to start a vote in the podling, and then a discussion on the incubator general@ mailing list.
I checked some prerequisite: - website is OK (https://whimsy.apache.org/pods/project/livy) - name is OK - maybe an update on the podling file (to avoid the "red" part https://whimsy.apache.org/roster/ppmc/livy) is welcome I agree to start podling vote and discussion on incubator general@. Regards JB On Fri, Jan 30, 2026 at 5:29 PM larry mccay <[email protected]> wrote: > I think that we agreed above that the existing mentions of Livy in the > wild can be a post-graduation discussion. > > What is needed from the Livy team in order to bring graduation to the IPMC > at this point? > Do we need to put together some proposal for graduation? > > On Sun, Jan 18, 2026 at 3:53 PM Justin Mclean <[email protected]> > wrote: > >> HI, >> >> > Not sure Mapr is even a thing anymore and no actively for 9 years on >> that fork. >> >> If the project can get the name change or a clear disclaimer added that >> this is not Apache Livy that would be best. >> >> > Microsoft does reference Apache Livy docs at least. >> >> As a link to another document. The first and most prominent use needs to >> be "Apache Livy", ideally with a TM symbol and a trademark attribution at >> the bottom of the page. >> >> > Question about repo names - if they aren't forks of the actual project, >> do they really have to name it to align with Apache Livy? >> >> Not in the way that they have there. In general, third-party software or >> repository names should not incorporate Apache product names. If they do, >> then they need to be in the form "[Project Name] for Apache [Product]” or >> similar. >> >> > They could really name it anything, couldn't they? >> >> They can, but we need to protect our trademarks. >> >> BTW feel free to clarify with tramarks what needs to be done here. >> >> Kind Regards, >> Justin > >
