Repository navigation
Updated version of the conflict of interest policy according to the decision paper 2026-08-17-Board-Decision-Conflict-of-Interest-Matrix-2026 - #57
Conversation
rfoucard
commented
Sep 24, 2026
- simplify the matrix so that individuals can more easily determine whether a conflict of interest is likely to exist or can reasonably be excluded.
- adopts a risk-based approach. Instead of primarily considering the accumulation of roles or responsibilities
- include a clear process for conflict of interest report with contact information and a Compliance Review Panel members pool
- add Units leading position in the Matrix to mitigate possible conflict of interest
|
✅ This pull request is classified as It requires 2 approvals by representatives of the document owner (TYPO3 Association Board if not stated otherwise). |
|
This pull request is classified as a formal change. This means it needs an formally documented decision by the TYPO3 Association Board, which must be documented in a new file under ✅ New decision record found at |
dkd-dobberkau
left a comment
There was a problem hiding this comment.
Thanks for the thorough update — the new mapping matrix and the detailed process chapter are a clear improvement over the old cross-table.
A few formatting issues that will produce Sphinx warnings or render incorrectly. All of them are in the newly added parts; nothing about the policy content itself.
| * A **perceived** conflict of interest exists when the public may believe that an individual's personal interests could influence the performance of his or her official duties - whether or not this is actually the case. | ||
|
|
||
| Code of Conduct | ||
| Duties and Requirements |
There was a problem hiding this comment.
The underline from the old heading was kept: Duties and Requirements is 23 characters, the === underline below is only 15. Sphinx will emit Title underline too short.
| | service providers(5) | by by-laws | by by-laws | | | | | | ||
| +-----------------------------+------------------+------------------+------------------------------------------+------------------------------------------+------------------------------------------+------------------------------------------+ | ||
|
|
||
| (1) References to a person's interests include interests held by their close relatives and persons with whom they have a close personal relationship where those interests could reasonably be perceived as influencing the person's judgment. |
There was a problem hiding this comment.
Footnotes (1)–(5) each end in trailing tab characters — looks like a copy/paste out of a spreadsheet. Worth stripping before merge.
| Reporting a Conflict of Interest | ||
| ===================================== | ||
|
|
||
| Any TYPO3 Association member, TYPO3 GmbH employee, or provider working for the TYPO3 Association or TYPO3 GmbH who becomes aware of a potential conflict of interest may report it to the TYPO3 Association Compliance Officer using the dedicated form available on **this page**. The report may concern the reporting person's own situation or a situation involving another person. |
There was a problem hiding this comment.
**this page** is still a placeholder without a link. Where should the reporting form point to?
| ------------------------------ | ||
|
|
||
| - The Compliance Officer sends an email to all persons listed in the Conflict of Interest register to ask them either to validate the declared situation, or to inform about any new situation. | ||
| - The recipient have 2 weeks to answer about their situation |
There was a problem hiding this comment.
reST needs a blank line between a list item and a nested sub-list, otherwise docutils reports Unexpected indentation and the sub-items do not render as a nested list.
Same pattern on lines 174 and 179.
Also: "The recipient have 2 weeks" → has.
| - If the situation hasn’t changed, the Board member responsible for the conflicts of interest documentation adds the last update date of the conflict. | ||
| - If the situation has changed, the conflict goes through the next steps like a new conflict. | ||
|
|
||
| Compliance Review Panel members pool (1 month after each GA) |
There was a problem hiding this comment.
Underline too short: heading is 60 characters, the --- underline is 36.
| - The Board votes (quorum) the strategies they want to apply | ||
| - The Board must record the decision in the meeting protocol | ||
|
|
||
| Monitor (One year after the strategies implementation) |
There was a problem hiding this comment.
Underline too short here as well: heading is 54 characters, underline is 33.
Unrelated, while in the area — a few subject/verb agreements in this chapter: "The Case Officer prepare" (line 173) and "The Compliance review panel vote" (line 178) should be prepares / votes.
dkd-dobberkau
left a comment
There was a problem hiding this comment.
All six points from my previous review are addressed in ee3135f — thanks for the quick turnaround. I re-checked the file with docutils: no warnings left, and the heading underlines, the stray tabs in the footnotes, the nested list indentation and the subject/verb agreements are all fixed. The reporting path now points to compliance@typo3.org instead of the placeholder.
Approving. Two non-blocking notes on the decision record, Documentation/Association/Board/Decisions/2026/08-17-ConflictOfInterest2026Update.rst, which I had not looked at last time:
- The title overline and underline are 32 characters, the title itself is 54 — docutils reports Title overline too short. The build still passes, it is only a warning.
:navigation-title: 09-17 Conflict of Interest Policy 2026 Updateshould probably read08-17, matching the filename and the voting date. The sibling decision records follow theMM-DDconvention.
Feel free to fold these into a follow-up if you prefer not to invalidate approvals again.
|
Note for whoever looks at the checks here: the red The workflow counted my approval correctly ( So the actual state is: 1 of 2 approvals. @martin-helmich, your earlier reviews were dismissed by the new commits — a re-approval from you is what is missing. |
af748f5
into
TYPO3-Documentation:main