1 |
Hi, |
2 |
|
3 |
I think some of the ideas you brought for GURU could be used to help tagging PRs more easily to sort them between "(un)known proxy-maintainee with background" on a per package/per dev area basis. |
4 |
There might be a bit much complexity in the following suggestion, but here it is. |
5 |
|
6 |
We could, at review time, add flags on a work done. They would be structured like a key-value attribute reflecting the type of change, and its complexity. |
7 |
There could be different kind of changes: bump specific package, eclass addition/modification, eapi-bump, python addition, etc |
8 |
|
9 |
By recording the experience of commit authors, we could set thresholds defining the average time and knowledge required for a gentoo dev needed to review and commit a PR. |
10 |
|
11 |
I wonder if it wont bring too much workload on the initial sorting though. And if people will agree to have evaluation records in general. |
12 |
|
13 |
|
14 |
Also, shouldnt the mail list system add a Reply-To field in the messages sent? |
15 |
|
16 |
Regards, |
17 |
Corentin “Nado” Pazdera |