|
1 | 1 | # Backlog
|
2 | 2 |
|
3 | 3 | ## Iteration +1
|
4 |
| -- Publish package to PyPI |
| 4 | +- Opsgenie: Add subsystem |
| 5 | +- GitHub: Export conversations |
| 6 | +- Refactoring: Spread GitHub modules along the feature axis |
5 | 7 |
|
6 | 8 | ## Iteration +2
|
7 |
| -- Options: Make `limit=100` configurable. Is paging needed? |
8 |
| -- Documentation: Recipes how to relay reports to messenger channels |
9 |
| -- Data: Search items with significant reactions |
10 |
| -- Data: Search items with EPIC or other keywords in its titles |
11 |
| -- Data: Search for assignments |
12 |
| -- Report: On the CI report, render sections only conditionally |
13 |
| -- Report: On HTML links, always include the org name as prefix |
14 |
| -- GitHub/CI: Can the retrieval process be optimized, not needing to iterate |
15 |
| - repositories manually? |
16 |
| -- GitHub/Bugs: More flexible processing of "labels" vs. "sections", |
17 |
| - i.e. improve grouping code, making it more maintainable. |
| 9 | +- GitHub/CI: Currently lacks parameter `--timerange` |
| 10 | +- GitHub: Search items with significant amounts of reactions |
| 11 | +- GitHub: Search items with significant (amount or length of) comments |
| 12 | +- GitHub: Search items with EPIC or other keywords in its titles |
| 13 | +- GitHub: Search items with people assignments |
18 | 14 | - GitHub/API: On errors, the JSON response includes the reason as an
|
19 | 15 | error message. However, it isn't displayed, yet.
|
| 16 | +- Options: Make `limit=100` configurable? Is paging needed? |
20 | 17 |
|
21 | 18 | ## Iteration +3
|
22 | 19 | - Data: Identify items with high conversation activity (comment frequency, etc.)
|
|
29 | 26 | corresponding time range.
|
30 | 27 | - Report: Make configurable if Rapporto shall only return a share of top changes,
|
31 | 28 | or each one. Currently, the default is 2/5, but 1/3 is also reasonable.
|
| 29 | +- GitHub/Bugs: Also consider issues flagged with `Type: Bug`, |
| 30 | + orthogonal to GitHub's "labels". |
| 31 | + - Examples: |
| 32 | + - https://github.com/crate/cratedb-prometheus-adapter/issues/176 |
| 33 | + - https://github.com/tech-writing/sphinx-design-elements/issues/128 |
| 34 | + => Currently there is no API for this attribute yet. |
| 35 | + - https://github.com/orgs/community/discussions/140874 |
| 36 | + - https://github.com/orgs/community/discussions/139933 |
32 | 37 |
|
33 | 38 | ## Done
|
34 | 39 | - Make it work.
|
|
40 | 45 | - Documentation: Baseline
|
41 | 46 | - Added basic
|
42 | 47 | - Options: Make options optional, to report about the complete corpus
|
| 48 | +- Publish package to PyPI |
| 49 | +- Report: On the CI report, render sections only conditionally |
| 50 | +- GitHub/CI: Can the retrieval process be optimized, not needing to iterate |
| 51 | + repositories manually? No: The GitHub API is per-repository. |
| 52 | +- Report: On HTML links, always include the org name as prefix |
| 53 | +- GitHub/Bugs: Add `stale` label |
| 54 | +- GitHub/Bugs: More flexible processing of "labels" vs. "sections", |
| 55 | + i.e. improve grouping code, making it more maintainable. |
| 56 | +- GitHub/Bugs: Add label `type: Bug` |
| 57 | +- Documentation: Include breadcrumbs into static docs, not just README |
0 commit comments