Code sprint 2024‐05‐07
Daniel Siepmann edited this page May 7, 2024
·
8 revisions
2024-05-07 from 9am to 3pm UTC
Team Channel on typo3.slack.com
Kanban board
9am kick-off huddle (UTC) agenda:
- welcome!
- times: 9am – 3pm
- introduction round
- explain sprint goals
- sprint rules
- explain board, huddle
2:30 finishing huddle (UTC) agenda:
- Party, e.g. number of commits and tasks done today.
git fetch; git log --format=format:"%h %an %s" f8ff931..origin/main
https://github.com/FriendsOfTYPO3/tea/commits/main?since=2024-05-07&until=2024-05-07 - Create photo (screenshot of huddle) from all participants. Participants can leave the huddle or turn off camera if they prefer not to be on the photo as real human but with their avatar or not at all).
- Everyone: What can you part on, which overall goal did you reach, suggestions for next time?
- Is anyone willing to write a news for typo3.org?
- Mention upcoming sprint date and focus (if decided yet).
- Mention next team call on Slack.
- Archive the Done column.
- Check out our https://github.com/FriendsOfTYPO3/tea/blob/main/CONTRIBUTING.md
- Please install ext:tea https://github.com/FriendsOfTYPO3/tea/
You can use the introduction package as a TYPO3 base, or use https://github.com/oliverklee/TYPO3-testing-distribution.
Feel free to use ddev for local development: https://ddev.readthedocs.io/en/stable/ - Ensure the extension is working.
- Please share your GitHub username, so we can invite you.
- There are no stupid questions.
- We go out of our way to treat each other well.
- We all do our best to help each other.
- Ping others via chat if you have questions. That way we can focus on our work and listen to music or whatever helps each of us.
Also check out our general team rules at: https://typo3.org/community/teams/best-practices#c13052
- have a good time
- learn new things
- find out if you'd like to join the Best Practices team
- contribute towards the technical goals
- continue with the tasks that got started during the last sprint
- finish the open runTests.sh tasks
- work on 13.x support
- do the other breaking changes
- @lukaszuznanski
- @oliverklee
- @DanielSiepmann
- @kanow
- @sbuerk
- @deltanart
- @wegewerk-mdt
- Participants are not able to change Status of their own issues (moving them on the board). Probably because boards and status are on Organizational level. Maybe there is a workaround? (Daniel)
- Better prepare description (content) of issues for participants. (Daniel)
- Focus on Berlin times the next time as most participants are from Europe and got confused by UTC times. (Oli)
- Provide Mentors for first-time contributors to get up and running, e.g. installation, running tests, rendering docs, etc. (Oli)
- Define next sprint upfront in order to communicate the date at end of current sprint. (Daniel)