This is an automated email from the ASF dual-hosted git repository.
chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fory-site.git
The following commit(s) were added to refs/heads/main by this push:
new 92bf598e [Blog] Important Announcement: Apache Fury is Now Apache Fory
(#256)
92bf598e is described below
commit 92bf598e2b1708d03c6d50a5f9b9292bfb5c7274
Author: Shawn Yang <[email protected]>
AuthorDate: Sat Jun 7 23:22:57 2025 +0800
[Blog] Important Announcement: Apache Fury is Now Apache Fory (#256)
add blog for renaming: `Important Announcement: Apache Fury is Now
Apache Fory`
---------
Co-authored-by: tison <[email protected]>
---
blog/2025-06-06-fury_renamed_fory.md | 55 ++++++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
diff --git a/blog/2025-06-06-fury_renamed_fory.md
b/blog/2025-06-06-fury_renamed_fory.md
new file mode 100644
index 00000000..fe3f6651
--- /dev/null
+++ b/blog/2025-06-06-fury_renamed_fory.md
@@ -0,0 +1,55 @@
+---
+slug: fury_renamed_to_fory
+title: Important Announcement - Apache Fury is Now Apache Fory
+authors: [chaokunyang]
+tags: [fury]
+---
+
+
+Our new identity: Fast Serialization Framework **FOR Y**ou
+
+## Announcement
+
+**The Apache Fury team is now officially announcing that Apache Fury has been
renamed to Apache Fory**, effective immediately. This transition impacts all
project components including code repositories, package names, documentation,
and communication channels.
+
+## Why This Change Is Necessary
+
+This transition is required to resolve naming conflicts identified by the ASF
Brand Management. Following massive discussions and a formal vote, this change
ensures compliance with ASF's guidelines.
+
+The new name "Fory" preserves phonetic similarity to "Fury" while establishing
a distinct identity aligned with ASF standards.
+
+## Technical Changes and Impact
+
+This transition requires updates across the ecosystem:
+
+- **Java packages** migrated from `org.apache.fury` to `org.apache.fory`
+- **Class names** migrated from `XXXFury/FuryXXX` to `XXXFory/ForyXXX`
+- **GitHub repositories** renamed to `apache/fory` (code) and
`apache/fory-site` (website)
+- **Downstream integrations** (Quarkus-Fury, Camel-Fury) require dependency
updates
+- **Mailing lists** transition to `@fory.apache.org`
+
+## Migration Support
+
+To facilitate this transition:
+
+- Existing Apache Fury release document remains intact at [v0.10
document](https://fory.apache.org/docs/0.10/docs/introduction/)
+- Critical URL redirects in place
+
+## Why "Fory"?
+
+The name was chosen by prioritizing:
+
+- Phonetic similarity to "Fury"
+- No existing trademark conflicts
+- Preservation of our technical identity
+- Short, memorable, and globally pronounceable
+
+## Our Commitment
+
+We recognize the burden this places on our users, especially those with deep
integrations. Please know:
+
+- All existing issues and PRs have been migrated
+- Performance benchmarks remain consistently superior
+- Release cycles continue uninterrupted
+
+This rename represents our commitment to respecting intellectual property
while maintaining technical excellence. We're grateful for your patience and
continued trust as we navigate this transition together.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
