Skip to content

Updated version of the conflict of interest policy according to the decision paper 2026-08-17-Board-Decision-Conflict-of-Interest-Matrix-2026 - #57

Merged
martin-helmich merged 20 commits into
TYPO3-Documentation:mainfrom
rfoucard:main
Sep 28, 2026

Conversation

@rfoucard

Copy link
Copy Markdown
Collaborator
  • 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

@rfoucard
rfoucard requested a review from a team as a code owner September 24, 2026 09:43
@github-actions

github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

✅ This pull request is classified as type: formal change.

It requires 2 approvals by representatives of the document owner (TYPO3 Association Board if not stated otherwise).

@rfoucard rfoucard added type: formal change Changes to the meaning of the text. Require a formal decision by the owner. formal decision present A formal decision on whether this change can be implemented was made and documented. labels Sep 24, 2026
@github-actions

github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

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 Documentation/Association/Board/Decisions/.

✅ New decision record found at Documentation/Association/Board/Decisions/2026/08-17-ConflictOfInterest2026Update.rst.

@github-actions github-actions Bot added pending formal decision Awaiting a formal decision on whether or not the change can be implemented. and removed formal decision present A formal decision on whether this change can be implemented was made and documented. labels Sep 24, 2026
@github-actions github-actions Bot added formal decision present A formal decision on whether this change can be implemented was made and documented. and removed pending formal decision Awaiting a formal decision on whether or not the change can be implemented. labels Sep 24, 2026
@github-actions github-actions Bot added pending formal decision Awaiting a formal decision on whether or not the change can be implemented. and removed formal decision present A formal decision on whether this change can be implemented was made and documented. labels Sep 24, 2026
@github-actions github-actions Bot added formal decision present A formal decision on whether this change can be implemented was made and documented. and removed pending formal decision Awaiting a formal decision on whether or not the change can be implemented. labels Sep 24, 2026
martin-helmich
martin-helmich previously approved these changes Sep 24, 2026
@TYPO3-Documentation TYPO3-Documentation deleted a comment from github-actions Bot Sep 24, 2026
@martin-helmich
martin-helmich requested a review from a team September 24, 2026 12:19
martin-helmich
martin-helmich previously approved these changes Sep 28, 2026

@dkd-dobberkau dkd-dobberkau left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch, done

| 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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Footnotes (1)–(5) each end in trailing tab characters — looks like a copy/paste out of a spreadsheet. Worth stripping before merge.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

**this page** is still a placeholder without a link. Where should the reporting form point to?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

------------------------------

- 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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

- 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)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Underline too short: heading is 60 characters, the --- underline is 36.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

- 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)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@dkd-dobberkau dkd-dobberkau left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 Update should probably read 08-17, matching the filename and the voting date. The sibling decision records follow the MM-DD convention.

Feel free to fold these into a follow-up if you prefer not to invalidate approvals again.

@dkd-dobberkau

Copy link
Copy Markdown
Contributor

Note for whoever looks at the checks here: the red Required approvals — 0 / 2 is stale and should not be read as blocking.

The workflow counted my approval correctly (1 / 2 approvals in the job log), but could not publish the status check — Resource not accessible by integration, the known fork-PR issue in #56. The badge will only refresh on the next pull_request_target event, i.e. a push or a label change.

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.

@martin-helmich
martin-helmich merged commit af748f5 into TYPO3-Documentation:main Sep 28, 2026
5 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

formal decision present A formal decision on whether this change can be implemented was made and documented. type: formal change Changes to the meaning of the text. Require a formal decision by the owner.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants