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