1 |
Perhaps it's a good idea to add a section to the devmanual about adding |
2 |
new keywords to packages. |
3 |
|
4 |
Recruits in particular might benefit from some background on what |
5 |
keywording means and when it should be done, especially before they |
6 |
start maintaining packages and then realise their packages are so |
7 |
beautiful that they positively *deserve* to have some random keywords |
8 |
added. This is not productive. |
9 |
|
10 |
The way it works is that users of |
11 |
specific architectures find that a package works for them on their |
12 |
systems (which have enough resources and have the correct interfaces for |
13 |
that particular program to be used conveniently, and so on), and that |
14 |
they then request that their architecture keyword be added. What |
15 |
doesn't work is having a handful of keywords on a package that nobody |
16 |
cares about who actually uses the architectures in question. |
17 |
|
18 |
Since over the years the Random Keyword Requests happen a *lot* right |
19 |
after recruitment, it might even be useful to ask about this in the |
20 |
quizzes. (The answer: your time is better spent fixing actual bugs. |
21 |
bumping versions, adding features and maintaining a stable branch, |
22 |
rather than raising the architecture count for your packages for no |
23 |
adequately explored reason.) |
24 |
|
25 |
|
26 |
Kind regards, |
27 |
jer |