2018-08-09 Regular Team Meeting¶
Attendees: Daniel Siepmann, Martin Bless, Nikolai Townsend
Excused: Sybille Peters
Beginning of the meeting: 09:00 UTC, 11:00 CEST, 16:00 ICT (Indochina Time)
- Team sprint took place in Münster, July 27-28, 2018: Too bad, the report still has to be written. Main result: We are trying to assign assignees to pull requests and issues.
- Moving forward rendering to Bamboo (Daniel S.) - https://jira.typo3.com/browse/DOCS-9
- Cleanup Changelog 8.x breaking changes and important (Daniel S.) - https://review.typo3.org/#/c/57829/
- Use Google docs instead of this etherpad the written notes? We talked about it. We don't want too many ways to do the same thing. But there are no strong objections not to use them. In case it somewhen makes sense we probably can create a Google drive folder with write permissions for all team members. And create Google docs therein.
- Q: What does https://jira.typo3.com/browse/DOCS-16 mean? ("Render TYPO3 core extensions from standalone repositories"?) A: Ah, there is https://github.com/typo3-cms/ By means of "subtree split" all system extensions have their own repository there.
- Talk about the "viewhelper reference" stuff? No, we didn't. Except: Interesting stuff is going on.
- Q: "Looking at other open source projects: The TYPO3 documentation could have a better structure, a better homepage, …" Is that of interest to the team? A: Definitely! You are bumbing into open doors. Please write down something about what you found. You don't have to do it in public. Email, GoogleDocs, anything will do.
- The idea of "key topics ("Schwerpunktthemen")
We came up with the idea of key topics ("Schwerpunktthema"). For example: ① The docs.typo3.org homepage should be better. ② Can we use elasticsearch for a global search? ③ Find a solution for the viewhelper reference, ④ …
Treating identified problems or task as "key topic" means: Let's collect ideas, resources, links and thoughts in a way (which still has to be found) that makes it possible to present the task to our TYPO3 community and ask for help. So we could do a "RFC", a "request for collaboration". We could address the TYPO3 community like this: "Hello, we, the TYPO3 documentation team has identified a task where we need your help. The task is (for example) to improve the docs.typo3.org startpage. Are you interested? Would you like to help? Would you be willing to attend a sprint and work on this task there, together with some more people willing to do the same?"
Thinking of this as "key topic" may be more productive than "just" creating more issues.
- We had a lively conversation about Elasticsearch and the Docker container.
- The next regular meeting will be Thursday, September 20, 2018 11:00 CEST, 09:00 UTC. ATTENTION: As an exception this is the 3rd, not the 2nd Thursday of the month.
End of the meeting: 10:25 UTC, 12:25 CEST, 17:25 ICT
The notes: https://notes.typo3.org/p/T3DocTeam-2018-08-09
Moved to Forge wiki: https://forge.typo3.org/projects/team-docteam/wiki/2018-08-09_Team_meeting
Forge overview: https://forge.typo3.org/projects/team-docteam/wiki/index