Document the first-version product scope in the README #4

Open
opened 2026-11-01 20:10:59 +00:00 by viacheslavshuka · 0 comments

The README advertises availability editing through the bot. Availability editing belongs in website forms, with navigation from the bot.

Update the product introduction so contributors can understand the intended first version. Keep planned behavior distinct from implemented behavior.

Acceptance criteria

  • The introduction identifies a free, open-source application for one tester community. It preserves the repository's existing MIT license.
  • The account description includes Telegram login and mandatory verification of one rating profile.
  • The bot description covers basic actions and links to website forms for availability and other detailed editing.
  • The material description explains reusable author blocks, rounds, and packages. It does not promise individual-question tracking or exact counts of familiar questions.
  • The README states that question texts and answers remain outside Quorum. It does not advertise document imports or editor synchronization.
  • Meeting links come from organizers. The README does not promise automatic Jitsi rooms or another meeting-provider integration.
  • The description includes Russian-first localization, a responsive website, session discovery, and moderation controls where relevant to the introduction.
  • Planned features remain labeled as planned until their implementation exists. Links to contributor instructions describe commands that the repository actually provides.
  • The update introduces no payment, multi-community, private published-test, or built-in discussion feature.

Validation

Check each feature statement against this ticket's criteria and the current repository. Check links and the distinction between planned and available behavior.

The README advertises availability editing through the bot. Availability editing belongs in website forms, with navigation from the bot. Update the product introduction so contributors can understand the intended first version. Keep planned behavior distinct from implemented behavior. ## Acceptance criteria - The introduction identifies a free, open-source application for one tester community. It preserves the repository's existing MIT license. - The account description includes Telegram login and mandatory verification of one rating profile. - The bot description covers basic actions and links to website forms for availability and other detailed editing. - The material description explains reusable author blocks, rounds, and packages. It does not promise individual-question tracking or exact counts of familiar questions. - The README states that question texts and answers remain outside Quorum. It does not advertise document imports or editor synchronization. - Meeting links come from organizers. The README does not promise automatic Jitsi rooms or another meeting-provider integration. - The description includes Russian-first localization, a responsive website, session discovery, and moderation controls where relevant to the introduction. - Planned features remain labeled as planned until their implementation exists. Links to contributor instructions describe commands that the repository actually provides. - The update introduces no payment, multi-community, private published-test, or built-in discussion feature. ## Validation Check each feature statement against this ticket's criteria and the current repository. Check links and the distinction between planned and available behavior. ## Related work - [#27: Complete registration through verified rating-profile control](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/27) - [#28: Edit recurring availability with date overrides and overnight slots](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/28) - [#45: Browse tests and open website forms through the Telegram bot](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/45) - [#35: Create and reuse author blocks, rounds, and packages](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/35) - [#56: Manage organizer-supplied access links for tests](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/56)
Sign in to join this conversation.
No description provided.