projects / ceph.git / blame
| Commit | Line | Data |
|---|---|---|
| f67539c2 TL |
1 | <!-- |
| 2 | Welcome to the Jaeger project! 👋🎉 | |
| 3 | ||
| 4 | - Please search for existing issues to avoid creating duplicate bugs/feature requests. | |
| 5 | - Please be respectful and considerate of others when commenting on issues. | |
| 6 | - Please provide as much information as possible so we all understand the issue. | |
| 7 | - If you only have a question, you may get a faster response by asking in | |
| 8 | - our chat room https://gitter.im/jaegertracing/Lobby, or | |
| 9 | - the forum https://groups.google.com/d/forum/jaeger-tracing | |
| 10 | (but please don't double post) | |
| 11 | --> | |
| 12 | ||
| 13 | ## Requirement - what kind of business use case are you trying to solve? | |
| 14 | ||
| 15 | <!-- required section --> | |
| 16 | ||
| 17 | ## Problem - what in Jaeger blocks you from solving the requirement? | |
| 18 | ||
| 19 | <!-- required section --> | |
| 20 | <!-- If possible, describe the impact of the problem. --> | |
| 21 | ||
| 22 | ## Proposal - what do you suggest to solve the problem or improve the existing situation? | |
| 23 | ||
| 24 | <!-- It's ok if you don't have one. --> | |
| 25 | ||
| 26 | ## Any open questions to address | |
| 27 | ||
| 28 | <!-- Questions that should be answered before proceeding with implementation. --> |