-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update README to contain a quick start guide for speedb #18
Conversation
0a4eca2
to
d64a561
Compare
README.md
Outdated
@@ -1,32 +1,59 @@ | |||
## RocksDB: A Persistent Key-Value Store for Flash and RAM Storage | |||
# SpeeDB: A drop in replacement embedded solution for RocksDB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Are we indeed a drop-in replacement? Is that our approved marketing message? Just verifying
- The basic comment I have is that this is indeed a quick-start guide as the name of the branch implies, BUT, quoting from https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/: "In simple words, we can describe a README file as a guide that gives users a detailed description of a project you have worked on" (this matches multiple other pages describing the purpose / expected content of a README file).
We are replacing RocksDB's README (that does include this info). So, IMO, either we refer to that file for more information, or write our own (in case we would like to also be a drop-in replacement of the README file) - What is our project?
- Why are we developing a drop-in replacement for RocksDB (assuming we indeed provide a drop-in replacement)?
- What is our vision?
Etc.
The rest of my comments below will just assume that the comment above has been addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@udi-speedb, There's a separate thread on OSS marketing happening. I created issue #45 to update the README.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AmnonHanuhov let's be consistent and use the Speedb spelling everywhere rather than SpeeDB.
README.md
Outdated
`TODO:` This section should point the reader to a dedicated file explaining how to contribute | ||
|
||
## License | ||
SpeeDB is licensed under Apache 2.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where can I find the license?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rtpro care to elaborate on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
See the [github wiki](https://github.com/facebook/rocksdb/wiki) for more explanation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we point to our own wiki?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line was removed because I didn't want to point to the rocksdb wiki. Do we have a wiki that I can mention here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's work going on to create Speedb Documentation. We will link it once it's up.
README.md
Outdated
|
||
## Usage | ||
Usage of the library in your code is the same, regardless of whether you statically linked the library or dynamically linked it, and examples can be found under the https://github.com/speedb-io/speedb/tree/main/examples directory. | ||
The public interface is in `include/`. Callers should not include or rely on the details of any other header files in this package. Those internal APIs may be changed without warning. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may be the intention but doesn't hold in practice (I personally had to include a header that is in a different folder for my new filter type, and I have done this after discussion with @mrambacher)
mkdir build && cd build | ||
cmake .. [cmake options] -GNinja | ||
ninja | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we not mention make on purpose?
Are we advocating cmake as the only supported build system?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally I would want us to have a cmake script, I opened a ticket for it on Jira https://speedb.atlassian.net/jira/software/projects/SPDB/boards/1/backlog?assignee=61e4062385a2d60070295e91&selectedIssue=SPDB-711
But to answer your question, this is something that should probably be discussed with the rest of the r&d team. Whether we want to set a standard of compiling with cmake
(the cmake script I mentioned above), or mention make here as well, or maybe both.
e8ddf4c
to
f1d31ed
Compare
a8716c6
to
05355ee
Compare
README.md
Outdated
@@ -1,32 +1,59 @@ | |||
## RocksDB: A Persistent Key-Value Store for Flash and RAM Storage | |||
# SpeeDB: A drop in replacement embedded solution for RocksDB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AmnonHanuhov let's be consistent and use the Speedb spelling everywhere rather than SpeeDB.
3753450
to
81a2848
Compare
81a2848
to
a02d090
Compare
a02d090
to
83ebebe
Compare
Rendered