Verified Commit 8f0363ec authored by Daniel Siepmann's avatar Daniel Siepmann
Browse files

Add Meeting minutes from 29th March

parent d31bfd67
Meeting Minutes March 29
========================
.. contents::
:local:
Goal of this meeting was to get in contact with demo.typo3.org team.
Introduction round to introduce each team member to everyone else.
Let the demo team know what we do.
Also see: https://git.typo3.org/qa/internal-organization/-/blob/master/Documents/OurMission.rst
Understand what the demo team does.
They want to provide a demonstration especially for users of TYPO3, editors for exmple.
So main focus is on integration and polished backend.
The team is always meeting on last Tuesday each month at 3pm Europe/Berlin.
Come to a conclusion whether it makes sense to have a single repository for demo.typo3.org and best practices. If so, we can plan the next steps to continue working together.
We came to conclusion that it would make totally sense to work together.
URL to repository:
https://git.typo3.org/services/demo.typo3.org/site
URL to demo installation:
https://demo.typo3.org
URL to demo team:
https://typo3.org/community/teams/demo-project
URL to demo team Slack Channel:
https://typo3.slack.com/archives/C92E7HUDU
Next Steps
----------
Add to readme of demo.typo3.org that this project is also an example for studying and copying.
The demo team will move communication over to their public channel https://typo3.slack.com/archives/C92E7HUDU so we can exchange information and discussions.
And they will also move their monthly call over to the public Slack Channel.
Daniel will write a typo3.org news (interviewing David from demo team) promoting the joined effort.
And also promoting existing demo.typo3.org state as current best practice.
The news should also be used to promote actively community work. Everyone is welcome
to provide feedback, e.g. open issues and provide merge requests and participate in public slack channel. (Use call to action).
Come up with clarifications as documentation and additions.
E.g. why were certain decisions made the way they were (e.g. the testing framework on EXT:tea).
This task will not be assigned to anyone specific right now. We will discuss and re assign if there are no results.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment