[Draft] Policy for adding a new feature, functionality or modules to LocalGov Drupal

Requests for new functionality come from a number of places, content designers, council website product owners, developers to name a few.

New features usually come in the form of Drupal contributed modules or custom modules that can be included in the default codebase.

Additionally, the installation profile can enable such features on a default installation.

For any request, we need to assess whether we should include the new module module or feature

• in the localgov profile codebase (i.e. make it a dependency in the profile composer.json)
• as installed by default (i.e. add it to the .info.yml file such that it is installed by default on a fresh installation).

Considerations:

1. Does more than one council want this feature? / Does a significant proportion of our users want this feature?
2. Can the feature be disabled after installation without any dependency problems?
3. Does the product group / product owner / product lead want to prioritise this feature?
4. Will this enhancement be communicated to users with an existing installation? (e.g. release notes / README.md / drupal_set_message )

If questions 1-4 are all answered with a "yes", this is a candidate to be included directly in the installation profile.

If question 2 is "no", then the feature or module is probably better as an optional module.