<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>Official TYPO3 news</title>
        <description>Posts by author Martin Helmich</description>
        <language>en</language>
        <link>https://news.typo3.com/article/author/martin-helmich/blog.author.xml</link>
        <lastBuildDate>Fri, 24 Jul 2026 02:45:47 +0200</lastBuildDate>
        
    
    
        
<item><title>TYPO3 Association Board Meeting Protocol (8 July 2026)</title><link>https://news.typo3.com/article/typo3-association-board-meeting-protocol-8-july-2026</link><comments>https://news.typo3.com/article/typo3-association-board-meeting-protocol-8-july-2026#comments</comments><pubDate>Mon, 20 Jul 2026 05:30:00 +0200</pubDate><dc:creator>Martin Helmich</dc:creator><guid>https://news.typo3.com/article/typo3-association-board-meeting-protocol-8-july-2026</guid><description>The Board and BCC met for their regular meeting. Topics were a follow-up on membership exclusions, how AI-generated contributed code should be handled, and an update on the Conflict of Interest Matrix for board members.</description><enclosure
            length="12563"
            type="image/svg+xml"
            url="https://news.typo3.com/fileadmin/TYPO3_Stock/Governance/Board_Protocol.svg" /></item>


    
        
<item><title>TYPO3 Association Board Meeting Protocol (24 June 2026)</title><link>https://news.typo3.com/article/typo3-association-board-meeting-protocol-24-june-2026</link><comments>https://news.typo3.com/article/typo3-association-board-meeting-protocol-24-june-2026#comments</comments><pubDate>Wed, 24 Jun 2026 19:11:00 +0200</pubDate><dc:creator>Martin Helmich</dc:creator><guid>https://news.typo3.com/article/typo3-association-board-meeting-protocol-24-june-2026</guid><description>The Board discussed recent developments within the Core Team, the ongoing dialogue with the community, and membership-related processes. The Board reaffirmed its commitment to constructive exchange and reviewed next steps regarding outstanding membership fees.</description><enclosure
            length="12563"
            type="image/svg+xml"
            url="https://news.typo3.com/fileadmin/TYPO3_Stock/Governance/Board_Protocol.svg" /></item>


    
        
<item><title>TYPO3 Association Board Quarterly Summit Protocol (Q2/2026)</title><link>https://news.typo3.com/article/typo3-association-board-quarterly-summit-protocol-q2-2026</link><comments>https://news.typo3.com/article/typo3-association-board-quarterly-summit-protocol-q2-2026#comments</comments><pubDate>Wed, 10 Jun 2026 13:43:00 +0200</pubDate><dc:creator>Martin Helmich</dc:creator><guid>https://news.typo3.com/article/typo3-association-board-quarterly-summit-protocol-q2-2026</guid><description>At the Quarterly Summit of the Association, the Board planned for the coming month, redistributed roles and responsibilities and started the preparation for the 2027 General Assembly.</description><enclosure
            length="12563"
            type="image/svg+xml"
            url="https://news.typo3.com/fileadmin/TYPO3_Stock/Governance/Board_Protocol.svg" /></item>


    
        
<item><title>TYPO3 Association Board Meeting Protocol (27 May 2026)</title><link>https://news.typo3.com/article/typo3-association-board-meeting-protocol-27-may-2026</link><comments>https://news.typo3.com/article/typo3-association-board-meeting-protocol-27-may-2026#comments</comments><pubDate>Wed, 27 May 2026 12:00:00 +0200</pubDate><dc:creator>Martin Helmich</dc:creator><guid>https://news.typo3.com/article/typo3-association-board-meeting-protocol-27-may-2026</guid><description>Topics included international growth, security initiatives, and stronger community structures. The Board also reviewed the General Assembly protocol and measures to strengthen trust, transparency, and security across the TYPO3 ecosystem.</description><enclosure
            length="12563"
            type="image/svg+xml"
            url="https://news.typo3.com/fileadmin/TYPO3_Stock/Governance/Board_Protocol.svg" /></item>


    



    </channel>
</rss>
