Meetable events should clearly show event author/organizer and creation datetime
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 22/100
Direzione di ricerca
The payload names no files, so start by finding where event pages are rendered and where an event's creator is recorded when it is saved. Check whether the IndieAuth sign-in identity is stored with the event at all, since that decides whether this needs a schema change. Done means each public event page shows the organizer (with h-card name and photo, or the domain as a fallback) and the creation datetime. The thread has had no comment in about six years and no decision on the approach, so confirm with the maintainer before writing code.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Typical popular events sites and services (Google Calendar, Facebook) prominently show who created and is organizing events, as well as when they were created. Meetable should do this by default, at a minimum using the author’s personal site they used to sign-in via IndieAuth, and the datetime at which they created the event.
The author’s personal site can be parsed for a representative h-card to use for their display name and image (h-card name and logo or photo), though even showing the domain name of the author would be useful (absent an h-card display name or logo/photo).
This would at a minimum be very useful for the events.indieweb.org deployment of Meetable, as that was used to replace use of the wiki for events which had this information implicitly in the browsable edit history.
Who created it use-cases: knowing who created an event helps clarify the potential legitimacy of the event and/or how much help the organizer may need (is it a known organizer of such events, the usual person, or a new person but still known to the community, or a random person who may need help). Additionally, having a clear organizer helps provide at least a default contact for any Code of Conduct follow-ups.
When was it created use-cases: it is useful to know the when created information as a method for if an event was created long in advance and might not still be happening, or if it was created very recently and thus is much more likely to be happening.
This information should be prominently publicly displayed on Meetable event pages.
(Originally published at: https://tantek.com/2020/062/b1/)
- Lingua principale
- PHP
- Stelle
- 171
- Fork
- 14
- Merge medio
- 1m
- PR unite (30g)
- 1
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di aaronpk/Meetable
-
Difficoltà 2/5 Mezza giornata Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 40/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 35/100
-
enhancement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 30/100
Tutte le issue di aaronpk/Meetable
Issue simili
-
[Sync EN] Pdo\Pgsql: document session state reset on persistent connections (PHP 8.6) (#6084)Forse già presa @lacatoire l’ha presa oggi. Apertasync-en
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Potential Bug To Triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
matomo-org/matomo#25740 ·
I maintainer di solito rispondono entro 1 giorno
-
[Type] Bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
WordPress/ai#1386 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
E2E setup scripts seed the legacy `payment_request` settings keys instead of `express_checkout`Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
woocommerce/woocommerce-gateway-stripe#6201 ·
I maintainer di solito rispondono entro 2 giorni
-
bug status: unverified
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno