Board Decision: Allow the Community Expansion Committee to broaden the scope
- Proposed at
-
26 June 2024
- Decision owner
- Decision status
-
✅ Accepted, with 5 yes
Attendance and voting
| Board Member | Attendance | Vote |
|---|---|---|
| Olivier Dobberkau | ||
| Stefan Busemann | In meeting | ✅ Yes |
| Boris Hinzer | In meeting | ✅ Yes |
| Rachel Foucard | In meeting | ✅ Yes |
| Susi Moog | ||
| Tymoteusz Motylewski | In meeting | ✅ Yes |
| Thomas Maroschik | In meeting | ✅ Yes |
Decision description
Facts/Problem
- The Community Expansion Committee (CEC) started to engage with countries mostly in the South and East (developing countries).
- The general concept of offering a standardized approach for governmental websites is successful - not only in developing countries.
- On several occasions, contacts with leads in countries in Europe have been created.
- The Community Expansion Committee is currently limited to developing countries.
- We should avoid multiple parties going to the same institution/country without knowing it. So exchange of information between the Committee, the Board and the TYPO3 GmbH (including the project ambassador) needs to happen.
- The CEC is collecting information about countries and their potential for TYPO3 in the public sector in a structured way; the idea is to use it also for other countries.
Objective
The CEC wants to create more leads for the standardized approach for governmental websites within Europe.
Obligations to cooperate
TYPO3 GmbH / TYPO3 Association Board - to avoid duplicate efforts.
Financial and human resources impacts
- None on short notice.
- In the medium term, the team needs to grow to spread the tasks over several shoulders. More activities can lead to the need to increase the funds in later years.
Resolution/Petitum
Allow the Community Expansion Committee to approach countries within Europe as well, and to be a go-to place to inform if somebody was approached by a country/public institution, so information is tracked in one place (right now, even if some country is using TYPO3, we often don't know it, which makes communication hard).
Discarded alternatives
None
Attachments
None
Comments
None