Create a formal list of stakeholders

As part of governance, there should be a formal list of Drupal stakeholder groups which is updated as required. This would be useful in several ways such as creating a vision document for initiatives (see #1606788: Create a vision document for each major initiative and submit it to governance review). And generally speaking it would be a good checklist to determine whether the impacts (if any) on all stakeholders have been considered.

As a start here are some suggested stakeholders:

• Site builders (small to medium)
• Site builders (enterprise)
• System administrators
• Core coders
• Contributed module coders
• Themers/designers
• Hosting services
• Users/coders/themers with accessibility requirements
• IT security professionals
• Database administrators
• Enterprise architects
• IT support
• Trainers
• Drupal documentation team
• Multilingual users or themers (including non-English language, East Asian languages etc.)

The idea is not that the list is set in stone or applicable in all cases and often within a larger group there may be different stakeholders with differing needs and issues (and of course any individual might be simultaneously in multiple groups) but having a general idea of who your stakeholders are, is pretty much an essential first step in governance (since the idea of governance is to make sure that stakeholder interests are at least considered, even if they can't always be served). Ideally you'd want to hear from the stakeholder groups themselves as to what, if any, impact or issues they foresee.