| 1 |
You can review the PRs and try to remove common errors before the devs |
| 2 |
check it. Then they don't have to correct the same mistakes again. I don't |
| 3 |
mean you do the corrections, you just suggest them to the PR authors so |
| 4 |
they probably won't repeat them again. |
| 5 |
|
| 6 |
Common stuff like: |
| 7 |
- using latest eapi (at least for new pkgs)? |
| 8 |
- correct distfile name? |
| 9 |
- proxy maint project in metadata? |
| 10 |
- correct, sorted deps? |
| 11 |
- slot operators for rebuilds? |
| 12 |
- working tests if possible? |
| 13 |
- patches from reliable sources? |
| 14 |
- using || die after commands? |
| 15 |
- reusing eclasseses instead of custom solutions? |
| 16 |
- openrc/systemd done right? |
| 17 |
- is it secure? |
| 18 |
- you name it... :) |
| 19 |
|
| 20 |
Maybe we could script some of these to help too. |
Archives