[New Process Improvement Need]: Triaging Change Requests

[riverma]

Checked for duplicates

Yes - I've already checked

Category

Information Sharing - documentation design, templates, communication, etc.

Describe the need

We have a need for better guidance / standards for:

• Triaging Strategy for New Issue Tickets (+1'd by @kgrimes2)
• Governance approach for acceptance / rejection of proposed software changes
• Dynamic change-management process (make it quick to decide on swapping out or adding a new A&A system, etc.)
• Governance approach for vetting and integrating outside contributions to open source projects (+1'd by @ngachung)
• Governance approach for handling feature requests and community-based decision making.
• Governance approach for creating / modifying core software documentation

[riverma]

+1’d by @jeffreypon @kgrimes2, @pymonger

[riverma]

Tagging AERIE team members on this ticket for discussion: @mattdailis @joswig. They've got a great triaging strategy implemented for AERIE repositories we could learn from to help move this ticket forward.