Metadata Fields for v0

	A	B	C	D	E	F	G	H	I	J	K
1	Metadata	Description	Required	Pypi source	Github Source	Full view	Stub view	Filter on	Sort on	Search
2	Plugin Name		Required	pypi:info/name	--	✅	✅	⛔	✅	✅
3	Summary		Encouraged	pypi:info/summary	e.g.: .napari/hub.yml	✅	✅	⛔	⛔	✅
4	Description	Long description, in markdown or restructured text	Encouraged	pypi:info/description & pypi:info/description_content_type	e.g.: .napari/README.md	✅	⛔	⛔	⛔	✅
5	Author(s) w/ email	email should not be displayed on the site, but should be used as a unique identifier for filter, etc	Encouraged	pypi:info/author & pypi:info/author_email	e.g.: .napari/hub.yml	✅	✅	✅	⛔	⛔
6	License	Short name	Encouraged	pypi:info/license	--	✅	✅	✅	⛔	⛔
7	Python version(s)	List of minor versions of Python that are supported (3.7, 3.8, 3.7, etc)	Encouraged	pypi:info/requires_python	--	✅	⛔	✅	⛔	⛔
8	Operating System		Encouraged	inspect the wheel name? idk	--	✅	⛔	✅	⛔	⛔
9	Requirements		Encouraged	pypi:info/requires_dist	--	✅	⛔	⛔	⛔	⛔
10	Project Site	URL of main project site	Supported	pypi:info/home_page	e.g.: .napari/hub.yml	✅	⛔	⛔	⛔	⛔
11	Documentation	URL of documentation	Encouraged	??	e.g.: .napari/hub.yml	✅	⛔	⛔	⛔	⛔
12	Support	URL of support forum	Encouraged	??	e.g.: .napari/hub.yml	✅	⛔	⛔	⛔	⛔
13	Report issues	URL to report issues	Encouraged	??	e.g.: .napari/hub.yml	✅	⛔	⛔	⛔	⛔
14	Twitter	handle of project twitter	Supported	??	e.g.: .napari/hub.yml	✅	⛔	⛔	⛔	⛔
15	Code repository	Link to github or gitlab	Encouraged	??	e.g.: .napari/hub.yml	✅	⛔	⛔	⛔	⛔
16	Github stars		Encouraged	not in json	--	✅	⛔	⛔	⛔	⛔
17	Github forks		Encouraged	not in json	--	✅	⛔	⛔	⛔	⛔
18	Github issues & PRs		Encouraged	not in json	--	✅	⛔	⛔	⛔	⛔
19	Release date	most recent release	Required	pypi:releases/<latest>/upload_time_iso_8601	--	✅	✅	⛔	✅ (default)	⛔	Would enable "recently updated" feature on landing page
20	Version	of most recent release	Required	pypi:releases/<latest>	--	✅	✅	⛔	⛔	⛔
21	First released		Required	pypi:releases/<first>/upload_time_iso_8601	--	✅	⛔	⛔	✅	⛔	Would enable "new plugins" feature on landing page
22	Development Status		Encouraged	pypi:info/classifiers: "Development Status"	--	✅	⛔	✅	⛔	⛔
23	Topic		Supported	pypi:info/classifiers: "Topic" (would need further parsing)	e.g.: .napari/hub.yml or github tag?						Note: better to use as search than filter b/c free form
24
25
26
27			Required	This is basically guaranteed to exist in PyPI. Design and engineering can assume that this will exist.
28			Encouraged	This is not strictly required by PyPI, but we will encourage devs to include the info, though dev utilities (cookiecutter, devtools, etc) and, where appropriate, design (e.g. greyed out with tooltip that developer did not provide this info). A plugin's profile will be lacking without this info
29			Supported	If the developer contributes this metadata, we will present it. If they don't, we should simply omit it.
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100