## SRT V1 improvement ideas (period 135)

Some ideas inspired by [our previous discussions](https://youtu.be/Vo8k91wwA9g?t=605).

## 1. Use SRT V1 as flat issue tracker instead of as a tree?

Practically this means not creating abstract / general contribution requests.

Alternative is to start "growing SRT V1" (for TPs and CRs to have children and associated polls). Maybe two level trees are ok at first?

## 2. Contribution Requests and Contributions are one and the same?

Any meaningful contribution only starts with publishing of the first iteration. Even if there are no more iterations afterwards, you want your contribution to receive attention, be reviewed, tested and so on. It's just one sentence in a continuous communication stream within the community.

A contribution is just a contribution request that asks for attention / feedback / recognition / improvements?

Analoguous principle holds for topic proposals. Any answer to a topic has potential to become a discussion in its own right.

This would resolve the question of whether we need new type of "contribution" items, keep the tree symetrical and simple.