Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Switch DTC event Q&A to the shared community-base event_qna app

Aperta
  • Qualcosa non va?
#458 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
django, python
Ambito
authorization, backend, web-dev

Direzione di ricerca

This is a multi-repository extraction plan, not a single change. Start by reading the existing event_qna/ app and templates/events/qna/ in DataTalksClub/website, then docs/plan/phase-4.md and docs/04-quality-gates.md in community-base. Nothing here names a concrete first edit, and the access policy hook and agenda items still need design. A finished contribution would be agreed with the maintainers in a scoped sub-issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Depends on the community-base extraction (tracking AI-Shipping-Labs/website#1930).

Reporter intent

Alexey wants event Q&A on both community sites from one shared implementation. Today DataTalksClub/website has a Django-native event_qna app (EventQnaSession, EventQnaQuestion, EventQnaVote, EventQnaCohostInvite; host, present, public and cohost views; Studio page; pluggable backend with native first; see event_qna/ and templates/events/qna/ in ~/git/dtc-website). AI Shipping Labs has no event Q&A. The separate serverless ~/git/dataqna service (qna.dtcdev.click) stays for anonymous rooms and podcasts and is out of scope.

Decisions from the intake conversation

  • Django-native, not an integration with the dataqna service.
  • One Q&A session per event. A course office hour is an event, so it has its own Q&A; there is no per-course standing list.
  • Access follows the event's own access level: open (free) events are open to anyone with the link who has a free account (sign-in required, anonymous is not allowed on AI Shipping Labs); events gated to Basic, Main or Premium are open only to members at that level, exactly like who can see or join the event. Registration is not required (people may arrive from other sources). The DataTalks.Club site keeps its current fully open behaviour, so the rule is configurable per site (a policy hook), not hard-coded.
  • Questions can be asked from the moment the event is published until it ends, including before the event and during it. Attendees can upvote. Participants can attach files (the dataqna feature set the reporter wants: uploads) if the existing event_qna supports it; groomer to confirm and list the gap.
  • Presenter/host view for the livestream (existing present and host views), co-host invites as in DTC.
  • Courses: office hours appear as part of the curriculum. Everyone in the course sees the Q&A on the curriculum page and can ask in advance. The course admin can add their own items to the list (pinned agenda items: things to talk about), shown distinctly from member questions.
  • Carrying unanswered questions over to the next office hour is a possible later step, not v1.

Delivery shape (three repositories)

  1. DataTalksClub/community-base: new package app (working name event_qna) extracted from the DTC implementation, with the access policy hook, agenda items, tests, docs and a release. Plan-driven (docs/plan/), quality gates in docs/04-quality-gates.md; both consuming sites must be tested against the change.
  2. DataTalksClub/website: replace the local event_qna app with the package (data preserved; see phase 4/5 notes in community-base docs/plan/phase-4.md).
  3. AI-Shipping-Labs/website: adopt the package: event page Q&A, access by tier, curriculum integration for course events, agenda items for course admins, Studio, API/docs.

DTC work

Replace the local event_qna app with the package app once released: data and URLs preserved (public ids, QR, co-host links), the open access policy keeps today's behaviour, no downtime for live Q&A sessions, row counts before and after equal.

Lingua principale
Python
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DataTalksClub/website

Tutte le issue di DataTalksClub/website

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.