Consolidate Open Issues and Establish a Road Map

[freephile]

There are old open issues all over the place. They need to be consolidated, and secondly they need to be prioritized into a Road Map. The consolidation part implies that there are certain tags to identify what the issue pertains to so that issues can be grouped and sorted logically:

Product Management Aspect

Bug, Feature, Organization / Administration, Financial / Sponsor, Documentation, Planning, Big Picture / Alternatives, Security, Integration.

Project Management Aspect

Issues classified by type: 'minor', 'issue', 'story' or 'epic' so that individual issues can be assembled into stories and worked. Or that stories can be broken down into issues. A default 'issue' should be clear and concise enough to describe work that can be done in less than half a day (3 hours). If not, then it is too big or too vague - so it becomes a story that must be refined into distinct issues that compose all the work for the story. If the work is so big that there are multiple stories; and it is cross-functional; then it should probably be an epic.

Architecture / Component Aspect

Web server, proxy, PHP, Python, JavaScript, Git, Ansible, Elasticsearch, Database

User Aspect

UI, UX, Developer, Systems Administration, DevOps, Quality, Testing

The Queues

• Meza doesn't support the config I need enterprisemediawiki/meza#1051 lists Wanted Features such as security
• https://github.com/nasa/meza/issues/ is the list of 'current' issues
• https://github.com/freephile/meza/issues/ list of issues from the development perspective