sbp commented on issue #32: URL: https://github.com/apache/tooling-trusted-release/issues/32#issuecomment-2815556675
The distribution of ASF member participation in projects associated with a committee (I will call this umbrella structure a "group") is as follows, if the data sources we're currently using in ATR are accurate: ``` Count | # Users ------|-------- 0 | 0 1 | 5210 2 | 2640 3 | 448 4 | 134 5 | 78 6 | 43 7 | 32 8 | 15 9 | 10 10 | 9 11 | 12 12 | 7 13 | 1 14 | 2 15 | 1 16 | 0 17 | 0 18 | 1 19 | 0 20 | 0 ``` (There are also a few members participating in more than 20 groups; the most is `jbonofre`, who participates in 36.) There are 8647 members. 7850 of those (~91%) are participating in only 1 or 2 groups. 8298 (~96%) participate in only 1, 2, or 3 groups. This suggests that we should just show all committees, (sub)projects, and draft / candidate / preview releases on one page. For most users this is going to be a few cards, maximum. We should not show finished releases on the landing page, because this will be overwhelming. The top of the page could have a list of alphabetical buttons to skip to the right section. I don't think that the landing page, or many interior pages, should mention "PMC", "committee", or "(sub)project" terminology at all. Just give the names of the groups; that's enough to recognise what's going on. The ontology of the organisation is not indispensible information. To aid those few users who are in many groups, we could have one list of groups that have any draft / candidate / preview releases at the top, and another list of those that don't at the bottom. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For additional commands, e-mail: dev-h...@tooling.apache.org
