Skip to content

feat: link the anonymous Code of Conduct report form - #16

Merged
thevvalverde merged 4 commits into
mainfrom
feat/anonymous-report-form
Sep 11, 2026
Merged

thevvalverde merged 4 commits into
mainfrom
feat/anonymous-report-form

Conversation

@thevvalverde

Copy link
Copy Markdown
Collaborator

Why

CODE_OF_CONDUCT.md promised an anonymous report form "linked from the conference website and app", but the link did not exist anywhere on the site. The same sentence pointed readers to the response guide "for what this covers and its limits" — and the response guide said nothing about anonymous reports. Both halves of that promise are now real.

The form: https://forms.gle/v6De4jLPm1XZ64SN9

Commits

1. feat: link the anonymous report form

Adds the link in the three places people actually look:

  • The Code of Conduct's "Where to report incidents" list, replacing the vague wording.
  • The contact page, beside conduct@djangocon.eu.
  • The response guide, so a volunteer can point someone to it on the spot.

Also adds an "Anonymous reports" section to the CARE team guide covering what an anonymous report can and cannot lead to — no follow-up questions, no outcome notification, and limits on resolutions that need a testable account or the reporter's consent. It closes with the case that comes up most in practice: someone willing to be contacted but not willing to have their name shared with the other party does not need the anonymous channel, and the normal process preserves every resolution option.

No navigation change — submenu URLs must map to folders under djangocon/content/, and an external form is not a content page.

2. fix: unescape target="_blank"

Found while verifying commit 1 renders. The Markdown carried target="\_blank" inside raw HTML anchors and the backslash survived rendering, so the browser saw a window named \_blank and opened these links in the same tab. Six anchors across three files, including the Slack link two lines above the new one in the Code of Conduct.

The sponsorship brochure keeps its backslash on purpose: it uses attr_list syntax ({:target="\_blank"}), where Markdown does process the escape and the output is already correct. Verified both forms through the renderer before changing anything.

3. docs: set the transparency report deadline

Replaces the [X weeks — organizers to set] placeholder with 4 weeks.

Verification

Rendered every content file through the real loader (render_markdown_file), the same path the views use:

  • 24 target attributes site-wide, all _blank, no backslash leaks.
  • All 4 form links present and well-formed.
  • Section ordering and meta parsing unchanged for every affected directory.

pytest lives only in the Docker image, so the suite was not run here; the one existing test (tests/test_seo.py) does not cover content markdown. Worth a just pytest on CI.

🤖 Generated with Claude Code

https://claude.ai/code/session_011i8AYdEkHBURzkFmyGpQmy

thevvalverde and others added 4 commits September 11, 2026 09:40
The Code of Conduct promised an anonymous report form "linked from the
conference website and app", but no such link existed anywhere on the
site, and the response guide it pointed to for "what this covers and its
limits" said nothing about anonymous reports.

Link the form from the three places people look for it, and document the
limits the Code of Conduct already promised were written down:

- The Code of Conduct's "Where to report incidents" list.
- The contact page, next to conduct@djangocon.eu.
- The response guide, for volunteers who need to point someone to it.

The CARE team section now covers what an anonymous report can and cannot
lead to, and notes that a reporter who is willing to be contacted but
does not want their name shared with the other party should go through
the normal process, which preserves every resolution option.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011i8AYdEkHBURzkFmyGpQmy
The Markdown source carried target="\_blank" inside raw HTML anchors, and
the backslash survived rendering: the browser received target="\_blank"
and read it as a window named \_blank, so these links opened in the same
tab instead of a new one.

Both spellings were in use across the content, so this aligns the raw
HTML anchors with the already-correct ones in information/venue and
talks/cfp. The sponsorship brochure keeps its backslash: it uses
attr_list syntax, where Markdown does process the escape and the
rendered output is already target="_blank".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011i8AYdEkHBURzkFmyGpQmy
Replaces the "[X weeks — organizers to set]" placeholder in the response
guide with a concrete deadline.
@thevvalverde
thevvalverde merged commit 14f4557 into main Sep 11, 2026
3 checks passed
@thevvalverde
thevvalverde deleted the feat/anonymous-report-form branch September 11, 2026 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant