+1

Best,
Harish Krishnakumar

On Fri, 11 Apr 2025, 17:58 Apratim Shukla, <aprshu...@ucdavis.edu.invalid>
wrote:

> Hi all,
>
> To facilitate the continuous integration and deployment (CI/CD) of tools
> and libraries within the ResilientDB ecosystem, we propose transferring the
> following repositories, currently under their respective GitHub
> organizations, to the Apache Software Foundation's GitHub organization.
> This aims to:
>
>    - Centralize development under Apache governance
>    - Standardize CI/CD workflows
>    - Ensure consistent deployment across ResilientDB components
>
> Proposed Repositories for Transfer:
>
>    - ResVault SDK - https://github.com/ResilientEcosystem/resvault-sdk
>    - Resilient Node Cache -
>    https://github.com/ResilientEcosystem/resilient-node-cache
>    - Resilient Python Cache -
>    https://github.com/ResilientEcosystem/resilient-python-cache
>    - ResilientDB Ansible -
>    https://github.com/ResilientEcosystem/resilientdb-ansible
>    - Create Resilient App -
>    https://github.com/ResilientEcosystem/create-resilient-app
>    - ResilientDB Rust SDK - https://github.com/ResilientEcosystem/rust_sdk
>    - ResCLI - https://github.com/ResilientApp/ResCLI
>    - ResDB ORM - https://github.com/ResilientEcosystem/ResDB-ORM
>    - ResContract - https://github.com/ResilientEcosystem/ResContract
>    - Resilient Contract Kit -
>    https://github.com/ResilientEcosystem/resilient-contract-kit
>    - Smart Contracts GraphQL -
>    https://github.com/ResilientEcosystem/smart-contracts-graphql
>    - ResilientDB Orbit -
>    https://github.com/ResilientEcosystem/resilientdb-orbit
>    - ResLens Middleware -
>    https://github.com/ResilientEcosystem/ResLens-Middleware
>    - ResLens - https://github.com/ResilientEcosystem/ResLens
>
> Please reply to this thread with *+1 (yes)* if you support this transfer,
> -*1
> (no)* if you do not, or *0* to abstain.
>
> Looking forward to your feedback!
>
> Best regards,
> Apratim Shukla
> Apache ResilientDB (Incubating)
> apra...@apache.org
>

Reply via email to