Review components and keywords, define labels for future use

[mkoeppe]

component_frequency.txt

keyword_frequency.txt

[kwankyu]

So the migration is a good time to update the components list? Would there be a corresponding (fixed) list in Github?

I don't know if we have anything to do with keywords though. They are just whatever the authors chose.

[mkoeppe]

Yes, our script maps components to labels of the form "component: ...."

The set of labels is fixed for the repository (can only be changed by privileged users), and it needs to be a small list because the UI is a dropdown list for all labels. (Our prefix "component: " makes sure that they are kept together in the list.)

Removing component labels later is tricky because it amounts to removing historical information. (I think but have not tested that removing a label also removes the events that indicate adding this label.)

[kwankyu]

Outdated!

github labels for components:

Code	label	color	frequency
MF	foundations & categories		3682
MS	symbolics & calculus		3472
MM	numerical		880
MA	algebra		6115
ML	linear algebra		2338
MG	geometry & topology		3720
MC	combinatorics		5477
MP	graph theory		3454
MN	number theory		4152
MX	mathematics		1576
IL	programming		3720
IP	packages		7624
ID	documentation		4796
IT	doctest		2178
IB	build		4008
II	interfaces		2234
IG	graphics		1820
IU	user interface		3108
IR	refactoring		1210
ID	distribution & porting		2270
IX	miscellaneous		3595

[kwankyu]

Outdated!

Mapping trac components to github labels:

Code	trac component	frequency
MC	combinatorics	5477
IP	packages: standard	5313
ID	documentation	4740
MP	graph theory	3454
IB	build	3362
MA	algebra	2990
IL	python3	2540
MS	symbolics	2390
IX	misc	2350
ML	linear algebra	2338
MF	basic arithmetic	2232
IU	notebook	2100
II	interfaces	1938
IG	graphics	1820
IP	packages: optional	1806
MG	geometry	1742
IT	doctest coverage	1572
MA	commutative algebra	1406
MN	number theory	1392
MG	algebraic geometry	1182
IR	refactoring	1138
MS	calculus	1082
MN	elliptic curves	974
MN	number fields	936
IU	user interface	898
MM	numerical	880
MN	modular forms	850
MA	group theory	828
ID	porting: cygwin	782
MF	categories	754
ID	porting	708
MF	coercion	696
ID	distribution	664
IB	build: configure	610
IT	doctest framework	602
IX	scripts	600
MA	padics	568
IL	cython	468
MX	coding theory	442
ID	porting: solaris	428
IL	performance	370
IL	memleak	342
MG	manifolds	330
II	interfaces: optional	296
IP	packages: experimental	284
MC	combinatorial designs	270
MG	algebraic topology	266
MX	linear programming	264
MX	asymptotic expansions	258
MN	quadratic forms	252
MX	cryptography	228
MA	finite rings	217
MG	dynamics	200
IP	packages	199
MC	matroid theory	196
IX	website/wiki	190
MX	finite state machines	156
IX	c_lib	136
ID	debian-package	130
IX	pickling	120
IU	interact	110
IX	dsage	108
MA	factorization	106
MX	statistics	104
ID	porting: bsd	88
IR	relocation	72
ID	porting: aix or hp-ux	70
ID	docker	64
ID	translations	56
MX	finance	54
MX	game theory	54
IX	spkg-check	46
IB	pbuild	36
XX	linbox	30
IP	packages: huge	22
MX	fractals	8
IX	sage-mode	8
MX	databases	8
IX	fast callable	6
IT	doctests	4
IX	givaro	1

[kwankyu]

Maybe, 21 component labels are still too many?

[kwankyu]

Apart from mapping trac components to github labels, we may want to leave the trac component in the issue's description.

[kwankyu]

After we decide the maximum number of github component labels, I could request a help on sage-devel.

[mkoeppe]

What is the purpose/meaning of the two-letter code?

[mkoeppe]

After we decide the maximum number of github component labels, I could request a help on sage-devel.

This is definitely a good topic for sage-devel. A brief previous discussion on this happened in https://groups.google.com/g/sage-devel/c/2dKvRwdwVQM/m/dDmGmheFAgAJ

[kwankyu]

What is the purpose/meaning of the two-letter code?

That is to organize the mapping from trac components to github labels, as a temporary stepping stone.

Also it groups the github labels by:

initial letter	group
M	mathematics
I	infrastructure
D	distribution

and X for miscellaneous or anything. The second letters were chosen arbitrary.

[kwankyu]

The number of labels, presently 21, is adequate? Could we increase?

[mkoeppe]

In addition to the label name, we can also play with the label's color and text_color.

[mkoeppe]

The number of labels, presently 21, is adequate? Could we increase?

I'll have a version of the imported repository ready later today, then we can check how things feel on the UI side of things

[jhpalmieri]

Is there a limit on the length of each label? If I had an issue related to categories, I am not sure that I would realize it should belong under "Foundation" (or "Foundations"), but a longer label might capture that. Similarly, "Geometry & Topology" would be better than "Geometry", especially since topology is not geometry. "Symbolics & Calculus".

Does "Refactoring" need to be a label?

Re colors: I like the idea of using one color for the M labels, another for I, etc.

[mkoeppe]

Is there a limit on the length of each label?

I don't know if there's a hard limit, but probably we shouldn't make it much longer than "component: interfaces: optional" so that the display in the issue list does not become unwieldy
(see the very preliminary issue list at https://34.105.185.241/sagemath/sage-20230110084128/issues)