Dear Apache Fory Community, We are writing to formally announce that Apache Fury has been renamed to Apache Fory, effective immediately. This name change is necessary to resolve naming conflicts and ensure compliance with ASF's brand management guidelines.
Key Changes: 1️⃣ Package/Class Migration: - Java packages: org.apache.fury → org.apache.fory - Class names: XXXFury/FuryXXX → XXXFory/ForyXXX 2️⃣ Repository Updates: - Code: github.com/apache/fury → github.com/apache/fory - Docs: github.com/apache/fury-site → github.com/apache/fory-site 3️⃣ Communication Channels: - Mailing lists now use @fory.apache.org domains - Legacy fury.apache.org URLs will redirect temporarily Migration Support: - Existing Fury 0.10 documentation remains available at: https://fory.apache.org/docs/0.10/docs/introduction/ - All issues/PRs have been migrated to new repositories - Critical URL redirects are in place Why Fory? The name was selected because it: ✅ Preserves phonetic similarity to "Fury" ✅ Has no trademark conflicts ✅ Maintains our technical identity ✅ Is globally pronounceable and memorable Our Commitment: We recognize this transition creates significant work for our users, especially those with deep integrations. Please know: - Performance remains consistently superior - Release cycles continue uninterrupted - All Fury features are preserved in Fory This evolution represents our commitment to both technical excellence and ASF compliance. We're grateful for your understanding as we navigate this transition. For full details, see our announcement blog: https://fory.apache.org/blog/fury_renamed_to_fory/ Best regards, Shawn Yang
