I am trying to get better at this and only share more quality projects, but I was just wondering what all of your takes on this is.
Do you think there is an appropriate time to share your OSS project?
A lot are of the sort "I played around with this idea over the last couple of weeks. I want to get back to it (maybe) but don't have the time now. Here's the code in case someone else finds it useful."
Even popular packages have a hard time finding people willing to contribute code back.
So, I argue that you shouldn't worry about if it's the right time or not.
Now, there are certainly projects where worrying about timing is appropriate and important. If you write a new text editor or database you want to make sure it doesn't destroy user data even in the first release because the project will get a reputation that it doesn't care about basic assurance testing, which is important for those sorts of projects.
However, what you describe doesn't seem like one of those.
I actually am working on a project like that (database) so your point resonated with me. For what I am building I'll take my time and I won't release before it's stable because if it doesn't work properly for v1 then that could be a problem.
I guess the answer for the original question though is that it just depends.
Personally, I prefer releasing when docs cover the public API and I have at least some test coverage.