[Gluster-Maintainers] Backlog generation framework

[Kaushal M]

In the last maintainers meeting, we touched on the topic of component
backlogs. One of the questions raised regarding this was that what
constitutes a backlog.

Shyam and others came up with a framework to identify backlogs for
components. The framework is as follows.

A backlog is anything you wish to do for your component. These could
be new features, something that you want to fix or make better, or
just an idea that you'd like to see implemented some time. To identify
these, you can think about what you'd like to do for your component
related to the following topics.

- Focus areas
   - Testing Improvements
   - Technical Debt
   - Server Side Replication
   - Scalability Improvements
   - Performance Improvements
   - Must Fixes
   - Developer Experience
   - Container Integration
   - Client Side Caching
- Other (means to extract more technical debt)
   - debuggability/maintainability
   - Documentation (user experience)
   - developer documentation
   - Usability
   - Recovery
   - Upgrade
   - Health/Integrity
   - Codegen
   - Versions and compatability
   - Crash consistency
- Current major upstream work and its impact
   - Graph cleanup
   - Compound FOPs
   - SE Linux
   - Brick multiplexing
   - Footprint reduction for containers
   - md-cache changes