tisonkun commented on code in PR #5680:
URL: https://github.com/apache/opendal/pull/5680#discussion_r1977040290


##########
website/blog/2025-03-01-2025-roadmap/index.md:
##########
@@ -0,0 +1,81 @@
+---
+title: "Apache OpenDAL 2025 Roadmap: Perfecting Production Adoption"
+date: 2025-03-01
+tags: [announcement]
+authors: xuanwo
+---
+
+Hi everyone, long time no see. Although we have been actively developing 
OpenDAL and consistently releasing updates, we haven’t provided a clear 
overview of where OpenDAL is heading. This post aims to address that. Here, we 
will discuss OpenDAL's current position and the future directions we are moving 
toward.
+
+I hope this post serves as a guide for our development, encourages more people 
to contribute, and ultimately helps achieve the vision of OpenDAL.
+
+<!--truncate-->
+
+## What's OpenDAL?
+
+OpenDAL (`/ˈoʊ.pən.dæl/`, pronounced "OH-puhn-dal") is an Open Data Access 
Layer that enables seamless interaction with diverse storage services. Our 
VISION is [**One Layer, All Storage**](https://opendal.apache.org/vision), and 
our core principles are Open Community, Solid Foundation, Fast Access, Object 
Storage First, and Extensible Architecture.
+
+We are building:
+
+- [A core library built in Rust](https://crates.io/crates/opendal) that 
supports all services at zero cost and offers unified retry, concurrency, 
logging, tracing, metrics, timeout and more layers.
+- Language bindings for [Python](https://pypi.org/project/opendal/), 
[Java](https://central.sonatype.com/artifact/org.apache.opendal/opendal-java), 
[Node.js](https://www.npmjs.com/package/opendal), C/C++, and more.

Review Comment:
   ```suggestion
   - Language bindings for [Python](https://pypi.org/project/opendal/), 
[Java](https://central.sonatype.com/artifact/org.apache.opendal/opendal), 
[Node.js](https://www.npmjs.com/package/opendal), C/C++, and more.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to