TYPO3 Policy Directory
This directory holds policy documents relating to the TYPO3 Association and related community, product, and project.
This directory holds policy documents relating to the TYPO3 Association and related community, product, and project.
Version 2.0, 20 January 2018
Below you find the regulations of the TYPO3 Association Board in conducting its business. They are the rules of order.
The number and type of Board members are defined in the statutes, the job descriptions can be found in the "Job Descriptions". The "Job Descriptions" of the Board are adapted by a vote of all its members; this also applies to any changes thereof.
Election procedure and term of office are defined by the statutes.
Sequence of a bi-weekly hangout:
- Sticky items
- Board Reports about personal tasks
- Decisions
- Discussions
The Board is working toward the aims of by-laws. Therefore each Board member is part of at least one committee. A committee is introduced by the Board and has to report towards the General Assembly.
A workgroup is a temporary group, to solve a speficic issue. Once the issue is solved, the working group is disbanded automatically.
The official language of the Board is English. Meetings of the Board may be conducted in other languages if all members are able to read, speak and understand this language.
These channels have to be used by all Board members for official internal Board communication:
There are two types of budgets:
As a budget owner, you need to hand in a budget application form. Please send a copy or the link of your application to budget(at)typo3.org
Your budget application can contain three different types of costs:
Note
Please note: The TYPO3 Association wants to foster contribution with our budgets. Applications with less working time will be preferred.
If the scope of a budget changes during the project / budget period, the budget owner can apply to adapt the budget.
If your request is accepted by the BCC, they will upload the document to “Documents” section of your budget
Please update the purposes of your budget to adapted budget application
When you receive an invoice, please check that it complies with the Travel Expense and Reimbursement Regulations.
The TYPO3 Association wants to support the TYPO3 project, TYPO3 CMS and it's community. We are happy about any ideas, which are working towards our goals and fit with our rules:
Our new by-laws are accepted by the General Assembly 2025 and are in place since July 2025
Under the name TYPO3 Association there exists an Association as stipulated in Art. 60 ff. of the Swiss Civil Code.
The TYPO3 Association has its registered office in Baar (ZG) Switzerland.
The TYPO3 Association promotes the TYPO3 Project, which has the particular purpose of making free software available by issuing open source licenses. The Board reviews the permissible licenses on an annual basis. The TYPO3 Association serves the TYPO3 community. The TYPO3 Association does not strive to make a profit. It supports development of software and makes software products of third parties available to the public. To support further development, the Association charges membership fees and collects donations for development projects.
In addition, the Association is entitled to found subsidiaries and to invest in companies that further the purposes of the Association.
The Association shall be entitled to pursue all commercial, financial and other activities in connection with the purposes of the Association or management of the Association's funds. In particular, the Association shall be entitled to grant loans, guarantees, and other types of financing and assurance for affiliated and related companies in Switzerland and abroad.
The TYPO3 Association is non-partisan and denominationally neutral.
In particular the TYPO3 Association has the following tasks:
On written request, new members shall be accepted through decision of the Association Board via immediate provisional acceptance. Definitive acceptance shall occur through the General Assembly.
If the Association refuses to grant acceptance, then the applicant can contest the decision within 30 days after the application is received by the Association Board for the attention of the General Assembly.
The Association Board and the General Assembly shall decide concerning the acceptance request at their own discretion. They shall not be obligated to provided the reasons for a rejection.
Members shall be authorised to use the Association logo, to demonstrate their membership and their support for TYPO3. Except for this limited purpose, use of the logo shall not be permitted.
Natural or legal persons shall be entitled to join the TYPO3 Association.
Members who have rendered particular service to the TYPO3 Association or its objectives can be elected as honorary members of the TYPO3 Association for life. Honorary members shall be exempt from the membership fee obligation; in all other aspects they are on equal terms with the members.
A member shall be entitled to leave the Association at the end of a memberships year by giving two months notice. The intent to leave the Association board must be declared in writing. The obligations to the Association for the current year of membership must fulfilled.
Moreover, membership shall end upon dissolution of the legal person or death of the member.
Members, who violate statutes, regulations, resolutions, or otherwise act in a manner that is seriously contrary to the interests of the TYPO3 Association, or, who if after two months from the sending of the second written warning indicating exclusion, are still in arrears with payment of the membership fees, can be excluded by the Association Board with specification of the grounds for exclusion.
Before the resolution is passed the Association Board shall give the member an opportunity to state his position. The excluded member shall be entitled to dispute the decision of the Association Board within 30 days after receipt of the excluded member's disputation claim addressed to the General Assembly. In this case the decision of the General Assembly shall be definitive.
A. General Assembly B. The Association Board (Board) C. Auditors D. Business Control Committee E. Committees
The General Assembly is the supreme governing body of the Association. It is convened by the Association Board and takes place in the first half of every year. The Association Board invites the members in writing at the latest 30 days before the meeting (also via email), with specification of the agenda items. The notification period shall begin on the day following the sending of the letter of invitation. The letter of invitation shall be considered as delivered to the member, if it is sent to the most recent address or email address specified in writing by the member to the TYPO3 Association.
The Chair of the meeting shall announce supplementation of the agenda items to the General Assembly at the beginning of the meeting. The General Assembly shall definitively decide concerning requests to supplement the agenda items.
The Association Board shall be entitled to convene an extraordinary General Assembly at any time. One fifth of the members shall be entitled to request the convening of an extraordinary General Assembly in writing or electronically, with specification of the purpose and the reasons. In this case the Association Board shall be obligated to hold the extraordinary General Assembly within 3 months of the request.
Requests addressed to the General Assembly shall be submitted in writing and substantiated to the President at least 14 days before the General Assembly.
The tasks and competencies of the General Assembly are as follows:
Each General Assembly convened in accordance with the statutes shall constitute a quorum. It shall act by simple majority of the voting members present, if nothing to the contrary is stipulated in the statutes.
Participation in the General Assembly shall also possible without physical presence, via electronic transmission ("Internet General Assembly"). With the invitation to the General Assembly the Association Board shall specify whether this type of participation will be offered. A member's request to participate electronically must be received by the Association Board 20 days before the meeting, at the latest. At the meeting location the Association Board shall ensure technically that the votes of the member can be transmitted simultaneously via word and image. Electronic participation in the meeting shall only apply as valid, if the member can be clearly identified. Votes submitted electronically shall be shown separately in the meeting minutes.
Instead of a meeting as a gathering, on request of the Association Board an exclusively electronic meeting can be conducted ("virtual General Assembly"). The same provisions shall apply mutatis mutandi that apply for the General Assembly.
Instead of a meeting by gathering, ballot votes (written majority decisions concerning factual issues) shall also be permitted. For determination of the respectively required quorum, in this case only the valid votes submitted will be evaluated. Electronic voting shall be permitted as long as clear identification of the voting parties is ensured.
For votes of the Auditors and of the Business Control Committee, in a first ballot the absolute majority, in the second ballot the relative majority of the voting members shall apply.
The General Assembly shall decide by open ballot in all cases, unless the General Assembly decides to conduct the vote by secret ballot. On request of a voting member this can be decided with two-thirds majority of the voting members present. In the case of an Internet General Assembly or virtual General Assembly, the Association Board shall ensure that the secret ballot procedure can occur electronically.
Each member shall be entitled to contest decisions that violate the law or the statutes, within 30 days after knowledge of such decisions is obtained.
Each member shall have one vote in the General Assembly. Another member can be authorised in writing to exercise the voting right. The authorisation shall be granted separately for each General Assembly; however one member shall not represent more than the votes of 3 other members. In the case of a tied vote, for property transactions the Chair of the meeting (President, Vice President, or selected Chair for that day shall cast the deciding vote; elections shall be decided by lot.
Double functions on the Association Board and Business Control Committee shall be excluded. Per legal person a maximum of only one person can take a place on the Association Board or on the Business Control Committee. Persons who execute paid orders of the Association shall be excluded from passive eligibility.
The association’s board consists of the president, vice president, actuary, treasurer and at least two other board members (at least 6 members in total).
The term of office for the association’s board is three years according to the financial year or calendar year. Only members of the association can be elected as members of the board. Re-election is permitted. The board has a maximum of 9 members.
At the end of the term of office, elections for the association’s board are held during the general assembly. The first time the board is elected, the elected members select 4 board members whose term of office is only one year in order to ensure continuity in the board (meaning new elections are held each year).
Every association member may nominate themselves or another board candidate for election; nominees have to confirm their candidacy in advance. Written notice of proposed board candidates must be submitted to the board no later than during the general assembly. The association’s board may also be elected prior to the general assembly by online voting. In this case, the members must be granted a reasonable advance term for the announcement of board candidates.
The outcome of the election is decided by counting the votes received by the candidates (in case of tie votes for excess candidates, there shall be a second ballot; in case of another tie vote, the decision is made by lot). The election and assignment of functions (president, vice president, actuary and treasurer) are performed during the general assembly before the start of a new term of office by a simple majority of the attending board members.
The candidate for the office of president must have been a member of the association’s board for at least one year, otherwise the term of office is limited to one year.
The termination of association membership also terminates the office of an association board member.
In case of by-elections during the term of office, the newly elected association board member completes the predecessor’s term of office. Instead of by-elections, the association’s board may also ask the next ranking candidate from the previous election whether they want to move up. If more than three association board members step down during a term of office, new elections are held for all resigned positions during an extraordinary general assembly.
The association’s board can call new elections for the entire board by a simple majority of the entire board.
The Association Board shall be responsible for arranging the Association's affairs. In particular, the Association Board shall be responsible for
Meetings shall be convened by the President of the Association Board, as often as business matters so require. Each member of the Association Board shall be entitled to request a meeting. In this case the meeting must be held within three weeks. The Association Board shall keep minutes of resolutions. By order of the President or on request of a member of the Association Board, votes that have been taken shall be summarised and recorded in the minutes.
The Association Board shall constitute a quorum if at least four of the members of Association Board are present. The Chair can execute circular resolutions. A circular resolution shall only be valid with unanimity of all members of the Association Board.
The Association Board shall strive for consensus in its decisions. The Association Board shall decide through majority vote of the members of the Association Board present. If the vote is tied the President shall cast the deciding vote. On request of a member of the Association Board a vote by secret ballot shall be conducted. Each member of the Association Board shall be authorised to provide a minority opinion to be included in the minutes.
A joint signature of two members of the Association Board shall be required. The President or, in the event that he is hindered, the Vice President together with an additional member of the Association Board, shall sign in each case.
Usually the President presides over the meeting of the Association, and chairs the Association Board. He monitors the TYPO3 Association activity within the framework of the resolutions of the General Assembly and of the Association Board.
The Treasurer ensures the entire accounting and manages the TYPO3 Association's assets. As part of his activity he signs jointly with the President, with the Vice President or with another member of the Association Board.
The General Assembly shall elect for a term of office of one year, a recognised trust agency as auditing authority, which has been approved in accordance with the regulations of the Swiss Audit Supervision Act of 12/16/2005. Even without legal obligation, the Association shall commission the audit authority to conduct an unrestricted audit in accordance with provisions of Art. 729-729c OR. Through resolution of the General Assembly, the General Assembly can dispense with an unrestricted audit of the following Association year.
The audit authority shall audit the bookkeeping, and shall report in writing to the General Assembly and refuse or grant discharge relative to the Treasurer and the Association Board.
The Business Control Committee shall consist of 4 members.
The term of office of the Business Control Committee shall be two years. Election shall occur through the General Assembly. Re-election is permitted. Only members of the Association can be elected to serve as members of the Business Control Committee. With termination of membership in the Association the office of a member of the Business Control Committee shall also be terminated. In the case of by-elections during the term of office, the newly elected member of the Business Control Committee shall complete the term of office of the predecessor. In even years the first half of the members of the Business Control Committee shall be elected, in odd years the second half of the members shall be elected.
The Business Control Committee shall be entitled to review all project loans for expenditure agreement with the loan application, achievement of the cited objectives and cost-efficient project fulfillment. It shall report to the Expert Advisory Board and to the Association Board quarterly and shall report to the General Assembly annually in writing.
The Business Control Committee shall issue Rules of Procedure and shall regulate its tasks and division of responsibility therein.
The Expert Advisory Board and the Association Board shall be entitled to utilise advisory committees or individual persons without decision-making authority for special tasks.
The calendar year shall apply as the fiscal year.
The membership year deviates from the fiscal year. The membership year shall apply individually for each individual member. It shall start with the decision of the Association Board concerning the written membership application.
The TYPO3 Association procures its funds from:
The acceptance fees, as well as the annual fees, are specified by the General Assembly. Increases in fees shall apply effective immediately for all invoices starting from the time of the increase. In exceptional cases, the Association Board shall be entitled to waive fees in whole or in part or defer fees.
At any time, members and third parties shall be entitled to inject funds that Association can freely dispose of for achievement of the Association's objectives (in particular via fund-raising activities).
The Association's expenditures shall be specified with the budget. The budget shall show the appropriated amounts per legal transaction. The budget shall be prepared and decided on by the Expert Advisory Board. Prior to preparing the budget a survey of the members shall be conducted (also possible via electronic means) concerning the project applications. Budget applications shall be formally reviewed by the Treasurer.
In exceptional cases, the Association Board can decide on budget excesses of a maximum of 5% of the total budget amount.
A compensation can be granted to the members of the Association Board of the Expert Advisory Board and of the Business Control Committee. This must be specified in the budget.
For liabilities on the part of the TYPO3 Association, Association assets shall be exclusively liable. The individual member shall only be obligated to pay the acceptance fee as well as the membership fee.
Members who leave the Association or are excluded from the Association shall lose any claim to the Association assets.
Each member shall be given a copy of the statutes. With admission to the club, a member shall acknowledge these statutes and shall be obligated to comply with and honour the resolutions and directives of the responsible governing bodies of the Association.
Amendment of the applicable statutes can be decided by the General Assembly or by an extraordinary General Assembly. Such resolutions shall require the approval of the two thirds of the members present.
For dissolution of the Association, two thirds of the voting members of the TYPO3 Association must be present at an extraordinary General Assembly convened for this purpose. The dissolution shall be effected if three fourths of the voting members present shall approve.
If two thirds of the voting members of the TYPO3 Association are not present, then after 30 days a second extraordinary General Assembly shall be convened. The dissolution shall be effected if four fifths of the voting members present shall approve.
If nothing to the contrary is decided by the extraordinary General Assembly, the Chairman and the Treasurer jointly shall be authorised liquidators. The assets remaining after liquidation is concluded shall be donated to a charitable organization that shall be determined by the extraordinary General Assembly. The provisions above shall apply accordingly if the Association is dissolved for a different reason or loses its legal capacity.
Mergers shall not apply as dissolution of the Association.
The place of jurisdiction for all disputes affecting the membership shall be the court responsible for the registered office of the Association.
The bylaws were approved by the regular general assembly on 11 April 2018 and come into force on the date of the regular general assembly in 2019. They replace the bylaws dated 20 November 2016.
Gültig seit Juli 2025
Unter dem Namen TYPO3 Association besteht ein Verein im Sinne von Art. 60 ff. des Schweizerischen Zivilgesetzbuches.
Die TYPO3 Association hat ihren Sitz in Baar (ZG) Schweiz.
Die TYPO3 Association fördert das Projekt TYPO3, welches insbesondere die Zurverfügungstellung freier Software unter Vergabe von Open Source Lizenzen bezweckt. Der Vorstand überprüft jährlich die zulässigen Lizenzen. Sie dient der TYPO3 Community. Die TYPO3 Association erstrebt keinen Gewinn. Sie unterstützt die Entwicklung von Software und stellt der Öffentlichkeit Softwareprodukte Dritter zur Verfügung. Um die Weiterentwicklung zu finanzieren erhebt der Verein Mitgliedsbeiträge und sammelt Spenden für Entwicklungsprojekte.
Ferner kann der Verein Tochtergesellschaften gründen und sich an Unternehmen beteiligen, die dem Vereinszweck dienen.
Der Verein kann alle kommerziellen, finanziellen und anderen Tätigkeiten ausüben, welche mit dem Vereinszweck im Zusammenhang stehen oder der Verwaltung des Vereinsvermögens dienen. Insbesondere kann der Verein Darlehen, Garantien und andere Arten der Finanzierung und Sicherstellung für verbundene und nahestehende Gesellschaften im In- und Ausland gewähren.
Die TYPO3 Association ist parteipolitisch und konfessionell neutral.
Die TYPO3 Association hat insbesondere folgende Aufgaben:
Neumitglieder werden auf schriftliches Gesuch hin durch Entscheid des Vereinsvorstands per sofort vorläufig aufgenommen. Die definitive Aufnahme erfolgt durch die Generalversammlung.
Verweigert der Vereinsvorstand die vorläufige Aufnahme, so kann der Antragsteller den Entscheid innerhalb von 30 Tagen nach Zugang beim Vereinsvorstand zuhanden der Generalversammlung anfechten.
Der Vereinsvorstand und die Generalversammlung entscheiden über das Aufnahmegesuch nach freiem Ermessen. Sie sind nicht verpflichtet, die Gründe einer Ablehnung mitzuteilen.
Mitglieder sind berechtigt, das Vereinslogo zu führen, um ihre Mitgliedschaft und ihre Unterstützung für TYPO3 zu demonstrieren. Ausserhalb dieses begrenzten Zwecks ist eine Nutzung des Vereinslogos nicht gestattet.
Der TYPO3 Association können natürliche oder juristische Personen beitreten.
Mitglieder, welche sich um die TYPO3 Association oder deren Zielsetzung besonders verdient gemacht haben, können als Ehrenmitglieder der TYPO3 Association auf Lebzeiten gewählt werden. Ehrenmitglieder sind von der Beitragspflicht befreit und ansonsten den Mitgliedern gleichgestellt.
Der Austritt kann auf Ende eines Mitgliedsjahres mit einer Kündigungsfrist von zwei Monaten erfolgen. Der Austritt ist schriftlich an den Vereinsvorstand zu erklären. Die Verpflichtungen gegenüber dem Verein für das laufende Mitgliedsjahr sind zu erfüllen.
Die Mitgliedschaft endet im Weiteren durch Auflösung der juristischen Person bzw. Ableben des Mitglieds.
Mitglieder, welche Statuten, Reglemente, Beschlüsse verletzen oder sonst den Interessen der TYPO3 Association in schwerwiegender Weise zuwiderhandeln, oder wenn sie nach Ablauf von zwei Monaten nach der Absendung der zweiten schriftlichen Mahnung unter Androhung des Ausschlusses mit der Zahlung von Mitgliedsbeiträgen weiterhin im Rückstand sind, können vom Vereinsvorstand unter Angabe der Gründe ausgeschlossen werden.
Vor der Beschlussfassung muss der Vereinsvorstand dem Mitglied Gelegenheit zur Stellungnahme geben. Das ausgeschlossene Mitglied kann den Entscheid des Vereinsvorstands innert 30 Tagen seit Zustellung beim Vereinsvorstand zuhanden der Generalversammlung anfechten. Über den Ausschluss entscheidet diesfalls die Generalversammlung endgültig.
Die Generalversammlung bildet das oberste Organ des Vereins. Sie wird vom Vereinsvorstand einberufen und findet jeweils im ersten Halbjahr statt. Der Vereinsvorstand lädt die Mitglieder spätestens 30 Tage vor der Versammlung schriftlich (auch per eMail) und unter Angabe der Traktanden ein. Die Frist beginnt mit dem auf die Absendung des Einladungsschreibens folgenden Tag. Das Einladungsschreiben gilt dem Mitglied als zugestellt, wenn es an die letzte vom Mitglied der TYPO3 Association schriftlich bekannt gegebene Adresse oder eMail-Adresse gerichtet ist.
Der Versammlungsleiter hat zu Beginn der Generalversammlung die Ergänzung der Traktanden bekannt zu geben. Über Anträge auf Ergänzung der Traktanden, die in Generalversammlungen gestellt werden, beschliesst die Versammlung endgültig.
Der Vereinsvorstand kann jederzeit eine a.o. Generalversammlung einberufen. Ein Fünftel der Mitglieder können die Einberufung einer a.o. Generalversammlung schriftlich oder elektronisch unter Angabe des Zwecks und der Gründe verlangen. Diesfalls hat der Vereinsvorstand die a.o. Generalversammlung innert 3 Monaten nach Eingang des Begehrens durchzuführen.
Anträge zuhanden der Generalversammlung sind dem Präsidenten mindestens 14 Tage vor der Generalversammlung schriftlich und begründet einzureichen.
Die Aufgaben und Kompetenzen der Generalversammlung sind Folgende:
Ernennung von Ehrenmitgliedern; #. Beschwerde gegen geschäftsführende Organe, Beschlussfassung über die Berufung gegen einen Ausschliessungsbeschluss oder Ablehnung eines vorläufigen Aufnahmebeschlusses des Vereinsvorstands.
Jede statutengemäss einberufene Generalversammlung ist beschlussfähig. Sie beschliesst mit einfacher Mehrheit der anwesenden stimmberechtigten Mitglieder, sofern die Statuten nichts anderes bestimmen.
Die Teilnahme an der Generalversammlung kann auch ohne physische Präsenz durch elektronische Übertragung erfolgen ("Internet-Generalversammlung"). Der Vereinsvorstand legt mit der Einladung zur Generalversammlung fest, ob diese Art der Teilnahme angeboten wird. Ein Antrag eines Mitglieds auf elektronische Teilnahme hat spätestens 20 Tage vor der Versammlung beim Vereinsvorstand einzugehen. Der Vereinsvorstand hat am Versammlungsort technisch sicherzustellen, dass die Voten des Mitglieds mittels Wort und Bild simultan übertragen werden können. Die elektronische Teilnahme an der Versammlung gilt nur dann als gültig erfolgt, wenn das Mitglied eindeutig identifiziert werden kann. Elektronisch abgegebene Voten werden im Versammlungsprotokoll separat ausgewiesen.
Anstelle einer Präsenzversammlung kann auf Antrag des Vereinsvorstands auch eine ausschliesslich elektronische Versammlung durchgeführt werden ("Virtuelle Generalversammlung"). Es gelten sinngemäss dieselben Vorschriften wie bei der Internet-Generalversammlung.
Anstelle einer Präsenzversammlung sind auch Urabstimmungen (schriftliche Mehrheitsbeschlüsse zu Sachfragen) zulässig. Zur Ermittlung des jeweils notwendigen Quorums werden diesfalls nur die abgegebenen gültigen Stimmen ausgewertet. Elektronische Stimmabgabe ist zulässig, sofern die eindeutige Identifikation des oder der Stimmenden gewährleistet ist.
Bei Wahlen der Rechnungsrevisoren und in die Geschäftsprüfungskommission gilt im ersten Wahlgang das absolute, im zweiten Wahlgang das relative Mehr der anwesenden stimmberechtigten Mitglieder.
Die Generalversammlung entscheidet in allen Fällen in offener Abstimmung, sofern sie nicht beschliesst, diese geheim durchzuführen. Auf Antrag eines stimmberechtigten Mitgliedes kann dies mit Drittelmehrheit der anwesenden stimmberechtigten Mitglieder beschlossen werden. Im Falle einer Internet-Generalversammlung oder virtuellen Generalversammlung hat der Vereinsvorstand sicherzustellen, dass die geheime Stimmabgabe auf elektronischem Weg erfolgen kann.
Jedes Mitglied kann Beschlüsse, die das Gesetz oder die Statuten verletzen innert 30 Tagen, nachdem es von ihnen Kenntnis erhalten hat, gerichtlich anfechten.
Jedes Mitglied hat an der Generalversammlung eine Stimme. Zur Ausübung des Stimmrechts kann ein anderes Mitglied schriftlich bevollmächtigt werden. Die Bevollmächtigung ist für jede Generalversammlung gesondert zu erteilen; ein Mitglied darf jedoch nicht mehr als 3 fremde Stimmen vertreten. Bei Stimmengleichheit entscheidet bei Sachgeschäften die Stimme des Versammlungsleiters (Präsident, Vize-Präsident oder gewählter Tagesvorsitzender), bei Wahlen das Los.
Doppelfunktionen in Vereinsvorstand, Rechnungsrevisoren und Geschäftsprüfungskommission sind ausgeschlossen. Pro juristischer Person kann maximal nur je eine natürliche Person im Vereinsvorstand oder Geschäftsprüfungskommission Einsitz nehmen. Von der passiven Wahlfähigkeit ausgeschlossen sind Personen, die bezahlte Aufträge des Vereins ausführen.
Der Vereinsvorstand besteht aus dem Präsidenten, dem Vize-Präsidenten, dem Aktuar, dem Kassier und mindestens zwei weiteren Vorstandsmitgliedern (insgesamt mindestens 6 Mitglieder).
Die Amtsdauer des Vereinsvorstands beträgt drei Jahre und richtet sich nach dem Geschäfts- bzw. Kalenderjahr. Zu Vereinsvorstandsmitgliedern können nur Mitglieder des Vereins gewählt werden. Wiederwahl ist zulässig. Der Vorstand besteht aus maximal 9 Mitgliedern.
Nach Ablauf der Amtsdauer wird der Vereinsvorstand anlässlich der Generalversammlung neu gewählt. In jedem Jahr werden bis zu drei Vereinsvorstandsmitgliedern neu gewählt.
Jedes Vereinsmitglied kann sich selbst zur Wahl anbieten oder einen Vorstandskandidaten vorschlagen, welcher seine Kandidatur vorgängig bestätigen muss. Die Wahlvorschläge bzw. Vorstandskandidaten sind spätestens sechs Wochen vor der Generalversammlung dem Vorstand schriftlich bekanntzugeben. Der Vereinsvorstand kann auch vor der Generalversammlung per Online-Voting gewählt werden, wobei den Mitgliedern diesfalls eine angemessene Frist für die vorgängige Bekanntgabe der Vorstandskandidaten einzuräumen ist.
Die Wahl der Kandidaten wird durch die Rangfolge der erhaltenen Stimmen bestimmt. Ein Kandidat ist gewählt, wenn er mindestens 50 % der abgegebenen Stimmen erhält. Erreichen Kandidaten diese Mehrheit im ersten Wahlgang nicht, folgen weitere Wahlgänge, bis die erforderliche Mehrheit erreicht ist. Bei Stimmengleichheit überzähliger Kandidaten wird ein weiterer Wahlgang zwischen diesen durchgeführt; bei erneuter Stimmengleichheit entscheidet das Los.
Die Wahl und die Zuteilung der Funktion (Präsident, Vize-Präsident, Aktuar und Kassier) wird anlässlich der Hauptversammlung vor Beginn einer neuen Amtsperiode mit einfacher Mehrheit der anwesenden Vorstandsmitglieder bestimmt.
Der Kandidat für das Amt des Präsidenten muss mindestens ein Jahr dem Vereinsvorstand angehört haben, ansonsten seine erste Amtsperiode auf ein Jahr limitiert ist.
Mit der Beendigung der Mitgliedschaft im Verein endet auch das Amt eines Vereinsvorstandsmitglieds.
Bei Ersatzwahlen während der Amtsdauer vollendet das neu gewählte Vereinsvorstandsmitglied die Amtsdauer des Vorgängers. Anstelle von Ersatzwahlen kann der Vereinsvorstand den nächst platzierten Kandidaten aus der letzten Wahl fragen, ob er nachrücken möchte. Wenn mehr als drei Vereinsvorstandsmitglieder in einer Amtsperiode zurücktreten, werden Neuwahlen für alle zurückgetretenen Positionen in einer außerordentlichen Generalversammlung abgehalten.
Der Vereinsvorstand kann mit einer einfachen Mehrheit des vollständigen Vorstands Neuwahlen für den gesamten Vorstand ausrufen.
Der Vereinsvorstand ist im Rahmen von Gesetz und Statuten für die Besorgung der Vereinsangelegenheiten zuständig. Dem Vereinsvorstand obliegt insbesondere
Der Vereinsvorstand erlässt eine Geschäftsordnung und regelt darin seine Aufgaben sowie die Aufgabenteilung. Der Vereinsvorstand verfasst jährlich einen Jahresbericht über seine Tätigkeit.
Sitzungen werden durch den Präsidenten des Vereinsvorstands einberufen, so oft es die Geschäfte erfordern, mindestens jedoch einmal jährlich vor Ablauf der Amtsdauer (Hauptversammlung). Jedes Vereinsvorstandsmitglied kann die Einberufung einer Sitzung verlangen. Diesfalls ist die Sitzung innert drei Wochen durchzuführen. Der Vereinsvorstand führt ein Beschluss-Protokoll. Auf Anordnung des Präsidenten oder auf Verlangen eines Vereinsvorstandsmitgliedes werden gefallene Voten zusammengefasst protokolliert.
Der Vereinsvorstand ist beschlussfähig, wenn mindestens vier Vereinsvorstandsmitglieder anwesend sind. Der Vorsitzende kann das Zirkularverfahren durchführen. Ein Zirkularbeschluss ist nur bei Einstimmigkeit aller Vereinsvorstandsmitglieder gültig.
Der Vereinsvorstand strebt bei seinen Entscheidungen den Konsens an. Der Vereinsvorstand entscheidet durch Stimmenmehrheit der anwesenden Vereinsvorstandsmitglieder. Bei Stimmengleichheit hat der Präsident den Stichentscheid. Auf Verlangen eines Mitgliedes des Vereinsvorstands muss eine Abstimmung geheim durchgeführt werden. Jedes Vereinsvorstandsmitglied ist berechtigt, eine Minderheitsmeinung zu Protokoll zu geben.
Die Vereinsvorstandsmitglieder führen die rechtsverbindliche Kollektivunterschrift zu Zweien. Es zeichnet jeweils der Präsident oder im Verhinderungsfall der Vize-Präsident, zusammen mit einem weiteren Mitglied des Vereinsvorstands.
Der Präsident leitet üblicherweise die Versammlung des Vereins sowie des Vereinsvorstands. Er überwacht die TYPO3 Association Tätigkeit im Rahmen der Beschlüsse der Generalversammlung und des Vereinsvorstands.
Der Kassier besorgt das gesamte Rechnungswesen und verwaltet das TYPO3 Association Vermögen. Im Rahmen seiner Tätigkeit führt er Kollektivunterschrift mit dem Präsidenten, dem Vize-Präsidenten oder einem anderen Mitglied des Vereinsvorstands.
Die Generalversammlung wählt jeweils auf eine Amtsdauer von einem Jahr eine anerkannte Treuhandstelle als Revisionsstelle, welche nach den Vorschriften des Revisionsaufsichtsgesetzes vom 16.12.2005 zugelassen ist. Der Verein beauftragt die Revisionsstelle auch ohne gesetzliche Pflicht mit der Durchführung einer eingeschränkten Revision nach den Vorschriften von Art. 729-729c OR. Durch Beschluss der Generalversammlung kann auf die Durchführung einer eingeschränkten Revision des folgenden Vereinsjahres verzichtet werden.
Die Revisionsstelle prüft die Buchführung und erstattet der Generalversammlung schriftlich Bericht und stellt der Generalversammlung Antrag auf Erteilung oder Verweigerung der Décharge gegenüber dem Kassier und dem Vorstand.
Die Geschäftsprüfungskommission besteht aus 4 Mitgliedern.
Die Amtsdauer der Geschäftsprüfungskommission beträgt zwei Jahre. Die Wahl erfolgt durch die Generalversammlung. Wiederwahl ist zulässig. Zu Mitgliedern der Geschäftsprüfungskommission können nur Mitglieder des Vereins gewählt werden. Mit der Beendigung der Mitgliedschaft im Verein endet auch das Amt eines Mitglieds der Geschäftsprüfungskommission. Bei Ersatzwahlen während der Amtsdauer vollendet das neu gewählte Mitglied der Geschäftsprüfungskommission die Amtsdauer des Vorgängers. Bei gerader Jahreszahl wird jeweils die erste Hälfte der Mitglieder der Geschäftsprüfungskommission, bei ungerader Jahreszahl jeweils die zweite Hälfte gewählt.
Die Geschäftsprüfungskommission kann alle Projektkredite prüfen auf Ausgabenübereinstimmung mit dem Kreditantrag, erreichen der aufgeführten Ziele und kosteneffiziente Projekterfüllung. Sie erstattet vierteljährlich dem Vereinsvorstand sowie jährlich der Generalversammlung schriftlichen Bericht.
Die Geschäftsprüfungskommission erlässt eine Geschäftsordnung und regelt darin ihre Aufgaben sowie die Aufgabenteilung.
Der Vereinsvorstand kann für besondere Aufgaben beratende Ausschüsse oder Einzelpersonen ohne Entscheidungsbefugnisse einsetzen.
Als Geschäftsjahr gilt das Kalenderjahr.
Abweichend davon ist das Mitgliedsjahr. Dieses gilt individuell für jedes einzelne Mitglied. Es beginnt mit dem Entscheid des Vereinsvorstands über die Annahme des schriftlichen Mitgliedschaftsgesuchs.
Die TYPO3 Association beschafft ihre finanziellen Mittel aus:
Die Aufnahmegebühren sowie die Jahresbeiträge werden von der Generalversammlung festgelegt. Erhöhungen von Gebühren und Beiträgen gelten ab sofort für alle Rechnungen die ab dem Zeitpunkt der Erhöhung gestellt werden. Der Vereinsvorstand kann in ausserordentlichen Fällen Beiträge ganz oder teilweise erlassen oder stunden.
Mitglieder und Dritte können jederzeit zur freien Verfügung des Vereins finanzielle Mittel zur Erreichung des Vereinszwecks einschiessen (insbesondere über Fundraising- bzw. Spendenaktionen).
Die Vereinsausgaben werden mit dem Budget festgelegt. Das Budget weist die zweckgebundenen Beträge pro Rechtsgeschäft aus. Das Budget wird durch den Vereinsvorstand erstellt und beschlossen. Vorgängig findet eine Befragung (auch auf elektronischem Wege möglich) der Mitglieder zu den Projektanträgen statt. Budgetanträge werden formal vom Kassier geprüft.
Der Vereinsvorstand kann in Ausnahmefällen in eigener Kompetenz Budgetüberschreitungen von maximal 5% der Gesamtbudgetsumme beschliessen.
Den Mitgliedern des Vereinsvorstands und der Geschäftsprüfungskommission kann eine Entschädigung zugesprochen werden. Diese ist im Budget festzulegen.
Für Verbindlichkeiten der TYPO3 Association haftet ausschliesslich das Vereinsvermögen. Das einzelne Mitglied ist nur zur Bezahlung der Aufnahmegebühr sowie des Mitgliederbeitrages verpflichtet.
Mitglieder, die austreten oder ausgeschlossen werden, verlieren jeden Anspruch auf das Vereinsvermögen.
Die Statuten sind jedem Mitglied abzugeben. Mit dem Eintritt in den Verein anerkennt ein Mitglied diese Statuten und verpflichtet sich, den Beschlüssen und Weisungen der zuständigen Vereinsorgane nachzukommen.
Abänderung der geltenden Statuten können durch die Generalversammlung oder einer a.o. Generalversammlung beschlossen werden. Solchen Beschlüssen müssen zwei Drittel der anwesenden Mitglieder zustimmen.
Zur Auflösung des Vereins müssen zwei Drittel der stimmberechtigten Mitglieder der TYPO3 Association an einer zu diesem Zweck einberufenen ausserordentlichen Generalversammlung anwesend sein. Die Auflösung kommt zustande, wenn drei Viertel der anwesenden Stimmberechtigten zustimmen.
Sollten nicht zwei Drittel der stimmberechtigten Mitglieder der TYPO3 Association anwesend sein, so ist nach 30 Tagen eine zweite ausserordentliche Generalversammlung einzuberufen. Die Auflösung kommt zustande, wenn vier Fünftel der anwesenden Stimmberechtigten zustimmen.
Falls die ausserordentliche Generalversammlung nichts anderes beschliesst, sind der Vorsitzende und der Kassierer gemeinsam vertretungsberechtigte Liquidatoren. Das nach Beendigung der Liquidation vorhandene Vermögen fällt zu Gunsten einer gemeinnützigen Organisation, die von der ausserordentlichen Generalversammlung zu bestimmen ist. Die vorstehenden Bestimmungen gelten entsprechend, wenn der Verein aus einem anderen Grund aufgelöst wird oder seine Rechtsfähigkeit verliert.
Fusionen gelten nicht als Auflösung des Vereins.
Der Gerichtsstand bezüglich sämtlicher Streitigkeiten betreffend die Mitgliedschaft ist am Sitz des Vereins.
Die Statuten wurden von der ordentlichen Generalversammlung vom 11.4.2018 genehmigt und treten per Datum der ordentlichen Generalversammlung 2019 in Kraft. Sie ersetzen die Statuten vom 20.11.2016.
This policy was voted into effect through a Board vote in October 2023. The Possible Conflict of Interest Mapping matrix was updated 3 April 2025. Migrated to the current repository 19 November 2025.
TYPO3's Conflict of Interest Policy aims to ensure that the collective interests of the TYPO3 community prevail over personal interests by exercising our responsibilities and making our decisions impartially, objectively and independently.
The occurrence of a personal interest whose interference with the position held is such as to influence or appear to influence the loyal exercise of the position.
Only conflicts of interest within the perimeter of the sensitive processes, critical positions and at-risk operations are covered by this conflict of interest management policy.
Sensitive processes are processes whose conflict of interest would be harmful to the interests of the TYPO3 community. These processes are: Purchasing, sales, investments, accounting, and human resources management. This list is not exhaustive and will be updated regularly.
Critical positions include: TYPO3 Association Board and BCC members, TYPO3 Company Supervisory Board members, TYPO3 Company CEO, CTO and CFO, TYPO3 CMS product owner, project leader and co-leader. This list is not exhaustive and will be updated regularly.
Some operations inherent in the life of the TYPO3 project (prospecting, finding new markets, external growth, lobbying, lending or borrowing money, etc.) are more exposed to the corruption risk. Preventing conflicts of interest that may arise during these operations is likely to reduce the corruption risk.
There are several types of conflict of interest:
Any individual falling within the scope of the sensitive processes, critical positions and at-risk operations defined above must :
The priority matrix is used to weight the severity of a conflict of interest by its probability, and to determine whether action needs to be taken to reduce this priority.
Only conflicts of interest with a value greater than or equal to 4 should be dealt with using one of the strategies described below.
| Conflict of interest Type | Low (1) | High (3) |
|---|---|---|
| Perceived (1) | 2 | 4 |
| Potential (2) | 3 | 5 |
| Real (3) | 4 | 6 |
| Type + Severity | Board Member | BCC Member | GmbH Employee (CEO, CTO, CFO, critical roles) | TYPO3 Agency / TYPO3 Freelancer | Same Agency as Board Member | Direct Under Board Member | Same Agency as BCC Member | Direct Under BCC Member | Team / Committee Lead |
|---|---|---|---|---|---|---|---|---|---|
| Board Member | na | forbidden | forbidden | 5 | forbidden | forbidden | 6 | forbidden | 2 |
| BCC Member | forbidden | na | forbidden | 3 | 6 | forbidden | forbidden | forbidden | forbidden |
| GmbH Employee | forbidden | forbidden | na | forbidden | 6 | forbidden | forbidden | forbidden | 3 |
| TYPO3 Agency / TYPO3 Freelancer | 5 | 3 | forbidden | na | na | na | na | na | 4 |
| Same Agency as Board Member | forbidden | 6 | 6 | na | na | na | na | na | 2 |
| Direct Under Board Member | forbidden | forbidden | forbidden | na | na | na | na | na | 2 |
| Same Agency as BCC Member | 6 | forbidden | forbidden | na | na | na | na | na | 2 |
| Direct Under BCC Member | forbidden | forbidden | forbidden | na | na | na | na | na | 2 |
| Team / Committee Lead | 2 | forbidden | 3 | 4 | 2 | 2 | 2 | 2 | 2 |
Credit: This manifesto is based on the Drupal Association’s `original Open Web Manifesto <https://www.drupal.org/association/open-web-manifesto>`__.
Note
As a member of the Open Website Alliance, the TYPO3 Association adheres to the Open Web Manifesto.
The following is a declaration of this Alliance’s commitment to the open web and our belief in its power as a digital public good.
The open web is more than a technology—it is a cause.
It is built on freedom: You don’t need permission to learn, build, or advance open web technology. Anyone, anywhere can contribute to making it better.
It is defined by decentralization: No single person or entity controls the open web.
It thrives on inclusion: Everyone in the world, regardless of background, identity, ability, wealth, or status, has a home on the open web as a user, creator, architect, and innovator.
It requires participation: The open web is a shared resource and a shared responsibility, sustained by deliberate choice and collaborative effort.
It exists for empowerment: The open web is fueled by humanity’s collective quest for information, connection, and progress—and strengthened by every individual’s right to choice, privacy, and security.
To live up to that definition, an open web must not be built on proprietary technology.
The open web must be more than an ideal or a set of principles: to achieve its full potential as a global, digital public good, the open web must prove that it is a better web.
That means embodying the limitless innovation that can only come from collaboration; integrating with the best technology available; and earning people’s trust.
Our integrity ensures independence and inclusion for all. Every level of our community is both a beneficiary of the open web and a participant in building it:
Together, we’re shaping the foundation for how the digital world operates, and how future generations will live, work, connect, and express themselves.
As long as our software exists, that foundation will be an open web that is open source, open access, and always open to improvement.
Responsible for this document: Board of the TYPO3 Association
See also
Please read Decision-Making Processes, Contribution and Participation to understand the terms Committees and Official Team.
A temporary group working on a specific topic. No rights or obligations.
A community-driven team with specific responsibilities within an area.
Founding an Official Team: A request must be submitted to the TYPO3 Association Board.
Disbanding an Official Team: The Board or the General Assembly of the Association can disband a team. A team can be disbanded by the Association Board if it violates the expectations for more than 6 months.
An Association-driven team working towards the goals of the Association.
Committees are initiated by the TYPO3 Association Board and have to report to the General Assembly.
Disbanding a Committee: The Board or the General Assembly of the Association can disband a committee.
Committees enjoy the same benefits as official teams.
All members of a team have to respect the code of conduct. The Team and Committee Leaders have additionally to respect the policy for teams.
Version 2.0.1 • Valid for reimbursements submitted from 1st July 2023 (by TYPO3 Association Board decision 17th May 2023). Modified 10 January 2023, adding Swiss VAT number to 4.e. Migrated to the current repository 21 November 2025.
If you are new to the reimbursement process, you can read this introduction to learn the basics of how and when to reimburse expenses from the TYPO3 Association. If you have further questions, please feel free to contact the `budget owner <https://typo3.org/project/association/funding-finances/budget#c13503>`__ or read the detailed :ref:`Reimbursement Regulations <reimbursement-regulations>`.
While it is your job to correctly document your expenses and submit them in time, it is each budget owner <https://typo3.org/project/association/funding-finances/budget#c13503>`__’s responsibility to answer your questions and give you the information they think you need.
The TYPO3 Association is a not-for-profit organization funded by our members. We reimburse expenses and work time as a way to enable our community to do great things for TYPO3. If your expenses can be covered through other means, such as by your employer, we ask that you pursue such possibilities.
Each year, the TYPO3 Association’s money is divided into budgets for teams and projects, based on input from the members. Each budget has a single Budget Owner. This is the person to contact if you have questions. It is also the person who accepts (or rejects) your reimbursement requests. List of budgets and their owners
You should start the reimbursement process early, before you have had any expenses or done any work.
Ask the budget owner for pre-approval of your expenses using the Pre-Approval Form. You do not have to do this if the budget owner has issued a general pre-approval for your type of expense, but unless you’re certain of that, submitting the form is the way to go.
A pre-approval means the budget owner sees nothing wrong with reimbursing your expenses based on the information you have given. Your reimbursement request will be accepted when the time comes, as long as it does not violate the Reimbursement Regulations, e.g. by being contrary to the pre-approval, insufficiently documented, or submitted too late.
Book travel and lodging, do the work, and incur the expenses pre-approved by the budget owner. Make sure to keep hold of, photograph, or scan all receipts, invoices, time logs, and other paperwork that documents your expenses or work time. For more information, read section 5, Documentation.
If you are unable to cover travel, lodging, and food expenses, you can ask the budget owner for advance payment. You can do this by submitting a reimbursement request documenting the expenses you expect to have. See section 2.n for detailed requirements.
Submit a reimbursement request using the Reimbursement Tool within 20 days. Check out the step-by-step guide. This will send a request asking the budget owner to review your request.
The reimbursement is usually paid out by PayPal or bank transfer within a couple of weeks. A bit later you will receive an automatic email asking you to confirm that you have received the reimbursement. If the money has not arrived by this point, you should contact the budget owner.
Given the budget owner’s approval, the TYPO3 Association reimburses travel and lodging expenses, for real and practical participation in a TYPO3-related activity. The expenses should cover travel with the best price/time ratio, on the most environmentally friendly means of transportation, in the lowest service class, from a person’s home to their destination, and back.
Flying distances shorter than 300 km one way is a big “no”. Using your private car is allowed at EUR 0.30/km, maximum EUR 220. More private car rules in section 2.g.
Hotel rooms are reimbursed at maximum EUR 130/night. To save money, some teams do group bookings and share rooms. Don’t book hotel rooms in Düsseldorf, Germany. TYPO3 has special rates there, so contact your budget owner instead. Further details in section 2.k.
Food is only reimbursed if it’s an inclusive hotel breakfast or a reasonably-priced group meal at a sprint. See section 2.l.
If you reimburse work time, you have to keep a log of hours worked. It has to show the total number of hours worked per day, as well as either individual time entries or summarized time per task per day. You can work a maximum of 6 hours/day for a maximum of EUR 55/hour. See section 3 for details and this time log example.
If you’re a business or freelancer, you can invoice the TYPO3 Association and submit the invoice as a part of the reimbursement request. Remember to write the budget number on the invoice. Most invoicing applications will generate invoices that comply with the minimum requirements in section 4.d. Remember that you’re invoicing a Swiss association, so you should only apply VAT if you are invoicing from Switzerland.
Although you’re invoicing, you still have to include all of the paperwork that documents your expenses or work time. The invoice must be due at least 20 days into the future when you submit it. See section 4 for detailed requirements and this example invoice.
Events such as natural causes (fire, storms, floods), governmental or societal actions (war, invasion, civil unrest, labor strikes), infrastructure failures (transportation, energy), etc.
The keywords must, must not, required, shall, shall not, should, should not, recommended, may, and optional in these regulations are to be interpreted as described in RFC 2119.
Expense types that can be reimbursed. These are: travel, lodging, event tickets, food at sprint or meeting, work time, and invoiced services.
The TYPO3 Association’s reimbursement management tool at reimbursement.typo3.com.
Documentation that doesn’t directly document an expense, but explains a decision or need. For example a screenshot showing a travel cost different to the chosen one or an adverse weather alert requiring a detour. (Requirements for secondary documentation can be found in section 5.e.)
Reimbursement requests shall only be approved if they comply with these Reimbursement Regulations.
Reimbursements must be relevant to the reimbursing budget. In case of uncertainty, the final decision is up to the Business Control Committee.
All reimbursement requests must be submitted through the Reimbursement Tool unless it causes excessive inconvenience to the reimbursed.
Reimbursements will be made in Euro through bank account or PayPal transfers.
The TYPO3 Association shall not be liable for any fees or taxes incurred by the reimbursed when paying out a reimbursement.
All reimbursements should be pre-approved by the budget owner. Pre-approval indicates that the budget owner will approve the reimbursement request as long as it complies with the Reimbursement Regulations. Requests for pre-approval must state:
The budget owner may choose to issue a general pre-approval of reimbursements for a specific purpose. General pre-approvals must state:
The budget owner can reject reimbursement requests submitted without pre-approval at their own discretion.
Expenses can be split between multiple budgets using multiple reimbursements. Budget owners must be informed and agree to the split before such a reimbursement is made. The percentage reimbursed and the other budgets involved in the split must be included with the reimbursement documentation.
All budget-related decisions must be documented by the budget owner by uploading a PDF file in the Documents section of the budget's Reimbursement Tool Page. Budget-related decisions include reimbursement pre-approvals.
Expenses for travel, lodging, and food must concern participation in a TYPO3-related activity in a real and practical sense, unless participation was prohibited by unforeseen circumstances, such as illness, urgent family matters, job-related emergencies, or Force Majeure.
The TYPO3 Association will reimburse travel expenses with the best price/time ratio, on the most environmentally friendly means of transportation, from a person’s home to their destination, and back, including:
Expenses for public transportation should be for the lowest service class.
Expenses for car rental should be in the smallest vehicle class.
Reimbursement of a higher/larger service or vehicle class is possible in either of these cases, provided the reimbursement includes Secondary Documentation of the lowest/smallest class price:
If the total traveling time is more than 8 hours, a more expensive means of transportation is acceptable, if it reduces travel time or provides a more convenient itinerary.
When using a private car, up to EUR 220 will be reimbursed at EUR 0.30/km using the shortest route found on Google Maps. If added as Secondary Documentation in the reimbursement request, higher expenses or detours can be reimbursed in these cases:
Plane tickets for distances below 300 km one way will not be reimbursed.
Extra costs for CO2 offsetting will not be reimbursed. The TYPO3 Association offsets emissions through our climate protection partner.
Only the real net cost will be reimbursed. If you use a discount card, such as the German BahnCard, only the cost after discount will be reimbursed.
Hotel accommodation will be reimbursed up to an average of EUR 130/night. Higher expenses must be pre-approved. Hotel accommodation in Düsseldorf, Germany, should be booked through the TYPO3 GmbH. Alternatively, any accommodation below TYPO3 GmbH’s negotiated rate or the maximum rate given above (whichever is lowest) can be reimbursed.
Food costs will not be reimbursed, except for
Reimbursement requests for travel, lodging, or food, must be submitted no later than 20 days after the last expense date or last day of travel, whichever is the latest.
If a person is unable to cover travel expenses out of their own pocket, travel expenses can be covered in advance following these rules:
Work time will only be reimbursed if it is explicitly mentioned in an approved budget application, and only to the maximum amount mentioned therein.
The maximum paid work time must not exceed 6 hours/day.
The maximum rate must not exceed EUR 55/hour.
Invoices can be addressed to the TYPO3 Association by businesses and freelancers.
Employees are free to choose whether they choose to reimburse expenses as a private person, without an invoice, or through their employer, using an invoice.
Invoices should be submitted through the Reimbursement Tool.
At the time of submission, invoices must:
If the TYPO3 Association is the invoice recipient and the invoice issuer is not Swiss, no VAT should be applied to the invoice. The TYPO3 Association’s Swiss VAT number is CHE‑112.256.297 MWST.
All reimbursements must be fully documented using digital originals or complete and legible scans or photos of the documents.
The only acceptable documentation types are:
The documentation must contain at least the following information:
Time logs must additionally contain at least the following information:
Individual time entries for tasks or summarized time for each task during each day. Total time worked for each day when work was performed.
These documentation requirements do not apply to Secondary Documentation. It should instead contain as much of the relevant visible information as possible, e.g. a screenshot of the entire visible part of the website in the browser window.
TYPO3 is always written in uppercase, with no spaces. This rule covers all products under the TYPO3 project. URLs are the only exception to this rule.
A complete product name should have "TYPO3" as the first word, for example "TYPO3 CMS".
The number "3" is a part of the product name. It is not a version number.
Read about the history of the TYPO3 name.
This page was updated on 19th May 2025, on behalf of the TYPO3 Association Trademark Team, original publication October 2017. Migrated to the current repository 21 November 2025.
The word “TYPO3” is one of the trademarks owned by the TYPO3 Association.
The TYPO3 name is a registered trademark owned by the TYPO3 Association. These guidelines are designed to protect the integrity of the TYPO3 brand while allowing the community to promote and support TYPO3 in appropriate ways.
Protected: The wordmark "TYPO3" is a registered trademark.
Not Registered: The standalone TYPO3 logo (shield icon) is not a registered trademark but is governed by our brand guidelines.
You may use the TYPO3 wordmark descriptively to refer to the TYPO3 CMS in a factual manner. Examples include:
Conditions:
Members of the TYPO3 Association are permitted to use membership badges corresponding to their membership level, provided that:
Badges are available for download at TYPO3 Association Membership Badges.
Only Gold and Platinum members of the TYPO3 Association are permitted to use the TYPO3 wordmark in paid advertising, including but not limited to:
Non-members and members below the Gold level are not permitted to use the TYPO3 wordmark in any form of paid advertising.
The TYPO3 wordmark may not be used as part of:
This restriction applies to all individuals and organizations, regardless of membership status.
While the TYPO3 logo (shield icon) is not a registered trademark, its use is governed by our brand guidelines. Unauthorized use of the logo in a manner that implies endorsement or partnership is prohibited.
The TYPO3 Association reserves the right to take appropriate action against unauthorized or improper use of the TYPO3 trademark, including legal action if necessary.
For questions or to request permission for specific uses not covered in these guidelines, please contact us at trademark@typo3.org.
Note: This policy is subject to change. Please refer to this document for the most current version.
If you would like to apply for permission to use a TYPO3 trademark based on the guidelines above, please fill in the register trademark usage form, including full contact details and the details of your requested use.
Your application's approval will primarily be considered based on these criteria:
Are you planning a TYPO3-related event? You have the full support of the TYPO3 Association. Please note the following conditions:
We also ask that you consider donating a percentage of the event's total revenue to the TYPO3 Association. This donation will support the TYPO3 project.
We would like to thank the people at Ghost.org, whose trademark page inspired us. Please refer to Wikipedia's page on Trademarks for additional information on trademark usage.
PUBLIC VERSION
Written by: Boris Hinzer and Mathias Bolt Lesniak • Date: October 2023
Having a strategy for TYPO3 is essential for providing direction, creating a competitive advantage, optimizing resource allocation, fostering adaptability, promoting alignment, facilitating decision-making, and engaging stakeholders. The strategy acts as a roadmap for the success of the TYPO3 Association and helps us navigate the complexities of the business landscape.
It helps us build trust, engage employees and community members, attract investors and partners, and gain support from customers and the community.
The strategy will continue to be revisited as an iterative process to ensure it continues to meet our needs.
Having a strategy for the TYPO3 Association is crucial for several reasons. Here are some key benefits of having a well-defined strategy:
The last few years in the TYPO3 Association were marked by the professionalization of the services around TYPO3, but now it is time to focus on our main product.
The TYPO3 GmbH often acted as a pure service agency for infrastructural tasks or as a “rescue mission” for subprojects and events in need, that could not be carried out by the TYPO3 Association Board, the BCC, or community teams on a voluntary basis.
While the surrounding market was clearly developing in the direction of SaaS, subscription models, no-code/low-code offerings, and cloud-based solutions, neither the TYPO3 Association nor TYPO3 GmbH acted on these market opportunities and threats in a targeted manner, to counter them, or even to develop their business models around a strong product, TYPO3 CMS.
The desire for a strong, leading, and guiding TYPO3 Association came both from the bodies of the Association itself and from the extended TYPO3 community. This resulted in the strategy process for the TYPO3 Association, GmbH, and Project.
The TYPO3 Association is an integral part of the TYPO3 Project. Everything thought and done by the Association happens within the context of the TYPO3 Project and never outside of it. As a result, the TYPO3 Association’s vision, mission, and purpose is always the same as — or a subset of — the project’s vision, mission, and purpose.
While the TYPO3 Association’s vision and purpose are the same as for the Project, the mission is formulated thus:
“The TYPO3 Association enables community, collaboration, ideas, and exchange to foster the TYPO3 project and secure the freedom of open source.”
This image illustrates the relationship between the TYPO3 Project, TYPO3 Product, TYPO3 Association and TYPO3 GmbH (aka. TYPO3 Company), and their visions, missions, and purposes:
The TYPO3 Company is within the TYPO3 Association. The TYPO3 Association and TYPO3 Product are part of the TYPO3 Project
Empower :ref:`* <vmp-faq-vision-question1>` to unlock their potential, creating opportunities through content.
We believe that every person can bring something unique to the table. Content is fundamental to empowering people today to share knowledge, unlock possibilities, and achieve their potential regardless of who they are, what they believe, or where they come from. Our people, software, and services will empower content for everyone.
Enable :ref:`freedom <vmp-faq-mission-question1>`, :ref:`interconnection <vmp-faq-mission-question2>`, and collaboration through sustainable, world-class, open content management software.
Our mission is to make a better world for everyone by building and maintaining sustainable, affordable, accessible, easy-to-use, open-source software, offering professional services, and creating an open and welcoming community.
:ref:`Equalize opportunities <vmp-faq-purpose-question1>` through Open Source.
Our purpose is to equalize opportunities by making our world-class open source software available to anyone, free to download and use. We offer our supporting services at :ref:`prices adjusted to local circumstances <vmp-faq-purpose-question2>. Our products strengthen collaboration, empower independent businesses, educational and government institutions, and civil society worldwide.
Since the beginning, TYPO3 has been more than just a piece of software. TYPO3 is a community. Our values are there to guide our work and make sure the community is a great place for everyone.
These core values also apply to the TYPO3 Association.
Trust and respect each person and their work. Remember to give the trust and respect you expect to receive from others. To be trusted and respected, you need to be reliable. The concept of trust, respect, and reliability are not valid only for the people involved in the community, but are extended to the products as well. By being a reliable member and by doing reliable and respected work, the outcome should automatically translate into great products that everyone can trust.
The TYPO3 Community defines itself as inclusive. Not exclusive, but open and without barriers of any type. The openness that characterizes the community is directed at people and their backgrounds, opinions within the community and outside, the outside world, other teams and groups, and the market and its changes. Openness also relates to communication. Remember that open communication fosters the community's growth and health in an environment where everyone knows what's happening and what will happen.
An open source environment is characterized by collaboration. The TYPO3 Project sees collaboration as the sharing of knowledge, work, and support within teams and between teams, among people, and to the outside world. Sharing is improving, and collaboration enhances the efficient use of resources, knowledge, and ideas. Whenever possible, work with others and support them. Work transparently.
The Association is a part of the TYPO3 Project, and we have defined additional values that we think are mandatory in the whole TYPO3 Community.
Of those values, we think the following are lived by today:
The following values need to be developed further:
These are some action items and ideas for how to develop these values. How these will be carried out is yet to be determined.
We are open to additional suggestions from the TYPO3 Community.
The following goals and objectives for the TYPO3 Association are a result of our strategy process. They are continuously revised and adapted by participants from the TYPO3 Association Board, strategy program manager Ric van Westhreenen, and external consultant Patricia Moock from 4L Impact Strategies.
The following objectives and tasks have come out of the strategy process and are based on an initial SWOT analysis. They refer explicitly to the TYPO3 Association.
Additional goals and tasks were examined with regard to their possible and meaningful implementation, and, if necessary, moved to the of TYPO3 GmbH and aligned with their strategy.
In order to keep up with the changing market and the resulting changes in requirements, goals, and tasks, we agreed to review these goals at least once a year, but preferably on an ongoing basis, and adapt them in an agile manner.
Consequences for non-compliance and insufficient delivery will be defined by the board.
Fundraising will enable the TYPO3 Association to innovate and expand the user base in the face of changing market conditions and developing demands on the TYPO3 product.
The funding for TYPO3 is divided into three goals (with sub-goals):
Note
The monetary values have been removed from fundraising goals in the public version of this strategy.
In order to guarantee our goal of long-term independence in the spirit of open source, the TYPO3 Association does not seek to generate a budget through venture capital.
Responsible: The board member responsible for fundraising.
Action items for all board members: Each board member should prepare a plan to increase funding (with the beginning of their board period). The overall plan and targeting of certain members should be discussed in dedicated board meetings.
Controlling: The follow-through of the plan and achievements is discussed in board meetings, at least once per quarter. A board member will be assigned the task of controlling.
The implementation and improvement of governance best practices is another important goal of the strategy for the TYPO3 Association.
A strong community has developed around the TYPO3 software product. It has formed through collaboration and shared experiences, often at events. This TYPO3 community, characterized by friendship, has managed to pursue common interests even among competing market participants (agencies, freelancers, universities, corporates and governmental institutions). They have continuously developed the product and associated services together and established them on the market.
In order to successfully strengthen the market for TYPO3 and related services in the future, we see that a reliance only on friendship is not sufficient to create a foundation for further professionalization.
Unpopular decisions are sometimes necessary, but they must be made, communicated, and implemented by the TYPO3 Association in a professional manner. This requires an improvement in governance.
The following goals have been defined to improve governance:
As a special objective, we see the need for a standardized process for whistleblowing in order to be able to take action at an early stage in the event of deviations, irregularities, breaches of the law, compliance violations, or discrimination.
Responsible: Each board member is responsible to be compliant and to follow the governance mechanisms and processes. The board member responsible for Ethics, Compliance, and Governance is responsible for the concept of the strategic goals and can assign execution to the GmbH, BCC, teams, external support, etc. The person is also responsible for exchange of information with other stakeholders. The person will present the roadmap for the prioritized items in a board meeting.
Action items for all board members: Each board member should read and understand the code of conduct, risk management, and conflict of interest documents. Every board member is responsible for fine-tuning these documents. The owner of the documents is the board member responsible for Ethics, Compliance and Governance
Controlling: The progress of the plan and related achievements are reported in a board meeting, at least once per quarter. Responsible for controlling is board member responsible for Ethics, Compliance and Governance.
TYPO3 has been a registered trademark for many years, but we are seeing an increasing number of attempts at exploiting it (see: General Assembly 2023). The TYPO3 Association is continuing to enforce its trademark rights.
Some of the TYPO3 community is using the brand as a springboard for the marketing of their own services — often without regard to their membership status in the TYPO3 Association.
Competitors offering other systems and services misuse the TYPO3 brand in negative brand communication (e.g. “TYPO3 killer”) and misrepresented statements (e.g. “TYPO3 has a bad UI”).
The TYPO3 Association therefore considers the following goals for the TYPO3 brand to be indispensable:
As an example of a possible measure to secure and strengthen the TYPO3 brand, a compulsory training or webinar for TYPO3 Association members is being considered.
Responsible: The board member responsible for Trademark is responsible for the concept of the strategic goals and can assign execution to the GmbH, BCC, teams, external support, etc. The person is also responsible for the exchange of information and communication to other stakeholders and connecting parts. The person will present the roadmap for the prioritized items in a board meeting.
Action items for all board members: Each Board member should read and understand the trademark documents. Every Board member is responsible for the fine-tuning of those documents. The owner of the documents is the board member responsible for Trademark
Controlling: The follow through of the plan and achievements is reported in a board meeting, at least once per quarter. Responsible for controlling is board member responsible for Trademark.
Historically, the further development of TYPO3 was often driven by a developer's vision and, as Kasper Skårhøj has said it: “[to] scratch your own itch”. As a result, some past development tasks were carried out multiple times and were not prioritized in a way that was comprehensible to end users. Developer happiness seemed to be the primary goal.
TYPO3 has a great opportunity to become more welcoming and beginner-friendly.
Therefore, the TYPO3 Association board sees the need to open up a transparent innovation process.
One of the main goals for this innovation process is to develop a basic understanding and knowledge of how ideation, innovation, and product development should work. It is a must for Association bodies and leaders of committees and teams (especially those involved in product development for TYPO3 CMS), but we should also educate a wider audience, such as members of the TYPO3 Association and our community at large.
The members are an integral part of ongoing product and service development, and the sub goals are not nice-to-haves, but rather must-haves. Completing membership surveys could become a mandatory requirement to retain certain partnership and membership levels. The exact design, possible requirements, and non-compliance consequences will have to be defined.
To carry out the whole educational part of the ideation and innovation training, we see the role of an Innovation Manager arise in the TYPO3 GmbH.
As mentioned above, the innovation and development process of TYPO3 CMS and its surrounding services is only visible to the small number of people actively participating.
We believe the entire TYPO3 ecosystem will benefit from a change in this situation. We would like to clearly define the innovation process and increase the access to and involvement in it for users, developers, and TYPO3 Association members.
These are sub goals towards this goal:
Further goals are:
To reach these goals, we see the necessity of multiple and connected roles such as, TYPO3 Association Board members, the already mentioned Innovation Manager, and a possible Developer Relations Manager. These roles and persons should take part in regular, monthly stakeholder and decision-making meetings that should also provide insights from the TYPO3 community.
Responsible: The board member responsible for the Product is responsible for the concept of the strategic goals and can assign tasks to the GmbH, BCC, teams, external support, etc. The person is also responsible for the exchange of information and communication to other stakeholders and external partners. The person will present the roadmap for the prioritized items in a board meeting. The person reports monthly to the rest of the board on the progress.
Action items for all board members: Each board member should read and understand the product strategy documents. The owner of the documents is the board member responsible for the Product
Controlling: The progress of the plan and achievements is reported in a board meeting, at least once per quarter. Responsible for controlling is the Board at large.
Long-term transfer of expertise to customers, users, and decision makers will be an important topic for the TYPO3 Association and its members. It is also important beyond our community.
In a best-case scenario, we should be able to work preemptively on educating non-technical users — especially decision makers — about the importance of open source and related benefits, such as digital sovereignty. We see that large tech companies have a strong influence on how personal data and content is created, used, and distributed across the web and that they tailor it to fit their commercial interests.
As an example, the Cyber Resilience Act (September 2022) in the EU is primarily intended to increase security in the use of software and hardware to seal them off from cyberattacks. Here, it is immediately necessary to familiarize the legislative and executive bodies with the open-source theory and practice, its importance for the internet, and its possibilities and limitations.
We see the opportunity to lead, learn from, and collaborate with other organizations (e.g. other FOSS CMSs, eco Association, Open Source Initiative, OpenForum Europe, etc.) Working with them will benefit open source software in general, and thus also TYPO3.
We will intensify our efforts to reach out and connect with organizations in the free and open source (FOSS) community at large. We see every TYPO3 Association board member actively reaching out. Additional roles might arise in the future, and will be assigned in the TYPO3 Association board.
Responsible: The board member responsible for promoting informed decisions is responsible for the concept of the strategic goals and can assign execution to the GmbH, BCC, Teams, external support, etc. The person is also responsible for the exchange of information and communication to other stakeholders and connected parties. The person will present the roadmap for the prioritized items in a board meeting. The person reports on progress to the rest of the Board on a monthly basis.
Action items for all board members: Each board member should read and understand TYPO3’s views and narrative around the importance of open source and its connected challenges, such as digital sovereignty. The owner of the documents is the board member responsible for promoting informed decisions
Controlling: The progress of the plan and achievements is reported in a board meeting, at least once per quarter. The board at large is responsible for controlling.
During the strategy development process we want to expand these principles for TYPO3 CMS, related services and the TYPO3 association with additional principles:
TYPO3 Association memberships can be acquired by natural or legal persons by payment of a membership fee. For the duration of the payment period, the respective title may be used by the natural or legal person that is the actual contracting party.
This means that membership titles of natural persons may not be used by legal entities, this natural person is working for. Conversely, natural persons may not use the membership titles of legal entities they are working for.
This is a special agreement with TYPO3 GmbH. Please refer to the specific contractual rules that apply for your partnership.
Acquired titles are obtained by successfully completing a certification exam and receiving an official certificate.
Certification titles can only be obtained and held by natural persons.
The number of certified persons employed by a legal entity may be used in the communication of that entity for the period of validity of the respective certifications.
Through voluntary work in official TYPO3 teams and bodies of the TYPO3 Association, titles and positions can also be acquired. These titles may only be used by natural persons for the duration of their respective activity.
Warning
Only team members listed at the typo3.org team pages are allowed to use a title.
The titles described under 1, 2, and 3 may only be used by the natural or legal persons described and for the duration of their membership, certification, or activity. Any use beyond this time, even with additions such as “former”, is not permitted. The only exception to this is the description of former activities in official TYPO3 teams in CVs or similar listings, but not for promotional purposes.
Max Muster
Former member of the TYPO3 Content Team
2019 - 2019 Member in the TYPO3 Content Team
Version 2.0 13.11.2025 • Author Stefan Busemann
In case of extraordinary elections, the timetable is shortened:
The Voting Committee of the TYPO3 Association announces the election via the member mailing list and a news post on typo3.org. The announcement describes, for which positions people can apply. It also reminds all members to check their membership profiles and update their email addresses, because the voting tokens are sent to that address. The second announcement is a reminder for the members.
The first announcement is sent 84 days before the General Assembly (49 days in case of an extraordinary Assembly). The second announcement will be sent 21 days before the General Assembly.
Any individual can apply for positions in the TYPO3 Association. The nomination must be received via the nomination form (https://voting.typo3.org) within the period of the nomination phase.
The minimum data required are:
Each nomination can be done only for one election. In case of a nomination for more than one election (e.g. Board and BCC), the nomination form has to be submitted separately for each election.
The nomination phase starts 56 days (49 days in case of an extraordinary election) before the General Assembly and lasts for 28 days.
The nomination can be refused by the Board of TYPO3 Association, if the nominee can not prove a relationship to the TYPO3 project or if the nominee did harm to the project or the Association. Further nominations are not allowed if the result of an election could lead to a situation where two employees of the same company would be part of one body.
The members can discuss with all nominees. A platform is provided by the TYPO3 Association. The discussion phase starts 28 days before the General Assembly and lasts for 14 days.
The Voting Committee of the TYPO3 Association sends an invitation for the online voting to each member. The due date for the start of the online voting is latest -14 days at 0:00 before the General Assembly and earliest -28 days before the General Assembly. To be an eligible voter the admission fee has to be paid by the member and the membership must be signed until two weeks before the beginning of the online voting.
Each voter has as many votes, as positions in the body are to vote.
E.g. three members of the Board have to be elected, so the voter has three votes for this voting. It is not possible to accumulate or to cross-vote.
If a nominee has applied for more than one body and is elected in more than one body, he is elected for that body, which is elected first.
The voting committee is responsible for the online voting process. It sets up the platform and checks the validity of the election.
The Board nominates a voting committee which consists of at least three members. Members of the voting committee must not be part of a running election.
The committee will write a protocol about the voting which consists of:
The data in the online voting tool is kept up to the start of the next nomination phase. With the start of the next nomination phase, all expired elections and pollings will be removed.
Tenure of the board of the TYPO3 Association is three years and ends at a regular General Assembly. The Board is elected by the members of the TYPO3 Association.
The President, the Vice-president, the Secretary, the Treasurer and the four Assessors are elected within the Board itself. The president must be at least one year member of the Board. If no majority can be found within the Board for the president, a new election by the members takes place.
The Budget Polling is not an official election. It is a tool of the Board, to ask the members for their preferences regarding the next budget. For the polling, the voting is used, but it has no official character.
If a member of a body does not want to continue his job, he should inform the respective body 6 months before the ending of his mandate.
Stefan Busemann, Member of the Board of the TYPO3 Association, typo3.org
Short link to this page: typo3.org/coc
This code of conduct was voted into effect through a community vote that ended 7 March 2022.
Be constructive and considerate, respect other people's boundaries. Consider your actions—are they OK?
The Code of Conduct is here to ensure everyone feels safe and welcome in the TYPO3 community. It defines general rules and gives advice on how to behave.
Don’t be afraid to be yourself, but be your best. You are a free individual with the right to your own personal views and values. However, you also have the responsibility to treat people with respect.
This Code is using general terms and expects you to judge each situation by yourself. Even when acting with the best intentions, please understand that others might judge a situation differently to you. Stop when asked to. That’s your warning. You shouldn’t need more.
Local law might be more restrictive than this Code.
This Code of Conduct applies to all persons present at or in the following:
This also includes sponsors, speakers, and staff at events, for the entire duration of the event.
The Code of Conduct contains two sections:
We hold these rules to be self-evident:
Try to …
نحن نعتبر هذه القواعد من البَدِيهِيّات:
تعامل مع جميع أعضاء المجتمع بإحترام، بِغضّ النظر عن العرق، أو الجنس، أو العمر، أو التوجه، أو الإعاقة، أو المظهر الخارجي، أو الهُوِيَّة الوطنية، أو المعتقدات، أو الديانة، والخ. احترم خصوصية التعامل بالجسد وامتنع عن السلوكيات الجسديّة الخادشة للحياء. لا تبدأ، ولا تشجّع على العنف الجسدي أوعلى الشَخصَنَة، والحُروب الكلامية، والتحريض على الغير. نحن لا نتسامح أبداً مع التحرش الجنسي، الهجمات الشخصية، أو السلوك المُهين مع الآخرين. يشمل ذلك التصوير والتجسس على الآخرين، والايماءات الجنسية، ومتابعة الشخص أو مُراقبته عن عَمْد. لا تَقُم بتعطيل المُحادثات والأحداث والفَعاليات الأخُرى المنظمة. استخدم معلومات تواصل صحيحة (مثل Slack، والبريد الإلكتروني، وما إلى ذلك) والتي يُمكن الردّ عليها بشكل مباشر.
حاول أن…
تقول شكراً لِمن يستحق الشكر. تطلب المساعدة عندما تكون مُتردداً في شيء ما. تحصل على مساعدة من أطراف خارجيّة إذا كنت عالقاً في خلافٍ ما. تحترم الوقت التطوعي للآخرين. تكون إيجابيّاً وقدم ردود فعل بنّاءة. تنتبه إلى اللغة التي تتكلّم بها، فبعض النُكات أو الفكاهة أو السخرية من شيء ما، قد تكون صعبة الفهم لدى الجميع.
这些规则对我们来说是理所当然的:
這些規則對我們來說是理所當然的:
Smatramo da su ova pravila očigledna:
Pokušajte …
Vi anser disse regler for at være indlysende:
Forsøg at …
Deze regels beschouwen wij als vanzelfsprekend:
Probeer om …
Nous considérons que ces règles sont évidentes :
Essayez :
Diese Regeln sind für uns selbstverständlich:
कोशिश करें ...
हम ये नियम स्वतंत्र स्पष्ट स्थान रखते हैं
Kami memegang aturan ini untuk menjadi dasar dari prisip kami:
Mencoba untuk …
Consideriamo queste regole ovvie
Cerca di …
Vi anser disse regler for å være selvinnlysende:
Forsøk …
Me reknar desse reglane for å vera sjølvinnlysande:
Forsøk …
Consideramos que as seguintes regras são evidentes:
Busque …
Consideramos estas normas como sobreentendidas:
Trata de …
Die Regle send för üs säubstverständlech:
ہم ان اصولوں کو خود وضاحتی سمجھتے ہیں۔
کمیونٹی کے تمام ممبران کے ساتھ عزت کے ساتھ پیش آیئں بلا تفریک ، نسل، جنسی شناخت، عمر، جنسی رجحان، معذوری،شکل و صورت، قومیت، نسل، عقائد، مذہب وغیرہ۔ جسمانی سالمیت کا احترام کریں اور جسمانی طور پر مداخلت کرنے والے رویے سے پرہیز کریں۔ ذاتیات، شعلہ بیانی اور مذاق اڑانے سے گریز کریں اور ایسے عمل کی حوصلہ افزائی سے بھی گریز کریں ۔ ہم ہراساں کرنے، ذاتی حملوں، یا توہین آمیز رویے کو برداشت نہیں کرتے۔ اس میں بلا اجازت فوٹو گرافی یا ریکارڈنگ، ناپسندیدہ جنسی توجہ، اور جان بوجھ کر پیچھا کرنا شامل ہے۔ بات چیت اور دیگر منظم پروگراموں میں خلل نہ ڈالیں۔ رابطہ کی درست معلومات (مثلاً سلیک، ای میل، وغیرہ) استعمال کریں جس پر براہ راست جواب دیا جا سکے۔
کوشش کریں ..
حوصلہ افزائی کے مستحق کی حوصلہ افزائی کریں جب آپ کو یقین نہ ہو تو مدد طلب کریں۔ اگر آپ کسی اختلاف میں پھنس گئے ہیں تو باہر سے مدد حاصل کریں۔ لوگوں کے رضاکارانہ وقت کا احترام کریں۔ مثبت رہیں اور مفید رائے دیں۔ اگاہ رہیں کے مشکل زبان کو سمجھنا دوسروں ک لیے مشکل ہو سکتا ہے
Rydym yn credu bod y rheolau hyn yn gwbl amlwg:
Ceisiwch …
In case of a presumed Code violation, please contact the event staff, or a TYPO3 Association ombudsperson. The ombudspersons can always be contacted at `ombudsperson@typo3.org <mailto:ombudsperson@typo3.org>`__.
Reported cases are reviewed, without undue delay, by at least two TYPO3 Association ombudspersons. The review process should not usually take longer than two weeks.
In case of a suspected violation, all parties have a right to be heard during the review process. The ombudspersons may interview additional witnesses at their own discretion.
Event organizers or platform admins may limit a person’s access to the event or platform while a case is being reviewed. Any right to refund of event fees, etc. must be specified in the event’s refund policy.
All decisions made by the ombudspersons can be appealed to the TYPO3 Association Board. The Board’s decisions are final.
Reactions to a breach of this Code depend on the type, seriousness, and context of the violation. Typical reactions are defined and published by the TYPO3 Association Board and might span from a formal warning to a time-limited exclusion from some or all platforms.
Commentary and frequently asked questions to the Code of Conduct.
Treat all community members with respect, regardless of race, gender identity, age, sexual orientation, disability, physical appearance, national origin, ethnicity, beliefs, religion, etc.
It means that you think about what you say before you say it and consider the results of your actions. Could it hurt someone? Certain words and actions may have meanings that go beyond what you intend.
Generally speaking, if you are at the premises of a TYPO3 event or on a platform listed in the section Applicability and Scope, everyone you meet and interact with should be considered community members.
If you meet community members outside of these settings, they are still community members who can invoke the Code of Conduct. This is because the fear of repeated disrespectful behavior can discourage their participation in the TYPO3 community events and platforms.
Where you draw the line is up to you. The Code of Conduct applies to both. In some contexts these words have the same meaning, but “beliefs” also encompasses temporal (non-religious) convictions, likes, and dislikes. For example, which political party or CMS is the best.
The Code of Conduct requires you to show your fellow human beings respect. The “etc” (or “et cetera”) indicates that the list of items is not complete. You might think of more similar words, and they are also included. You can’t behave disrespectfully in a certain way just because it isn’t in the list.
Respect bodily integrity and refrain from physically intrusive behavior.
Basically don’t touch anyone without them having given you permission to do so.
Also consider that most people maintain a buffer zone or intimate zone around their body. Deliberately moving within this zone can be experienced as uncomfortable and a breach of integrity.
Doing anything that makes the other person want to move away or wish you weren’t there, such as deliberately following, stalking, threatening, or continuing a conversation when the other person has asked you to stop.
You can give a hug or kiss to everyone who answers “yes” when you ask them “may I give you a hug/kiss”. Hugging and kissing are more common in some cultures, but some people find it a breach of their personal integrity.
A consent to a hug can also be non-verbal. If you approach someone with arms wide open and they open their arms in return, they are consenting to a hug. If they keep their arms down, their are not up for a hug right now.
Do not start, continue, or encourage personal attacks, flame wars, and trolling.
Also known as “roasting”, this is to use insults, hostile language, or offensive words against or between people. It is often seen online, but the Code of Conduct covers both online and offline situations.
In our context, trolling is to deliberately provoke emotional reactions, manipulate or derail a conversation or discussion by inserting off-topic, insincere, or excessive arguments, or by being unnecessarily argumentative.
Even if your contributions are sincere and have the best intentions, people can perceive it as trolling. Be sensitive and stop unproductive arguments and don’t repeat yourself unnecessarily. If someone tells you to stop trolling, take a minute to consider why that might be. Step down gracefully.
Defending the product or community should never be done by demeaning or attacking other people. Only argue facts. For example, using bad words about someone will neither further the conversation nor defend the product. Saying “what you're saying is wrong because X, Y, Z” is the way to handle it. If the other party doesn't drop the topic, you drop the topic. Say: “I don't think we are getting anywhere with this discussion. I won't make any further replies.”
We do not tolerate harassment, personal attacks, or demeaning behavior. This includes intrusive photography or recording, unwanted sexual attention, and deliberate stalking or following.
If you see a Code of Conduct violation that falls under this clause, please consider speaking up against it or contacting the ombudspersons or event organizers.
It means to use words to frighten, humiliate, belittle, or degrade other people. Given emotional stress or anger, it isn’t always premeditated. It is our job as fellow TYPO3 community members to be constructive and stop it.
While rule #3 disallows participation, this rule covers more serious situations. While trolls are better left alone, those bystanders who feel safe to do so might consider intervening to stop ongoing harassment or unwanted sexual attention
Do not disrupt talks and other organized events.
No frequently asked questions available.
Use valid contact information (e.g. Slack, e-mail, etc.) to which direct responses can be made.
No, you don’t have to publish your real name or any sensitive personal information. However, we expect that your active participation in the community is a two-way conversation, not a monolog. If you want to voice your opinion, please take part in a fruitful and constructive discussion.
No. You can contribute code or money anonymously. However, the moment you voice an opinion or respond to others, we require you to be able to receive responses from others.
Give credit when it is deserved.
Include anyone directly involved in or who directly inspired your work. In the case of code contribution, you might choose to credit the person or people who:
This depends on context. Ask around or spend a little time looking at how other people have done it.
Ask for help when you are unsure.
This depends on context, but feel free to ask the community—even if your question is “where do I ask for help about this”. The Help and Support page has some good suggestions.
Yes. We all start out asking questions before we know enough to answer questions from others. And it never stops: Even the most experienced TYPO3 community members ask questions.
Get outside help if you are stuck in a disagreement.
Free to contact someone you know in the community or contact the TYPO3 ombudspersons.
Be respectful of people’s volunteer time.
Assume they are volunteers until you are certain they aren’t. Asking people is a good place to start.
Don’t ask or expect too much. Consider sponsoring a feature or bug fix.
Everyone should be mindful of other people's time. However, when speaking about the same task, volunteer time has a very different quality to paid time. Example: Repeatedly asking urgent questions and expecting immediate answers from volunteer community members would violate this section in the Code of Conduct. Doing the same with paid support would be a matter for your terms of service agreement.
Be positive and give constructive feedback
Rather than just saying that something is wrong, explain how it can become better.
Be aware that language can be difficult—sarcasm and irony is not understood by everyone.
Language can be difficult to understand, especially if it is a foreign language. Using complicated and uncommon words can make it especially difficult to understand what is being said. Some people also find reading or hearing difficult.
It might be (sometimes darkly) funny when something ends up the exact opposite of what you would normally have expected. It is ironic when the code change that is supposed to fix a hundred bugs instead introduces a hundred more bugs.
Sarcasm is when you say one thing, but mean the opposite. When speaking, we sometimes use a different intonation or pitch to underscore that we’re saying something sarcastic. When writing, we sometimes indicate sarcasm by putting a word within quote marks.
Let’s say you are stuck in a long queue of people and you’re very bored. Saying “this is so fun” sarcastically might underscore that the experience is absolutely not fun at all.
Lack of fluency in a language can make it hard to detect the subtle hints of sarcastic remarks. Others find sarcasm difficult due to mental disabilities or disorders.
From the TYPO3 Code of Conduct Community Review, September 2021.
Can we add “When you give promises to people, keep them.” as a basic rule?
Answer from the Ombudsperson Group:
Thank you for the suggestion. We believe promises can be hard to keep in certain life situations. Also, volunteer contributors have no contractual obligations. That doesn't mean promises have no value (on the contrary, they should be highly valued), but it is a tough rule if you consider the words of the Applicability and Scope section: “The Basic Rules are binding and should always be followed. Going against them will have consequences.”
You have for sure best intention here: “Even when acting with the best intentions, please understand that others might judge a situation differently to you. Stop when asked to. That’s your warning. You shouldn’t need more.“
But it's misguiding. I could say: I judge quite some parts of the coc of being way too strictly harmony driven - suppressing needed discourse and challenging others were needed to claim the responsibility that is needed for a healthy, grown-up community!
Using your coc against you: I’d like to ask the group to stop (this coc)! This is your warning. You shouldn’t need more! - Got my point? ;-) Of course, I don't want you to stop not do I want to warn you. Maybe a little on this “forcing harmony at any price thingie” of yours.
Less rules, more principles. Less harmony at any price, more healthy discourse, more responsibility, more diversity.
Thanks for your efforts!
Answer from the Ombudsperson Group:
Thank you for your feedback. Our intention is that the Code of Conduct should help discussions stay productive and fruitful. Even heated discussions can be fruitful. The Code of Conduct draws the line at things like personal attacks and harassment. We believe it is possible to disagree deeply with other people, but still maintain a constructive dialogue.
In the second paragraph, I would change "Please consider that this code also gives you the responsibility to behave respectfully towards everyone." to "Please consider, though, that this code also confers upon you the responsibility to behave respectfully towards everyone."
Like, sure, everyone is a free individual - but by abiding by the CoC you need to be aware that you are expected to act within certain guidelines. I consider this to be less of a gift of responsibility and more of an obligation of responsibility.
Answer from the Ombudsperson Group:
Your differentiation between a gift and an obligation makes sense. To keep it short and sweet and align it with the updated Basic Rule #1, we will change the last sentence in the second paragraph of the preface to “However, you also have the responsibility to treat people with respect.”
"It means that you think about what you say before you say it and consider the results of your actions. Could it hurt someone emotionally or physically?"
- How can something someone says hurt someone physically? This is physically not possible
- "hurt someone emotionally" - when code is criticized, people can get "hurt emotionally", especially if their "belief" is that they write the best code. So no negative code reviews anymore, just in case someone "could" be hurt emotionally?
Answer from the Ombudsperson Group:
Thank you for the feedback. We will change the sentence “Could it hurt someone emotionally or physically?” in the FAQ to “Can it hurt someone?”.
Negative code reviews are of course still possible. Constructive criticism and feedback are encouraged. A “-1” should neither be made without reason nor perceived as an insult or attack.
I‘d exchange “respect” with “decency” and “courtesy”. Reasoning: In a lot of cultures respect is earned by actions. Respect should be given based on a persons actions and I think guess treating people courteously and with decency is the original meaning of the sentence.
Answer from the Ombudsperson Group:
Thank you for the feedback. You have a good point, and we wanted to give you a good answer. To do so, we had to ask for some advice and give it some good thought.
We will change “Behave respectfully to all community members” to “Treat all community members with respect”. Even if respect is earned by actions, the code of conduct says that all community members should extend respect first, regardless of whether the person has earned it or not. That means we should assume good intent. This also the meaning explained in the FAQ.
In English the word respect is a broad and widely accepted term. It is hard to find a word that is entirely unambiguous. Decency and courtesy are not less open to misinterpretation. By swapping the adverb respectfully with the noun respect, we hope the sentence becomes clearer than it was.
This means you cannot hug people anymore without checking first. While I understand the rule it is a bit unfortunate because it will lead to less warmth in human contact in the long run. You can check first if touching (hugs, shaking hand etc.) is ok, but I assume most people will not bother to do this and refrain from touching in general.
Answer from the Ombudsperson Group:
Thank you for the feedback. We believe human warmth can be expressed in many ways, and hugging is definitely one of them. Physical closeness usually requires some kind of existing connection, just as you probably wouldn't hug a random person on the street without some kind of prior interaction.
A consent can be non-verbal. If you approach someone with arms wide open and they open their arms in return, they are consenting to a hug. If they keep their arms down, their are not up for a hug right now.
I like "condone" isn't a strong enough word. "We don't condone" is often used as a weasel-word (at least in the US) to mean "I don't approve of, but I am not going to do anything about it." I recommend strengthening it to "we do not tolerate".
Answer from the Ombudsperson Group:
Thank you for the feedback. We will change “We don't condone” in Basic Rule #4 to “We do not tolerate”.
I support the clause saying everyone has a responsibility to discourage and stop inappropriate behavior. But that is not at all implied in the wording of the original statement from the "short version." If that's the intended difference between points 3 and 4, that needs to be better stated. As is, it seems like it comes out of nowhere in the FAQ part.
Answer from the Ombudsperson Group:
You are quite right. The FAQ entry doesn't entirely represent the meaning of the rule. We will change the end of the FAQ entry to say “… this rule covers more serious situations. While trolls are better left alone, those bystanders who feel safe to do so might consider intervening to stop ongoing harassment or unwanted sexual attention”.
Why should I only respect the time of volunteers? Shouldn't I be mindful of the time of everyone? Just because someone is paid to do a job, doesn't mean I need to unnecessarily waste their time.
Answer from the Ombudsperson Group:
You are right that everyone should be mindful of other people's time. However, when speaking about the same task, volunteer time has a very different quality to paid time. Example: Repeatedly asking urgent questions and expecting immediate answers from volunteer community members would violate this section in the Code of Conduct. Doing the same with paid support would be a matter for your terms of service agreement.
This is good. However, you should be respectful of someone's time even when they're paid in what they're doing, or in some cases someone may be spending a mix of paid and unpaid time. Everyone has the same hours in the day, and they're all valuable. Just be respectful of people's time, period.
Answer from the Ombudsperson Group:
It is great to hear that you like the proposal. Thank you. We have answered a similar question regarding respect for time above.
This should also apply for the creation of issues on forge.
Answer from the Ombudsperson Group:
Thank you for the feedback. We will shorten General advice #5 to "Be positive and give constructive feedback."
"constructive feedback" is unfortunately not something everyone understands. I would create an extra bullet point for this and explain it (instead of lumping it in "be positive").
Also, if you can agree on this, "constructive feedback" has IMHO some more elements. In addition to the ones you already wrote:
- DO NOT GENERALIZE negative feedback and be SPECIFIC: not "your suggestions are (always) irrelevant", but e.g. "you made a number of suggestion this year. Though some were very good and have been implemented, you might take some time to search if an issue already exists before you post."
- explain why, instead of, "your issue is unhelpful", "your issue is a duplicate of #123."
One thing I noticed when people give positive feedback in the TYPO3 community: It is often very general and not specific. Specific feedback (positive and negative) is more helpful IMHO.
Answer from the Ombudsperson Group:
Giving constructive feedback is indeed no easy task. We try to keep the code of conduct short, so we won't add it all in there, but we think it is an excellent as a FAQ item, and you have given us a very good starting point. Thank you!
Would the ranting which happened on twitter some weeks ago already be against the code of conduct and when does defeating the product and the loved community end and trolling begin?
Answer from the Ombudsperson Group:
(We think you mean defending, rather than defeating, so we're basing the answer on that.)
We can't comment on individual cases, and since this case happened in the past, it isn't covered by this code of conduct. In a potential future case where someone attacks TYPO3 or the community, it will be the defender’s job to be in accordance with the code of conduct, just as much as anybody else. Defending the product or community should never be done by demeaning or attacking other people. Only argue facts. For example, using bad words about someone will neither further the conversation nor defend the product. Saying “what you're saying is wrong because X, Y, Z” is the way to handle it. If the other party doesn't drop the topic, you drop the topic. Say: “I don't think we are getting anywhere with this discussion. I won't make any further replies.”
I very much like the requirement that both parties have a right to be heard. That's a critically important component often left out of many CoCs in the name of "protecting victims."
However, there is no mention of anonymity either way. That's... a touchy issue, depending on the situation and what the infraction is. I know some people feel reporter-anonymity is critical and necessary to protect victims, but conversely anonymity means the accused is unable to fully respond and defend themselves if appropriate. There should probably be some mention one way or another to avoid that becoming an issue in-the-moment.
Even if it's just "the need for anonymity will be judged case by case by the ombuds-team" or something like that, it should probably get a mention somehow so that it doesn't become a meta-fight later.
Answer from the Ombudsperson Group:
Thank you for your feedback. We will definitely allow anonymous reports of incidents. It is important to note that a reporter doesn't have to be a party in the case or know all the facts for certain. We define a party in the case as anyone directly involved in the code of conduct violation. If the violation wasn't directed at anyone in particular, a single person might be the only party.
The exact review process is not a part of the code of conduct. However, all good incident responders will first gather information from witnesses before judging if the case is a violation. Only if and when the case is judged to be a violation will the violating party be contacted and interviewed. Allowing everyone to be heard is a necessary step in a fair incident review process.
Everyone has the right to privacy. The identity of parties and witnesses involved in a review will be kept secret. In some cases, violators' names will be given out to third parties on a need-to-know basis, under a non-disclosure agreement. For example, event organizers may be given the name of anyone who is denied access to events.
I am concerned that the CoC can be used to shut down people who are a little socially awkward or who have unwanted views whatsoever. Is there an appeal process so that people who have violated the CoC can get their record cleared? Do you give people a second chance (after visible improvement and insight)? I would rather see it as a tool for guidance and nudging towards better behaviour rather than a punishment tool, without giving people room to improve and grow.
Answer from the Ombudsperson Group:
We share your concern, so preventing this has been a large part of our disucssions. Let's take them point by point:
This Code of Conduct is released under a Creative Commons Attribution 4.0 International (CC BY 4.0) license.
TYPO3’s Complaints Handling Policy aims to provide a means for receiving complaints or feedback, encourages the reporting of community complaints and issues, ensure that the Complaints Handling process is easily accessed, understood by the TYPO3 Community, meets the requirements of the TYPO3 Project strategy, and provides for a fair, equitable and timely response.
Expression of dissatisfaction made to the TYPO3 organization, related to its Code of Conduct, or the complaints-handling process itself, where a response or resolution is explicitly or implicitly expected.
This document does not apply to complaints referred for resolution outside the organization or for TYPO3 Company employment-related disagreements.
Only complaints within the Applicability and Scope of the Code of Conduct are covered by this policy.
The TYPO3 Ombudsperson Group, on the behalf of the TYPO3 Association, is actively committed to defining and implementing a complaints handling process. This team gets sufficient resources from the TYPO3 Association in order to be committed to complaints handling, and to manage it effectively and efficiently. These include resources such as training, procedures, documentation, external specialist support, materials and equipment, software and finances. This resource’s allocated budget follows the same approval process as any TYPO3 official team and is reviewed annually.The ombudsperson group lead is the budget owner.
The TYPO3 Ombudsperson group members have the personal attributes, skills, training, education and experience necessary to handle complaints.
The complaints-handling process is communicated to TYPO3 Association members, TYPO3 Company employees and other relevant interested parties. Individual complainants are provided with adequate information about the handling of their complaint.
The complaints-handling process is easily accessible to all complainants on the official TYPO3 websites. It details the steps about making and resolving complaints. The complaints-handling process and supporting information is easy to understand and use. The information is in clear language, in English, and if published on digital documents, in PDF/UA format, so that no complainants are disadvantaged.
Access to the complaints-handling process is free of charge to the complainant.
The TYPO3 Ombudsperson Group addresses the needs and expectations of complainers with respect to complaints handling. Complaints are handled as expeditiously as feasible given the nature of the complaint and of the process used.
The Ombudsperson Group ensures that the information about its complaints handling is accurate and not misleading, and that data collected are relevant, correct, complete, meaningful and useful.
Personally identifiable information concerning the complainant is available where needed, but only for the purposes of addressing the complaint within the organization and is actively protected from disclosure, unless the complainant expressly consents to its disclosure or disclosure is required by law.
A complaint can be sent by any TYPO3 Association member, TYPO3 official event participant, or TYPO3 Company employee by emailing the TYPO3 Association Ombudsperson Group via the official typo3.org form or ombudsperson@typo3.org.
This policy outlines the difference between groups, as well describing the decision-making, empowerment and disbanding processes.
Teams are responsible for a certain part of the community, indefinitely or for a longer period of time.
Committees are established by the TYPO3 Association Board as defined in the TYPO3 Association’s bylaws.
Every Team and Committee sends the Leader (or a representative) to the Team Leader Group. The Group is appointed by the Board of the TYPO3 Association and a representative of the Board chairs the group.
An initiative consists of people with a common interest to make long-term improvements to a specific area of TYPO3, including strategic plans, goals, and monitoring of progress. An Initiative is instanced by Team, Committee or the TYPO3 Association.
It’s important that initiatives maintain focus on achieving their defined goals. When the goals have been reached, the initiative is dissolved.
Examples of initiatives:
Decisions should be made within the groups (teams, Committees, Initiatives) themselves.
Each decision should be aligned with the common roadmap of the TYPO3 project.
If a decision influences the work of several teams, the Team Leader Group should be consulted. This is especially important if new services are being introduced, existing services are being shut down, and for situations concerning the external presentation of the TYPO3 project.
If the Team Leader Group is not able to reach a decision, the Association Board must be brought into the discussion.
Every decision should embrace the TYPO3 values. The benefits of changes should always be determined.
Every decision must be based on factual pros and cons and the intention to improve a situation. (“What is improved by choosing this particular direction?”)
TYPO3’s Dispute Resolution Policy aims to provide guidance to plan, design, develop, operate, maintain and improve effective and efficient external dispute resolution for complaints. Dispute resolution provides a solution when the TYPO3 organization fails to solve a complaint internally. Most complaints can be successfully resolved within the organization, without the need for more time-consuming and confrontational procedures.
Disagreement, arising from a complaint submitted to the TYPO3 organization.
The first expression of dissatisfaction made to the TYPO3 organization is a complaint. It is then handled by the Complaint handling process. It becomes a dispute if not resolved by the organization internally.
Since dispute resolution takes place when a complaint cannot be resolved internally by the members of the Ombudsperson Group, the dispute resolver must be someone external to the TYPO3 organization.
Dispute resolvers should have the personal attributes, skills, training and experience necessary to discharge their responsibilities in a satisfactory manner.
The TYPO3 community is international. It is therefore possible that a dispute may arise between two parties from different countries and native languages. Depending on the situation, the dispute resolver will be selected to ensure the best conditions for communication between the parties.
This document does not apply to disputes referred for resolution outside the organization or for TYPO3 Company employment-related disputes.
Only disputes within the Applicability and Scope of the Code of Conduct are covered by this policy.
Participation of the complainants in dispute resolution offered by the TYPO3 organization is voluntary. Consent to participate should be based on full knowledge and understanding of the process and possible outcomes.
The dispute resolution process is communicated to TYPO3 Association members, TYPO3 Company employees, and other relevant interested parties. Individual complainants are provided with adequate information about the handling of their dispute.
The dispute resolution process is easily accessible to all complainants on the official TYPO3 websites. It details the steps about making and resolving disputes. The dispute resolution process and supporting information is easy to understand and use. The information is in clear language, in English, and if published on digital documents, in PDF/UA format, so that no complainants are disadvantaged.
Access to the dispute resolution process is free of charge to the complainant.
The TYPO3 organization should engage in dispute resolution with the intent of fairly and honestly resolving the dispute with the complainant. The TYPO3 organization should select a provider whose dispute-resolution personnel and dispute resolvers engaged in dispute resolution are impartial and objective, so that processes, recommendations and determinative decisions are fair to both parties and are recognized as being made independently.
Dispute resolution should be delivered as expeditiously as feasible, given the nature of the dispute and of the process used.
Personally identifiable information should be kept confidential and protected, unless disclosure is required by law, or consent for disclosure is obtained from the person concerned.
Similarly, trade secrets should be kept confidential and protected, unless disclosure is required by law, or consent for disclosure is obtained from the party that has the trade secret.
The TYPO3 Association should acquire and deploy resources such as personnel, information, materials, funding and infrastructure, so that it can effectively and efficiently select and pay an appropriate dispute resolver provider, contribute to the proper functioning of the provider, participate in the dispute-resolution process, and evaluate the performance of the provider, its resolvers, and the dispute-resolution process.
This resource’s allocated budget follows the same approval process as any TYPO3 official team and is reviewed annually. The ombudsperson group lead is the budget owner.
The Dispute Resolution process starts when the TYPO3 organization fails to solve a complaint internally with the Complaint Handling process, and if the Ombudsperson group members decide that they should delegate to an external ombudsman.
Since the community is growing, we needed to have a written ruleset on how to use a personal @typo3.org address for communication to the outside. The rules as described below were voted on and accepted unisonous during the board meeting on October 11th 2010.
Instead of "firstname@typo3.org" or "nickname@typo3.org" new personal addresses will always be built as "firstname.lastname@typo3.org". This will avoid conflicts where multiple persons share the same firstname (sharing the mail address doesn't seem a clever solution). All existing address owners will get a "firstname.lastname@typo3.org" address, too. Their existing "firstname@typo3.org" or "nickname@typo3.org" address can be used further on, the new "firstname.lastname@typo3.org" will be redirected to the existing one. It's up to the owner, which one is used for communication to the outside. In the case that a second person with exactly the same name requires an address, a solution must be thought out that fits best for the situation.
Basically erveryone that is officially in charge of an official job within the TYPO3 universe should be allowed to get a personal mail address @typo3.org, this includes
If the above rules are not followed by the owner of a personal address, the Board of the TYPO3 Association can revoke the permission on such an address.
Before a personal address can be revoked, the owner has to be warned clearly in written form (CC to board list). If the situation doesn't change within reasonable time, the address can then be deleted.
--
Typus Bughunter
Member of the TYPO3 CMS Team
--
TYPO3 .... inspiring people to share!
Get involved: typo3.org
--
Olivier Dobberkau
President of the TYPO3 Association,
typo3.org
TYPO3 Association,
Rathausstrasse 14
CH-6340 Baar
Switzerland
The TYPO3 Ombudsperson Group is responsible for ensuring the wellbeing of everyone in the community through education about and enforcement of the Code of Conduct <coc>. To provide arbitration and mediation and general help in conflict resolution, the TYPO3 Association must ensure an environment that is open to feedback (including complaints), resolving any complaints received.
To fulfill the community's expectations regarding conflict mediation, the Ombudsperson Group has set up a full Community Mediation Process, validated by the TYPO3 Association Board.
This process consists of two possible levels when aiming to resolve a conflict: a first level of internal resolution called the Complaint Handling Process, and if this is unsuccessful, a second level of resolution with the help of external mediation called the Dispute Resolution Process.
Slack simplifies communication and brings our global community together, creating a virtual shared workspace where conversations are documented and accessible. These rules are a platform-specific addition to general community regulations, such as the Code of Conduct.
You can learn how to set up a TYPO3 Slack account.
-). Example: #generalcategory-specificcategory . This way, if someone is in several similar channels, they will be sorted in a way that is helpful for them.#cig (e.g. #cig-performance )#t3cs is used for TYPO3 Camp Stuttgart. That is already being used as hashtag. #t3ch-hamburg adds additional clarification and disambiguation.#ext-<extkey>. Example: #ext-news #t3ug<usergroupname>. Example: #t3ughof (User Group Hof), #t3ugrn (User Group Rhein-Neckar)#t3c<location>. Example: #t3ch (Hamburg) or #t3ch-hamburg (is longer, but avoids ambiguity)The Slack admin team identifies channel with duplicated purposes or with no actions. They will get archived and later deleted.
@user, @here, or @channel.Since the beginning, TYPO3 has been more than just a piece of software. It is a community. Our values are there to guide our work and make sure the community is a great place for everyone.
Trust and respect each person and the work the person does. Remember to give the trust and respect you expect to have from others. To be trusted and respected you need of course to be reliable. The concept of trust, respect, and reliability are not valid only for the people involved in the community, but are extended to the products as well. By being a reliable member and by doing a reliable and respected work, the outcome should automatically translate into great products that everyone can trust.
The TYPO3 Community defines itself as an inclusive one. With the wish of being open and not exclusive, the community wants to avoid barriers of any type. The openness that characterizes the community is directed to people and their backgrounds, to opinions within the community and outside, to the outside world, to other teams or groups, and to the market and its changes. Openness relates also to communication. Remember that an open communication fosters the community's growth and health, in an environment where everyone can know what's happening and what will happen.
An Open Source environment is characterized by collaboration. The TYPO3 world imagines collaboration as the sharing of knowledge, work, and support within teams and between teams, among people, and to the outside world. Sharing is improving and collaboration enhances the efficient use of resources, knowledge, and ideas. Whenever possible, work with others and support them, work transparently, and ask when in doubt: the others will share too.
The TYPO3 Community believes in a fun environment characterized by friendship bonds. Within the TYPO3 world each person has the possibility to meet inspiring people, build relationships, and share great experiences with others.
Remember that values finally translate into action. Remind yourself and others that we share the same values!
Since mid 2022, the TYPO3 CMS Product Strategy Group, with support from 4L Impact Strategies, has made significant strides in shaping the future of TYPO3. Through comprehensive analyses and end-user interviews, the team identified key opportunities and areas for improvement. These findings were thoroughly discussed in a series of workshops, culminating in an internal strategy paper first drafted in December 2023. It encapsulates the group's collective insights and outlines strategic objectives and forthcoming actions.
We conducted many analyses, in the form of business, market, JTBD, stakeholder, and SWOT analyses, to draw a global picture of the 2023 situation. We acknowledge that it is not possible to get authoritative data regarding the usage of TYPO3 and are aware of the difficult challenge of drawing conclusions from an incomplete picture. Still, it is possible to draw conclusions from common trends within the data sources and expressions from representative stakeholders (e.g. the JTBD interviews). During the ongoing efforts of the product strategy group, we will try to expand the analysis and get more insights, e.g. through telemetry. Additionally, a competitor analysis, together with market/technology evolution analysis, should be performed.
The product strategy, trend and market analyses, and this strategy paper will be updated annually, as a result of the group's ongoing work.
Around 85% of all TYPO3 instances are from the DACH region (Germany, Austria, and Switzerland). The German market is a strong user and backer of TYPO3. The markets in the USA, Great Britain, and Canada are showing significant growth potential for TYPO3, with a proportion of new sites that already exceed the global average. We'll focus our efforts on expanding TYPO3 and its user community to all continents, including emerging markets.
Decision makers evaluate costs over the long term, and may consider a cost to be an investment, provided that profits can be expected. We have identified a number of long-term cost reduction opportunities, such as less manual work (automation), lower cost of managing content and design, cheaper infrastructure, regulation compliance, etc. The cost of keeping software up-to-date and secure is a major topic, and we observed that customers are slow to upgrade to new versions. As a result, the feedback loop between releasing new TYPO3 features and getting end customers’ opinion is too long, and we want to reduce it. Finally, marketing features directly linked to tracking user profits must be easily integrated.
Many national and local governments, their agencies, and public institutions are using the platform today. TYPO3 is recognized in this sector as a reliable, regulatory-compliant tool. This is an important strength that we must continue to consolidate. Public organizations in European countries are particularly sensitive to these topics, and represent a high-potential market.
Currently, there are many people engaged in product development on a regular basis (in core development and official teams). Most of the effort is voluntary, and the work of some people is sponsored by agencies. The structure of the teams is the result of a gradual, volunteer-based process, and it is therefore not based on the required, but on the available expertise. Teams need to restructure and address their missing resources to cover the entire product innovation cycle.
The TYPO3 Product is an integral part of the TYPO3 Project. The TYPO3 product strategy is built within the context of the TYPO3 Project, and never outside of it. As a result, the TYPO3 Product vision is the same as — or a subset of — the project’s vision:
Empower * to unlock their potential, creating opportunities through content.
We believe that every person can bring something unique to the table. Content is fundamental to empowering people today to share knowledge, unlock possibilities, and achieve their potential regardless of who they are, what they believe, or where they come from. Our people, software, and services will empower content for everyone.
The TYPO3 Ecosystem is a big community consisting of, for example, agencies, solution providers, and freelancers. Additional services and solutions, like extensions, consulting, certification, and education are being offered. In contrast to, e.g. open-code models, TYPO3 is true open source, with key innovation delivered by community contributors.
The overarching vision is to cover the broadest range of applications, from small individual solutions to complete product architectures with the TYPO3 product as a base. The strategy focuses on alleviating the pain points of the current stakeholders and to foster exchange and interconnection between all actors. Therefore, it is compatible with the Equalize Opportunities through Open Source purpose statement.
TYPO3’s end users should benefit from the Ecosystem through use-case-specific solutions with better visibility and discoverability. The Ecosystem mission where end users and solution providers can match.
Based on the results from the jobs-to-be-done interviews and a product strategy workshop, the group has arrived at the following ten strategic goals. The goals have medium to long-term time frames (3–5 years). The goals and their priorities will be reviewed and modified during the annual update of the overall Product Strategy.
“We want to focus our development efforts on the public sector and small to medium enterprises (SME).”
Based on the results from the jobs-to-be-done interviews and recent market developments, the group concluded that TYPO3’s focus for the upcoming years has to be on the public sector and small to medium enterprises. This does not mean that all other TYPO3 customers and end-user groups will be excluded from our efforts, but that the main focus will be put on meeting the needs of these two representative customer sectors.
“We want to reduce complexity in order to enable more people to use TYPO3 CMS efficiently without the need for training.”
In order to better support end users with their daily tasks, TYPO3 should offer a modern and consistent user interface, self-explanatory workflows, and clear and unified best practices. Getting TYPO3 up and running has to be super-fast, easy, and bulletproof for newcomers.
“We want to help you deliver better content and better communication.”
TYPO3 should enhance the editors’ content creation experience by providing feedback and suggestions, promoting best practices and streamline task completion. For administrators, TYPO3 should assist in system management and health monitoring by providing feedback and suggestions within the user interface.
Additionally, TYPO3 should efficiently integrate with external tools, offer task automation, and use the built-in dashboard to enhance editors’ understanding of website health, trends, and content performance across multiple sites.
“We want to improve solution/use case communication and customer-oriented communication.”
Customers and end users should obtain better backend user experience through clear best practices and in-system support. This includes the creation and maintenance of several official solution-oriented cookbooks, how-tos, and overarching marketing and communication for use cases and business needs.
“We want to establish good Governance around product development, quality assurance, and cybersecurity.”
The TYPO3 Product Team can innovate more efficiently if all activities and other interrelated or interacting elements are managed as one system. The TYPO3 product development process should help the Product Team identify opportunities, create and validate concepts, and develop and deploy the best solutions. The process should include quality measurement KPIs, ideation, innovation mechanisms, and security and quality assurance by design.
“We want to make fact-based decisions, and provide facts — also to our community.”
Enhance decision-making processes by grounding them in factual data and a better understanding of the market and user dynamics.
This goal aims to optimize product development and market positioning for TYPO3. It underscores the commitment to making informed, data-driven decisions to ensure that technical and organizational strategies align with real-world usage and market demands.
“We want to be more interconnected.”
We aim to position TYPO3 as a highly connected and adaptable solution in the digital landscape by expanding TYPO3's integration capabilities and allow effortless connections with popular systems. This involves user-friendly integration processes, ensuring that TYPO3 can seamlessly interchange data with external systems, and improving the communication about such capabilities both internally and externally.
The efforts to establish official collaboration with external vendors should be strengthened. Official integrations with listings on vendors’ websites can enhance TYPO3's credibility and expand the Ecosystem.
“We want to make updates and maintenance easier.”
To deliver a high return on investment, TYPO3 should deliver customer value by offering long-term support and straightforward maintenance and updates. TYPO3 should promote the importance of keeping software up-to-date and secure, while also being accessible and less costly to maintain over time.
“We want to increase the end user’s success (lead generation/conversions/content delivery).”
TYPO3 should have clearly defined communication and feedback channels in order to build transparency and trust. Consistent storytelling and joint marketing efforts should be undertaken in order to leverage the increased visibility and reach. The Project needs to offer official and central marketing and sales support assets to help agencies succeed in selling and marketing TYPO3 CMS.
This goal also includes the definition, implementation, integration, and connection of success metrics as well as the establishment of official, centralized lead generation.
“We want to make the CMS more scalable.”
SMEs can profit from both scaling up and down, and thus spending their IT resources more efficiently.
The public sector needs high content availability and the ability to scale up on demand in response to increased request load. They also require efficient, distributed caches (CDN) and huge amounts of file resources (cloud storage).
TYPO3 should be refined for cloud hosting, incorporating a test chain to evaluate key functions, and ensuring horizontal scalability, e.g. the ability to scale down to zero. There is an opportunity in exploring push-based principles for frontend operations to align with modern cloud architectures and making TYPO3's performance in the cloud measurable.
TYPO3's compatibility with diverse cloud, on-premise and shared-hosting environments should be enhanced to optimize the operational efficiency. Different operational modes should be explored, including serverless models, standalone application servers, and asynchronous PHP solutions.
Stay tuned for updates, surveys, and community forums where you can actively contribute to shaping the next chapter of TYPO3.
Thank you for your continued support and enthusiasm. The TYPO3 CMS Product Strategy Group is eager to embark on this journey with you, and together, we will elevate TYPO3 to new heights.
As a now official TYPO3 Community group, the CMS Strategy Group will adhere to the general rules and provide quarterly reports on current updates for the entire ecosystem.
This vision, mission, and purpose statement was developed by the TYPO3 Association Board and representatives from the TYPO3 Company and the TYPO3 Core Team, with the help from external consultants.
Having a clear vision, mission, and purpose for the project means we can have clear visions, missions, and purposes for other fields of responsibility as well. Those will form the basis for strategic decisions.
This vision, mission, and purpose is ultimately an expression of where we see TYPO3 heading. On a very high and abstract level, you can view them as definitions of who we are, why we are here, and where we want to go. They are philosophical foundations that shape our decisions.
These are our thoughts and perspectives, and we hope publishing them will make it easier for you to tell us yours. Talking about such things is what shapes TYPO3’s farthest future today.
The vision, mission, and purpose for the TYPO3 Project are stated as single, short sentences. Each word carries a lot of meaning.
Some of that meaning is interpreted in the brief explanation following each sentence. We are building a Frequently Asked Questions section to further elaborate on how we interpret it. However, the sentences also stand by themself. The interpretations are not exhaustive, and should not restrict the interpretation.
The TYPO3 Project’s Vision, Mission, and Purpose should indeed be broad and give much freedom. The Product, Association, and Company will each have their own, separate and more restrictive visions, missions, and purposes.
Empower :ref:`* <vmp-faq-vision-question1>` to unlock their potential, creating opportunities through content.
We believe that every person can bring something unique to the table. Content is fundamental to empowering people today to share knowledge, unlock possibilities, and achieve their potential regardless of who they are, what they believe, or where they come from. Our people, software, and services will empower content for everyone.
Enable :ref:`freedom <vmp-faq-mission-question1>`, :ref:`interconnection <vmp-faq-mission-question2>`, and collaboration through sustainable, world-class, open content management software.
Our mission is to make a better world for everyone by building and maintaining sustainable, affordable, accessible, easy-to-use, open-source software, offering professional services, and creating an open and welcoming community.
:ref:`Equalize opportunities <vmp-faq-purpose-question1>` through Open Source.
Our purpose is to equalize opportunities by making our world-class open source software available to anyone, free to download and use. We offer our supporting services at :ref:`prices adjusted to local circumstances <vmp-faq-purpose-question2>. Our products strengthen collaboration, empower independent businesses, educational and government institutions, and civil society worldwide.
This is a catch-all or wildcard character. The TYPO3 project should empower through freedom, not restriction. The asterisk is a good symbol of that freedom. Feel free to replace it with any word you feel fits.
To “bring something to the table”, is an English idiom meaning to provide something of benefit. We believe every person is unique and that every person has something in them that can bring benefit to others. The TYPO3 project should empower every person to provide that benefit.
Yes, and on multiple levels. For example:
Merriam-Webster’s dictionary defines interconnection as “to connect with one another” or “to be or become mutually connected”. Here are three examples of how it can be interpreted:
This is one of these words that can mean a lot—and that’s intentional. Here are a couple of examples:
This is related to our purpose to “equalize opportunities”. Different regions, countries, and social strata can offer different financial opportunities. Because the TYPO3 Project should empower every person, we must also provide fair pricing that gives the same opportunities for similar effort. That could mean charging more for services in rich countries to offset a lower price for the same service elsewhere.
Social Media Guidelines for the TYPO3 Project
Authors: Naike Schulthess and Mathias Bolt Lesniak. Version: 2.0 (June 2017). Migrated to the current repository 19 November 2025.
1. Social Media
Social media is changing the way we work, offering a new model to engage with members, community, journalists, and the world in general. These are the official guidelines for participating in social media for the TYPO3 Project.
1.1 Official Profiles
The TYPO3 Association and the TYPO3 project manages official profiles on a number of social media platforms. Some teams and committees are also managing their own profiles. The Association Board keeps a list of official profiles. The creation of new official profiles should be discussed with the Association Board.
1.2 Private Profiles
You are encouraged to talk about TYPO3 and your work for the TYPO3 Association and TYPO3 project on your private social media profiles. While your private profiles and posts are not official TYPO3 communiques per se, you may still represent or be perceived to represent an official body or team.
2. Social Media Values
Your behavior has an impact on how TYPO3 and the TYPO3 Association are perceived. By upholding our values, you strengthen the organization and what we represent. The TYPO3 Association believes in the following values:
3. Social Media Use
3.1 What We Write About on Our Official Profiles
The official TYPO3 social media profiles are used for the following purposes:
3.2 What Not to Write on Official Profiles
The TYPO3 Project official social media profiles are not used for the following purposes:
If someone looks like they want to pick a fight, ignore that person. Discussions should take place on other platforms like telephone and email.
4. Responsibilities and Ownership
The TYPO3 Association owns the official social media profiles and decides on access and permissions. The TYPO3 Association is responsible for:
The responsibility for the tasks listed in chapter 3.1 is shared, but only a single person should be responsible for reacting to external comments and questions at any given time. This person is also responsible for delegating this task during times of absence.