Re: Documentation Suggestion

Hi! Greg Beaver wrote:

A possible solution to all the ire raised over documentation: Why not require API in-code documentation for all package proposals prior to acceptance, and peardoc for all packages prior to the first release (i.e. after package proposals are accepted)? Once people get over the initial hurdle of creating the docs, it's very easy to maintain them/improve them. Packages that have already been released need not be affected, but it would be nice if the developers would follow the lead of Alexey and Stephan and write excellent docs for existing packages.

I'd suggest making it "before the first *stable* release", as alphas and betas are usually directed at developers who can live without the docs.