Proposed repository and package naming conventions

[wpscholar]

Proposed changes

Updates to how we name repositories and packages.

Type of Change

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Documentation Update (if none of the other choices apply)

[0aveRyan]

The one other comment I'd add is that when we tie-in PHP Namespacing, I'm not sure this naming convention translates 💯 as everything should probably fall under Newfold\{X} or some branded abstraction for all our work. If we try to mirror the name otherwise, we again may run into some slightly longer names like...

• Newfold\Laravel\Hiive\App\Controllers\Users()
• Newfold\WP\Plugin\MU\FancyPantsMissionControl()
• Newfold\WP\Plugin\Bluehost\Admin\Assets()

I'm not calling it out as a problem, but it does get verbose i.e. class_exists('\\Newfold\\WP\\Module\\Staging\\REST\\CloneController')