Core Acquisition

This document will outline the process to communicate gaps within the system and provide steps to resolve.

The term gaps is used to define any functionality that the platform does not cover. It is not used to define BUGS. Bugs and gaps are separate issues. Gaps can be considered requests for new features that are either brand new or extensions/oversights of an existing feature like a specific plugin.

Gaps should originate from a desire to achieve a certain business level objective. Sometimes these objectives can be achieved using the current toolset or using custom plugins. Before ANY decision is made to extend core the current capabilities of the platform should be analyzed by a architect/subject matter expect. Once options to achieve the desired outcome have been established decision will be made as to the way to move forward which may turn into an issue/feature.

When integrating features into core the integration should be done in manor which facilities reuse and extensibility for all using the platform. The platform should never be extended with logic or plugins that are specific to an individual needs. Individual needs to be abstracted into features / functionality that can be reused throughout the entire ecosystem. Architects will be responsible for overseeing and working with developers to make sure that all core changes are done so with the ecosystem in mind not the individual.