More folder names should be considered for types

[stof]

This is found while looking at the list of other directories:

CSS preprocessors (might be discussed between resources and public as they don't need to be public depending on the setup):

• less
• sass
• scss

Other public folders:

• javascripts
• icons
• imgs
• wwwroot
• font

Other source folders:

• src-dev

Other doc folders:

• apidocs
• apidoc
• api-reference
• user_guide
• manuals
• phpdocs

Other test folders:

• unittest
• unit_tests
• unit_test
• phpunit-tests
• spec (for PhpSpec users), even though this may not disqualify a package to be compliant, as PhpSpec specs are not primarily tests

These are not among the commonly used names, so they should not alter the final decision, but they might be worth taking into account for the compliance tool (which needs to list non-compliant alternatives) and in the stats about the amount of package using each group.

[pmjones]

Although the compliance check is intended as a "tentative" compliance, more accuracy is better. If you send a PR with those additions to the compliance script, and/or other code as needed, I'll be happy to review it. Thanks!

[pmjones]

@stof If you are already working up a PR on this let me know; otherwise, I'll address it myself.

[pmjones]

This is applied in fab33c9 . Let me know if you think of anything else, and thanks for your attention to detail!