Skip to content

Commit 17ee4ae

Browse files
authored
[docs] Update expected cadence of when Transparency reports are published (#142026)
1 parent 821cd6a commit 17ee4ae

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

llvm/docs/ResponseGuide.rst

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -283,9 +283,7 @@ Transparency Reports
283283
Lack of transparency in the outcomes of our Code of Conduct incidents leaves
284284
our community without an understanding of how or if the organizers worked to
285285
resolve incidents. The CoC committee should aim to publish transparency
286-
reports, if reports are received, after major events (such as the LLVM
287-
Developers' meetings) and on the following dates: Jan 15, April 15, July 15,
288-
Oct 15.
286+
reports, if reports are received, at least 2 times in a calendar year.
289287

290288
A transparency report consists of 2 parts:
291289

0 commit comments

Comments
 (0)