Show tester and organizer activity rankings from recorded participation #71

New issue

Open

opened 2026-11-01 20:12:38 +00:00 by viacheslavshuka · 0 comments

viacheslavshuka commented

2026-11-01 20:12:38 +00:00

Owner

Community statistics should count participation and eligible organizing periods, rather than registrations or announcement volume.

Acceptance criteria

Provide separate tester and organizer rankings on the protected website, defaulting to the last thirty days, with an all-time view and underlying counts.
A tester receives one attended-test credit for full or partial attendance. Several blocks in one test still count once.
Show full and partial attendance counts separately. No-shows, pre-start withdrawals, tentative interest, waiting, and unfulfilled requests add no credit.
Award one organizer credit to each eligible accepted organizer whose role overlaps the test's running period.
Someone who leaves before start or joins only after completion receives no organizer credit. Organizing-restricted intervals do not count as eligible role time.
Later removal or departure preserves earned credit. The site-wide held-test total counts each test once regardless of its organizer count.
Corrections and marking a test never held update tester, organizer, and aggregate totals. Interrupted tests retain actual partial participation and its normal credit.
Organizer credit describes recorded role eligibility and timing, not observed attendance in an external meeting.
Do not provide a ranking opt-out setting. Ranking entries and aggregate counts do not disclose a complete list of tests someone attended.
Preserve historical inputs beyond notification retention. Calculate counts from recorded domain events, not signup or delivery counts.

Validation

Use an independent table of test periods, role intervals, restrictions, full/partial attendance, and expected totals. Check exact period boundaries, several organizers, correction reversal, and no duplicate credit after worker retries. Check the protected API does not expose unrelated testing history.

Dependencies

#47: Manage test co-organizers through accepted invitations. Provides recorded organizer role intervals.
#65: Correct attendance and group familiarity without erasing history. Provides corrected attendance and never-held reversals.
#69: Restrict participation and organizing capabilities with reversible expiry. Provides restriction intervals that affect organizer eligibility.

#68: Generate alphabetical tester acknowledgment lists

Community statistics should count participation and eligible organizing periods, rather than registrations or announcement volume. ## Acceptance criteria - Provide separate tester and organizer rankings on the protected website, defaulting to the last thirty days, with an all-time view and underlying counts. - A tester receives one attended-test credit for full or partial attendance. Several blocks in one test still count once. - Show full and partial attendance counts separately. No-shows, pre-start withdrawals, tentative interest, waiting, and unfulfilled requests add no credit. - Award one organizer credit to each eligible accepted organizer whose role overlaps the test's running period. - Someone who leaves before start or joins only after completion receives no organizer credit. Organizing-restricted intervals do not count as eligible role time. - Later removal or departure preserves earned credit. The site-wide held-test total counts each test once regardless of its organizer count. - Corrections and marking a test never held update tester, organizer, and aggregate totals. Interrupted tests retain actual partial participation and its normal credit. - Organizer credit describes recorded role eligibility and timing, not observed attendance in an external meeting. - Do not provide a ranking opt-out setting. Ranking entries and aggregate counts do not disclose a complete list of tests someone attended. - Preserve historical inputs beyond notification retention. Calculate counts from recorded domain events, not signup or delivery counts. ## Validation Use an independent table of test periods, role intervals, restrictions, full/partial attendance, and expected totals. Check exact period boundaries, several organizers, correction reversal, and no duplicate credit after worker retries. Check the protected API does not expose unrelated testing history. ## Dependencies - [#47: Manage test co-organizers through accepted invitations](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/47). Provides recorded organizer role intervals. - [#65: Correct attendance and group familiarity without erasing history](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/65). Provides corrected attendance and never-held reversals. - [#69: Restrict participation and organizing capabilities with reversible expiry](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/69). Provides restriction intervals that affect organizer eligibility. ## Related work - [#68: Generate alphabetical tester acknowledgment lists](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/68)

viacheslavshuka added the

labels

2026-11-01 20:14:45 +00:00

viacheslavshuka referenced this issue

2026-11-01 20:16:18 +00:00

Attribute groups to registered and unregistered authors #37

viacheslavshuka referenced this issue