-
Notifications
You must be signed in to change notification settings - Fork 472
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
QAQ Time: Let's take a break and polish details of OpenDAL #4738
Comments
And the compatibility matrix of each backend x each trait? |
Can you provide more details? Are you referring to the supported features of every service? |
yes. e.g. |
Website is a bit complex, let's move to seperate issue to track. |
All issues have been closed, let's move. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
QAQ, opendal doesn't smell good at the moment.
Our codebase is full of outdated comments, typos, and incorrect examples. A number of recently added crates lack proper documentation. The internal implementation leaves much to be desired. We've hastily released numerous versions, each featuring significant breaking changes and extensive refactoring. It's time for us to pause and refine our details.
I plan to postpone all breaking changes for the next two or three releases. During these patch versions, we can improve OpenDAL's appearance and prepare for our upcoming journey.
I called it QAQ Time. Hoping the opendal community will like it.
I will list the tasks I aim to complete during QAQ Time. Feel free to suggest new ones or choose any that interest you.
Tasks
Website
Docs
Quality
size
inRangeWrite
#4478Typos
Yes, we all make typos, but I've made quite a few. Feel free to submit batches of typos! Including documentation improvements is even better.
The text was updated successfully, but these errors were encountered: