I'm writing some library code (ex. jQuery plugins, Django apps) that is meant to be used by other people as building blocks for larger applications. Often I don't see much need for others peer-reviewing my code, but it would be great to get people's opinions on its API (the public interface to each component), since the earlier I fine-tune them (preferably long before the code is released) the more opportunities I have to make changes. After the code is released, changing the API without breaking legacy code is much harder, specially if my libraries have many users at this point.
The objective of these questions would include, among others: the classes/methods/etc names are good, descriptive and self-documenting? The number/order/types of the parameters are intuitive/follows the platform's conventions? Are there useful operations that are missing, or are ankward to use in the current form? Are there doubts about whether or not a function would work with certain corner-case arguments?
My question is whether or not this kind of question is on topic for this site. Or if there is any other Stack Exchange site where I could ask about this. API design may be a bit more subjective than most other facets of code (security, performance, correctness), but not a lot, about the same level as "best practices and design pattern usage".
And if on-topic, may I ask these questions without including the whole (or any) code? I mean, implementation code, examples of usage would be obviously needed. Not that having the rest of the code reviewed would be bad, just that the question might get too long with it (and the focus is on the code as a black box - exactly how most users will see it).
