palladius / palladius/rubycon.it
Inconsistent timings for the schedule
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Problem:
The current schedule has highly inconsistent talk durations and some unrealistically short breaks, which creates confusion for speakers preparing their talks and discomfort for attendees:
- Inconsistent Talk Durations: Ranged seemingly at random from 30m, 35m, 40m, to 45m.
- Unrealistic Coffee Break: The morning coffee break was listed as lasting only 5 minutes (from 11:15 to 11:20), which is impossible for attendees to actually get coffee and return.
Proposed Solution:
Standardize the schedule ensuring all speakers get between 35 and 45 minutes slots, coffee breaks are no longer than 15 minutes, lightning talks expanded to a full hour, and Piadina wrap is shranked to 20m.
| Event | Old Schedule Start | Old Duration | New Schedule Start | New Duration |
|---|---|---|---|---|
| Check-in | 08:30 | 60m | 08:30 | 60m |
| Welcome | 09:30 | 15m | 09:30 | 15m |
| Keynote (Carmine) | 09:45 | 45m | 09:45 | 45m |
| Talk 1 (Julia) | 10:30 | 45m | 10:30 | 40m |
| ☕️ Break | 11:15 | 5m | 11:10 | 15m |
| Talk 2 (Silvano) | 11:20 | 35m | 11:25 | 40m |
| Talk 3 (André) | 11:55 | 30m | 12:05 | 40m |
| 🍝 Lunch Break | 12:25 | 90m | 12:45 | 75m |
| ⚡️ Lightning Talks | 13:55 | 50m | 14:00 | 60m |
| Talk 4 (Michele) | 14:45 | 35m | 15:00 | 35m |
| Talk 5 (Akira) | 15:20 | 30m | 15:35 | 35m |
| ☕ Break | 15:50 | 20m | 16:10 | 15m |
| Talk 6 (Marco) | 16:10 | 35m | 16:25 | 35m |
| Talk 7 (Yara) | 16:45 | 45m | 17:00 | 40m |
| Wrap (Riccardo) | 17:30 | 30m | 17:40 | 20m |
| Drinks | 18:00 | 120m | 18:00 | 120m |
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file or test is named in the issue. Find the repository content that renders the event schedule, compare it with the proposed new timings in the issue, update the schedule entries, and verify that the displayed agenda matches the table and remains chronologically consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100