> It looks like the related java packages moving from `org.apache.fury` to `org.apache.fory`, right? This could be a big impact of the quarkus-fury extension and camel-fury component.
Yeah it is quite painful for all downstream projects. The renaming request comes from some ASF management teams and as PPMC we must resolve it to make sure that this project will graduate smoothly : ) Best, Twice On Thu, May 29, 2025 at 3:14 PM Shawn Yang <[email protected]> wrote: > > It conflicts with movie https://en.m.wikipedia.org/wiki/Apache_Fury. > We must change it to comply with asf trade mark > > On Thursday, May 29, 2025, Zheng Feng <[email protected]> wrote: > > > Hi Shawn, > > > > It looks like the related java packages moving from `org.apache.fury` to > > `org.apache.fory`, right? This could be a big impact of the quarkus-fury > > extension and camel-fury component. I wonder if we also need to change to > > the new fory name as well. What is the motivation of this name changes? > > Sorry, I have not followed the discuss about this topic in the community > > before. > > > > Shawn Yang <[email protected]> 于2025年5月29日周四 14:38写道： > > > > > Hi, > > > > > > I asked someone in Ant Group to help design a new logo. > > > When the new logo design is finalized, I will create a PR to replace > > > the current logo. > > > > > > Best, > > > Shawn > > > > > > On Thu, May 29, 2025 at 2:18 PM Liangliang Sui <[email protected] > > > > > > wrote: > > > > > > > > Hi everyone, > > > > > > > > I have a question here: does the logo image need to be changed to fory? > > > > > > > > Best, > > > > Liangliang Sui > > > > > > > > On Thu, May 29, 2025 at 1:18 PM Shawn Yang <[email protected]> > > > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > I just created a PR to rename fury to fory in > > > > > https://github.com/apache/fury/pull/2263. > > > > > > > > > > After this gets merged, I will create a PR in fury-site to finish the > > > > > remaining renaming. > > > > > > > > > > I'm not sure how to change the repo name from fury to fory, and > > > > > fury-site to fory-site. > > > > > Does anyone know how to do this? > > > > > > > > > > Best, > > > > > Shawn > > > > > > > > > > On Thu, May 29, 2025 at 1:37 AM Pan Li <[email protected]> wrote: > > > > > > > > > > > > Hi PJ, > > > > > > > > > > > > Agree with your perspective! Thank you for your efforts in handling > > > > > > the renaming work. I think the examples you provided are extremely > > > > > > helpful for advancing the project's graduation. Happy to support in > > > > > > any way needed! > > > > > > > > > > > > Best Regards, > > > > > > Pan Li > > > > > > > > > > > > On Wed, May 28, 2025 at 6:22 PM PJ Fanning <[email protected]> > > > wrote: > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > It would be great to see the project graduate. It would make it > > > easier > > > > > to do releases and you would no longer need IPMC approval. There are > > > also > > > > > new podlings and new applications to become podlings so freeing up > > IPMC > > > > > time would be appreciated. > > > > > > > > > > > > > > The one thing that delays graduation is getting the project > > rename > > > > > done. > > > > > > > > > > > > > > * https://incubator.apache.org/guides/graduation.html > > > > > > > > > > > > > > Example Maturity Model. We would need a Fury/Fory one as part of > > > > > setting up the graduation vote. > > > > > > > * > > > > > > > > https://cwiki.apache.org/confluence/display/GRAVITINO/ > > Gravitino+Maturity+Model > > > > > > > > > > > > > > Does anyone have any opinions on this? > > > > > > > > > > > > > > Thanks, > > > > > > > PJ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > 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] > > > > > > > > > > > > > > > > ------------------------------------------------------------ > > --------- > > > > > 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] > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
