Establish a baseline on how the specific module/functionality actually operates in the existing version of Evergreen.
Discern the difference between process, policy and software solutions.
Document optimal module functionality within a future Evergreen release and develop a list of requirements.
Become the defacto module testing group, through which all new development would be filtered from the PINES library side of the development process.