When writing a new library with little adoption, with a goal of driving adoption where do you think effort should be dedicated between documentation, features, and promotion?
I think they all together a bit. I see documentation as a way of marketing features that have been written... but it doesn't help until people discover the project.
How do you know when documentation is holding you back?