Update docs site for ATR Beta - #94
Conversation
Added information about volunteer-led tools under development, including a Maven plugin and a Responsible AI service.
This document outlines the design for the Apache Trusted Releases platform, detailing automation of the release process, community involvement, and infrastructure requirements.
Updated the Trusted Releases documentation to include new endpoints, committee configuration details, and project/user settings. Enhanced sections on automation and community involvement.
Added steps for the release process including Compose, Vote, and Finish phases.
Added a section about the three phases of a release.
Updated links and added contribution information to the discussion section.
Updated the Apache Trusted Releases platform documentation to clarify project roles, goals, and configurations. Improved formatting and consistency in the text.
Updated content for trusted releases documentation, including changes to endpoints, repositories, and project settings.
Updated the description of the Apache Trusted Releases platform and added details about the Release Candidate phases, including methods for starting a release and artifact upload processes.
Removed outdated sections on release catalog and lifecycle phases.
Clarify voting phase details and update release announcement process.
Add table of contents to trusted releases documentation
Removed the old table of contents and added a new one.
Removed unnecessary hyphens from the list of websites and repositories.
Clarified descriptions for tooling repositories.
Corrected punctuation and formatting issues in the trusted releases documentation.
Updated the title and clarified the description of the ASF Tooling team.
Expanded FAQ section to detail how ATR mitigates various Supply Chain attack scenarios.
Added introduction link and features discussion for ATR.
cottage14
left a comment
cottage14
left a comment
There was a problem hiding this comment.
Minor text change proposals:
atr-design-doc.md
line 4: change 'the' to 'its'
line 16: I think this line should explain how PMCs benefit, or be removed
lines 21-28: so much bold text can make the material harder to read, not easier. Maybe only bold-face an acronym on its first reference
line 39: add comma after 'management'
line 41: change 'tracking' to 'track' to match the verb forms in the rest of this list
line 71: I believe 'runbook' is a single word, not two
index.md
"To report a new vulnerability you have disckovered..." does not need 'new'
supply-chain.md
new line 8: 'automated' shouldbe 'Automated'
new line 13: does not need 'to' after consumers
team.md
line 6: 'consist of' is awkward. How about 'We include both paid staff and volunteers'?
trusted-releases.md
line 8: comma after 'dynamic'
line 68: change 'branch' to 'branches'
line 73: should 'yaml' have a '.' in front of it: '.yaml'?
line 78: need a comma after 'artifacts'
4 participants
No description provided.