book: Std pages, network and security #594
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#599 book: retire the human pages of docs/
torbscript/language
#585 docs(book): a book for people, and the site built from it
torbscript/language
Reference
torbscript/language#594
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Slice of the epic #582. Starts after #585 (the concept, the vertical slice and the book gates) is merged.
Scope
Write one hand-written page in
book/std/per module:network,ip,dns,http,web,tls,digest,cipher,signature. Each replacesdocs/standard-library/<module>.md.Acceptance criteria
pageand is written asbook/CONCEPT.md, "How a page is written", says: the first paragraph says what the page covers, headings name ideas, prose first, no history, no internal references, no Related/Next sectionstrb runandtrb errorblock has itsoutputblock with the real output;torb docs check book,torb docs index --check bookandtorb docs site book --checkpass in CIbook/CONCEPT.mdthat the area touches are shown, not just nameddocs/this slice replaces are deleted in the same PR, unless a skill is still built from them (then they stay, unpublished, and the PR says which)package: std/<module>), so the site links the generated API reference oftorb doc stdtrb checkblocks with a sentence saying what they print; nothing reaches the internet in CIChildren
[loop:torbscript] intake: in scope (book std pages, slice of epic #582; dependency #585 is merged), no duplicate, no design-record collision, no seed impact. Next: refine (nine module pages, about 110 KB of old material, are too much for one PR).
[loop:torbscript] release refine: split into #664 (network, ip), #665 (dns, web), #666 (http), #667 (tls), #668 (digest, cipher), #669 (signature), each with the criteria of this issue and its own
Replaces in docs/list. All carryloop, none isready(made ready one after the other, CI is congested).[loop:torbscript] next: waiting (children #664 to #669)
[loop:torbscript] wait until 2026-10-30T09:00Z: children are filed, not ready; they are made ready as PR slots free up.
[loop:torbscript] wait until 2026-10-30T12:00Z: children #664 to #669 are not ready yet; the worker slots are full, they become ready as slots free up.
next: waiting (children #664 to #669) until 2026-10-30T12:00Z