1 |
Hi, |
2 |
|
3 |
The previous thread covered a few topics, in this one I'd like to focus |
4 |
on the data collected. So far people have indicated a few different |
5 |
kinds of data they'd find useful. However, I don't think enough |
6 |
attention has been put on explaining why they need the data and how |
7 |
they'd use it. |
8 |
|
9 |
I think we shouldn't collect any data unless we have a good plan on how |
10 |
we'd be able to use it. In this thread, I'd like to collect ideas |
11 |
on what data to collect and how it could realistically be used. |
12 |
|
13 |
I'm going to start with the data and uses I can think of. Please reply |
14 |
with other things you can think of. |
15 |
|
16 |
|
17 |
1) list of selected packages (@world) |
18 |
|
19 |
We would use this to determine the popularity of individual packages, |
20 |
plus by scanning their dependencies we would be able to make combined |
21 |
statistics for direct usage + dependencies of other selected packages. |
22 |
This would allow us to judge which packages need more of our attention. |
23 |
|
24 |
For example, as we port Python packages to Python 3.8 the packages with |
25 |
more declared users would be ported first. |
26 |
|
27 |
|
28 |
2) USE flags on installed packages (disabled/default/enabled) |
29 |
|
30 |
This would allow us to determine which flags users are most likely to |
31 |
actually rely on. This could determine tested flag combinations, |
32 |
defaults, and required level of support for individual flags. |
33 |
|
34 |
For example, if OCaml bindings on some package are broken and require |
35 |
a lot of work, I would find useful to know how likely it is that anyone |
36 |
is using it. Or if a lot of people are enabling 'frobnicate' flag, |
37 |
I could consider employing USE defaults. |
38 |
|
39 |
|
40 |
3) System profile |
41 |
|
42 |
This would primarily allow us to establish how transition to new |
43 |
profiles proceeds and could influence the decision on prolonging |
44 |
the support for old ones. As a side effect, we'd have stats on how |
45 |
popular different architectures are. |
46 |
|
47 |
For example, it would help us see whether people are moving away from |
48 |
amd64 17.0 to 17.1. |
49 |
|
50 |
|
51 |
4) Arch - installed package correlation |
52 |
|
53 |
This one could be considered a bit invasive but it would help us |
54 |
determine how important is keeping particular arch keywords |
55 |
on a package. |
56 |
|
57 |
For example, package A breaks on SPARC. Fixing it would require |
58 |
significant effort. If we know it has users on SPARC we're more likely |
59 |
to put that effort; otherwise, we may just drop SPARC keywords and move |
60 |
on. |
61 |
|
62 |
|
63 |
That's all really useful stuff I can think of right now. What's your |
64 |
angle? |
65 |
|
66 |
-- |
67 |
Best regards, |
68 |
Michał Górny |