GitHub user github-actions[bot] created a discussion: December 07, 2025: This Week in OpenDAL
*This weekly update is generated by LLMs. You're welcome to join our [Discord](https://opendal.apache.org/discord/) for in-depth discussions.* --- ## Overall Activity Summary The `apache/opendal` repository has experienced significant activity over the past week, with a focus on refactoring efforts to modularize services and layers as part of RFC-6828. Several pull requests have been merged to split services and layers into separate crates, improving maintainability and reducing complexity. Additionally, there have been bug fixes, new features, and documentation improvements. The community is actively engaging in discussions and tracking progress on key initiatives. --- ## Key Ongoing Projects - **Modularization of Services and Layers (RFC-6828)**: - #6868 by @manchangfengxu: Refactored the `moka` service into its own crate, reducing complexity and improving compilation speed. - #6866 by @Xuanwo: Moved the `s3` service into a separate crate as part of the modularization effort. - #6867 by @Xuanwo: Split the `async_backtrace` layer into a new crate, aligning with the modularization strategy. - #6858 by @Xuanwo: Split the core into a new `opendal_core` crate to prepare for further modularization. - **New Features**: - #6836 by @siomporas: Introduced a new `git` service with transparent LFS support, enabling generic Git repository handling. - #6844 by @zhan7236: Added user-defined metadata support for the Backblaze B2 (`b2`) service. - **Bug Fixes**: - #6859 by @yihong0618: Addressed a Python GIL hang issue by improving parallelism handling. - #6861 by @yihong0618: Fixed an issue with `just` not correctly finding `uv` during Python development setup. --- ## Priority Items - **Open Pull Requests Needing Attention**: - #6870 by @0lai0: Refactor to move the `http` service into its own crate as part of the modularization effort. - #6861 by @yihong0618: Fix for Python development setup (`just` and `uv`) that requires review and testing. - #6836 by @siomporas: The `git` service with LFS support is a large feature addition that needs thorough review. - **Open Issues**: - #6869 by @RaphDal: JVM deadlock on Windows when starting new threads as the Tokio runtime shuts down. This issue requires immediate attention to address potential deadlocks in Java bindings. - #6860 by @yihong0618: Python `just install-dev` fails to correctly handle `uv`. Needs resolution to streamline development workflows. --- ## Notable Discussions - **#6829**: Tracking the modularization of services and layers as part of RFC-6828. Contributors, including @0lai0 and @manchangfengxu, are actively working on splitting services like `http`, `moka`, and `s3` into separate crates. - **#6755**: Discussion on unifying code patterns across services to improve consistency and maintainability, led by @koushiro. - **#6869**: Important discussion on resolving JVM deadlocks in Java bindings, initiated by @RaphDal. --- ## Emerging Trends - **Modularization Focus**: The repository is heavily focused on modularizing services and layers to improve maintainability and reduce build times. This trend aligns with the goals outlined in RFC-6828. - **Enhanced Metadata Support**: Several services, including `b2`, are being updated to support user-defined metadata, reflecting a push for feature parity across backends. - **Increased Community Contributions**: Contributors like @siomporas, @zhan7236, and @yihong0618 are actively adding new features and addressing bugs, showcasing a growing and engaged community. --- ## Good First Issues - **#6829**: Tracking issues for RFC-6828: Core. New contributors can help split services or layers into separate crates. This task is well-documented and provides a clear entry point for understanding the repository's architecture. - **#5693**: Implement `Write Returns Metadata` for all services. Contributors can extend metadata extraction for specific services, following existing patterns. - **#2611**: Tracking issues for Object Versioning. Contributors can implement versioning support for services like `azblob`, `b2`, and `gcs`. - **#5480**: Tracking issues of RFC-5479: Context. Tasks involve implementing context propagation across services, which is a straightforward feature addition. --- Encourage new contributors to explore these approachable tasks and join the community on [Discord](https://opendal.apache.org/discord/) for guidance! GitHub link: https://github.com/apache/opendal/discussions/6872 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
