Daniel Siepmann (cb5cdd2a) at 04 Mar 17:54
Add meeting minutes 04.03.2024
Daniel Siepmann (27c67081) at 04 Mar 17:53
Add meeting minutes 04.03.2024
Create tickets (on GitHub) to add links from source code to the official docs.
We decided to use PHPDoc @see
and link to v11.4 and v12.4 (always the currently supported versions).
Use repobeats, create PR and issue
That's because we plan to join and use the same timing. We need that to calculate budet upfront.
Comment on older PRs and ask if we can close them
Contact hotel and book rooms about on-site sprint before T3DD
check with budget
create blogpost about codesprint 7th May, 11am - 7pm (Europe/Berlin)
Topics defined as in: https://git.typo3.org/qa/internal-organization/-/blob/master/MeetingMinutes/2024/02/05.md#decision-our-first-remote-code-sprint-daniel
Build (or search for existing solutions) to check links in our source code. This should be added to CI to ease the burdon of maintaining the link introduced by #44
Background: Having two separate plugins for the list and single view makes setting up the extension more work, and (for real-world extension) it also produces the problem of having to stop Google from indexing the single view page without any Tea UID in the URL, while allowing it to index the single view page with a Tea UID in the URL. News has this setup as well, but it also has a combined list/single view plugin that solves these problems.
There is no community sprint.
Daniel Siepmann (670a9adf) at 19 Feb 17:34
Add meeting minutes 19.02.2024
Check if it's suitable for ext:tea and implement https://github.com/staabm/phpstan-todo-by
CHeck if it's suitable https://github.com/TomasVotruba/cognitive-complexity
Check if it's suitable for ext:tea, implement if so https://github.com/spaze/phpstan-disallowed-calls
Thanks for your feedback. Yeah I would like the approach to separate code and none code. I added that to the agenda.
Thanks for referencing the issue. I'll close this one here.