Meetable events should clearly show event author/organizer and creation datetime
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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/)
- Dominant language
- PHP
- Stars
- 171
- Forks
- 14
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aaronpk/Meetable
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 40/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
All issues in aaronpk/Meetable
Similar issues
-
bug-report bug-report-triage customer report
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Codeinwp/tweet-old-post#1177 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
sonata-project/dev-kit#3119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
🧠 Admin
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
RSA PKCS#1 v1.5 verify fails for SHA-512/224, SHA-512/256 and SHA-3 (UnhandledMatchError on 4.x)Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day