Repository Naming

A good repository name allows users to accurately guess its contents. Repositories in Flutter-Global follow the conventions:

repository names should be lower case, using a dash (-) as a word separator.
a capability repository is prefixed with cap- e.g. cap-cashout.
a product repository is prefixed with product- e.g. product-global-betting-platform.
use a common relevant prefix to group several related repos together. e.g. for the fixed odds cashout quote functionality this is fcq-.
for the primary repository of an application use -service suffix, e.g. fcq-service.
each division usually maintains its own service deployment with a repository for each specific divisional configuration. These repos contain config (preferred), configrepo, chef or ansible to indicate their contents. Since they are owned by a particular division that is indicated by a suffix (-ppb, -fdg, or -isp). e.g. fcq-config-ppb contains PPB deployment config for the FCQ service.
supporting repositories can be referred to as a lib (shared library code), tests (separate testing code) or tool (a supporting utility)

Overview

Lower case repository name with a dash (`-`) word separator
prefix-	-body-	-suffix
existing abbreviation (e.g. tla name)	`service` for primary app	none by default!
`cap-` for capability	`tool` for supporting utility, `lib` for library, `tests` for tests	`-ppb`, `-fdg` or `-isp` indicates divisional ownership e.g. for deploy config.
`product-` for product	`config` for configuration (or `chef`, `ansible`)

For more examples please browse the service catalogue or search the list of repos by name in the organisation itself.