Add policy for development modules

[TraceyC77]

Description

Add policy that covers when not to split packages
into a -devel module due to man pages
Update policy: Prior to building a package to add
checking for a maintainer

Fixes #557

[EbonJaeger]

Suggested change

	In the cases where modules like `perl` or `python` would be split by the default `ypkg` policy (for instance because they contain category 3 `man` pages), the current best practice is to add a `patterns : /*` stanza to keep everything in the main package for convenience.
	In the cases where modules like `perl` or `python` would be split by the default `ypkg` policy (for instance because they contain category 3 `man` pages), the best practice is to add a `patterns : /*` stanza to keep everything in the main package for convenience.

In the interest of keeping the documentation "timeless," I think we should avoid saying that "this is the way it currently is." I think it can be inferred that by virtue of being in the documentation, it is "current."