+1 to bring this to a vote Other decisions need to be made around * a PMC chair * who will be invited to join the PMC and remain as a committer - it is valid to have all PPMC members become PMC members if this is the decision
On Tue, 17 Jun 2025 at 11:58, Shawn Yang <[email protected]> wrote: > > Hi everyone, > > Following up on our previous discussions and PJ's guidelines: > - Release Completion - Apache Fory v0.11.0 has been successfully > released under the new brand > - Infrastructure Migration - All rename-related tasks are complete, including: > - Website redirection from fury.apache.org → fory.apache.org > - Mail list migration to [email protected] > - Repository renaming and package migrations > - Maturity Model > - The graduation checklist has been prepared and reviewed [2] > > All prerequisites for graduation outlined in our discussions are now > fulfilled. > I recommend we formally initiate the graduation vote to transition > Apache Fory from incubation to Top-Level Project status per the > process outlined in the Incubation Guide[1]. > > Next steps if approved: > - PPMC members will vote on the [email protected] list > - Upon successful PPMC vote, we'll submit to IPMC for final approval > - Continue documentation updates during the voting period > > Request for feedback: Please share any remaining concerns. If no > objections are raised, I'll start the voting thread in the next few > days. > > We sincerely appreciate everyone's contributions to reach this > milestone - especially PJ for guiding the graduation process and all > contributors who helped complete the complex rename transition. > > [1] https://incubator.apache.org/guides/graduation.html > [2] https://cwiki.apache.org/confluence/display/COMDEV/Fory+Maturity+Model > > Best regards, > Shawn Yang > > On Mon, Jun 9, 2025 at 11:55 PM Shawn Yang <[email protected]> wrote: > > > > Yes, we should wait for the fury site redirect and a new release under fory. > > > > I think those things can be done this week if everything goes well. > > > > On Sun, Jun 8, 2025 at 8:25 PM PJ Fanning <[email protected]> wrote: > > > > > > The maturity model looks good. I would suggest that we hold off on > > > voting for graduation for a few weeks. > > > * let's get the fury site sorted out - redirecting to fory > > > * there probably would be no harm getting the 0.11.0 release done with > > > the fory name because then we can show the Incubator PMC that we have > > > a valid Fory release > > > > > > On Fri, 6 Jun 2025 at 15:14, Shawn Yang <[email protected]> wrote: > > > > > > > > Hi PJ, > > > > > > > > I created a Maturity Model for apache fory: > > > > https://cwiki.apache.org/confluence/display/COMDEV/Fory+Maturity+Model > > > > > > > > Please leave your comments. If everything goes right, I think we can > > > > start > > > > the vote for graduation in the next few days. > > > > > > > > Best, > > > > Shawn Yang > > > > > > > > > > > > On Thu, May 29, 2025 at 7:19 PM Shawn Yang <[email protected]> > > > > wrote: > > > > > > > > > There is no need to revert, it's ok to break some build stuff > > > > > temporarily. > > > > > Hope we can minimize this period. > > > > > > > > > > On Thu, May 29, 2025 at 6:56 PM PJ Fanning <[email protected]> > > > > > wrote: > > > > > > > > > > > > I added extra JIRAs and they are linked to > > > > > > https://issues.apache.org/jira/browse/INFRA-26865 > > > > > > > > > > > > I changed the .asf.yaml in the fury-site repo. I thought it was a > > > > > > protected branch but it isn't. I can revert the changes if requested > > > > > > but in the end, we're going to be temporarily breaking some build > > > > > > stuff during the rename anyway. > > > > > > > > > > > > On Thu, 29 May 2025 at 11:26, PJ Fanning <[email protected]> > > > > > > wrote: > > > > > > > > > > > > > > We will need to get the Infrastructure team to make a number of > > > > > > > changes, using JIRA. > > > > > > > * rename the LDAP group > > > > > > > * rename the DNS for the website > > > > > > > * rename the mailing lists > > > > > > > > > > > > > > We need to change the files in the incubator svn. I can do this > > > > > > > bit. > > > > > > > > > > > > > > On Thu, 29 May 2025 at 08:54, Pan Li <[email protected]> wrote: > > > > > > > > > > > > > > > > Yes, and perhaps Fury still has many potential users. > > > > > > > > I think the original version can be retained for a while > > > > > > > > temporarily > > > > > > > > and then initially switched to a new name. > > > > > > > > Meanwhile, record this event on fory-site. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Pan Li > > > > > > > > > > > > > > > > On Thu, May 29, 2025 at 3:40 PM Liangliang Sui < > > > > > [email protected]> wrote: > > > > > > > > > > > > > > > > > > I suggest that we notify all users in > > > > > > > > > https://github.com/apache/fury/issues/1766 after completing > > > > > > > > > the > > > > > remaining > > > > > > > > > renaming work. > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > Liangliang Sui > > > > > > > > > > > > > > > > > > On Thu, May 29, 2025 at 3:24 PM Twice <[email protected]> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > 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]
