Please setup the tracking issue of the client status
As described in README:
This client is still unfinished.
So can we set a tracking issue of the client status?
Within this tracking issue, we can:
- Track the current status, and update as needed.
- Adding detailed issues.
With this tracking issue, we will:
- Split tasks into smaller ones so contributors can start working.
- Convert the
unfinishedstatus into actionableworking onstatus - Establish a goal for the community: We can start using and contributing to this project.
In a word:
Please don't let the community wait for this project to be finished. Starts building it with the community now.
@Xuanwo, you literally are activating/coaching me, thanks!
I will spend some time to get needed context and study to make things synced(on both status, task breaking perspectives)
Thanks again ~~
For example, we can start by setting up a tracking issue of Release v0.1.
In the very first version of nebula-rust:
- Current state, what features we have implemented.
- Which features do we want to include?
- In which condition can we be ready for the
v0.1release?
@Shylock-Hg let's create/break down tasks so that open source heroes could help contribute!
It could be good timing for the long holiday and the hacktoberfest :)
Hello @Xuanwo : Thanks for your attention to Nebula Graph. This repo is pending for two reasons: 1. Rust supporting of fb-thrift is not mature 2. There are no enough users try rust for Nebula Graph If community user want to contribute to this repo, they should to know or to do:
- Update crate by https://crates.io/crates/fbthrift, and adjust it.
- Update thrfit IDL file of Nebula Graph, and provide the basic wrapper to data structure.
- Provide/Complete the basic abstraction about
Connection,ConnectionPool,SessionandSessionPool, and implement/test them(These could reference implementation of Java https://github.com/vesoft-inc/nebula-java). - Give the basic usage examples.
Thanks, @Shylock-Hg for the milestone/task breaking and guidelines :)