Repository navigation
Support intake stays mailto: policy line about automated triage, subject convention pinned (#635) - #738
Merged
Conversation
…and the subject convention pinned (#635) Dave chose option A on #635: the mailto intake stays, nothing is collected server-side, and an in-house multi-product support system (its own repo, built on house-mail) reads the mailbox, flags items for his review and sends the disposition itself. MegaPDF's part is the convention that system consumes and the policy line disclosing it. - privacy/ section 4: a paragraph (id="support-triage") saying support mail is read and answered by an automated system, with a person deciding. Replaces "an email to one person" with "a private email to us", which the new paragraph would contradict. Effective date bumped, per the file's history. Also fixes the stale "section 12" in a comment (the ordering rule is 11). - deploy.py check_support(): refuses a --support deploy whose policy lacks the support-triage paragraph, or whose page no longer builds the "MegaPDF support <ref>" subject the Outlook rule and the support system key on. - check-support-page.js: pins the subject for every platform and kind (15 combinations), the bare subject with nothing chosen, and the reference matching the body's first line. - website/README.md: "The support mailbox" section: the subject and body convention, the Outlook rule, and a placeholder for the support system's repo. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gy1pTSRfTv5rzMd8Pt6FRP
Owner
Author
|
Decisions on the three open points are on #635 (coordinator comment of 2026-10-22 08:55 EDT): the support page's two paragraphs change in this PR, one sentence is added to the support-triage paragraph, and unflagged mail belongs to the support-system repo. After that edit and a green pull_request run on the new head, this merges. |
This was referenced Oct 22, 2026
…heck (#635) The support page said "One person reads these messages", "no ticket robot" and "an email to one person", which contradict the privacy policy paragraph that discloses sorting by software (id="support-triage"). Per the coordinator's decisions of 2026-10-22 08:55 EDT on #635: - the page's intro paragraph and the privacy note are rewritten in the issue's words; "Write in English or in French" and the GitHub sentence are kept - the support-triage paragraph gains the sentence promising that the policy will name any outside service before software uses one to read a message - check-support-page.js pins that the page no longer contains "ticket robot" or "to one person" (fails on the old page, passes on the new) - website/README.md records the naming obligation for the support-system repo The website is English only, so there are no localised strings. Nothing is deployed from here; the page and policy go up together in one --support --privacy run. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gy1pTSRfTv5rzMd8Pt6FRP
This was referenced Oct 24, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
#635, option A as Dave decided it (2026-10-21 09:45 and 09:48-09:49 EDT): the mailto intake stays, nothing is collected server-side, and an in-house multi-product support system (its own repo, built on house-mail) will read the mailbox, flag items for Dave and send the disposition itself. MegaPDF's part is the convention that system consumes and the policy line that discloses it.
id="support-triage": support mail is read and answered by an automated system, with a person at Electric RV deciding what is done. "An email to one person" became "a private email to us" because the new paragraph would contradict it. Effective date bumped to 21 October 2026 (the file's own precedent is the commit date; Dave adjusts it at deploy if later). Stale "section 12" in a comment fixed (the ordering rule is section 11).website/deploy.py:--supportnow refuses unless the policy carriessupport-triage, and refuses a page that no longer builds the"MegaPDF support " + reference()subject.website/check-support-page.js: pins the subject for all 15 platform x kind choices, the bare subject with nothing chosen, and the reference matching the body's first line.website/README.md: "The support mailbox" section: subject/body convention, the Outlook rule, a placeholder for the support system's repo link.No app code, no strings in the apps, no new French: nothing for
FR-REVIEW. The website is English only.Verified (locally)
node website/check-support-page.js(jsdom): all checks pass, including the four new ones. Mutation: changing the page's Android label to "Android phone" makes the new check fail on exactly that.python3 website/deploy.py --dry-run --support --privacy: passes. Refuses with the new messages whenid="support-triage"is removed from the policy, and when the subject prefix is changed in the page (both tried, then restored).python3 tools/qa/check-matrix.py --check: passes (website tests are outside the matrix globs).Not done, and why
🤖 Generated with Claude Code
https://claude.ai/code/session_01Gy1pTSRfTv5rzMd8Pt6FRP