Skip to content

docs: propose public repository standard v0.1 and redisctl adoption record #1181

Description

@joshrotenberg

Scope

Prepare a versioned candidate public-repository checklist and redisctl adoption record in the existing developer documentation. Redisctl is the initial reference for redisctl, redis-cloud-rs, redis-enterprise-rs and redis-database-mcp-rs, not an approved organization-wide policy.

Acceptance

  • Every common checklist item has an observable outcome and evidence requirement; product-specific profiles remain distinct.
  • Redisctl record identifies audited source revision, observation date, applicable profiles, supported/distributed channels, required versus advisory checks and honest missing/partial/unknown evidence.
  • Record the accepted targets: required meaningful CI, independent agent review and Josh Rotenberg's merge decision; GitHub private vulnerability reporting with a named human triage owner.
  • Actual settings adoption, the named security triage person and permanent standard ownership/home stay visibly unresolved. Do not invent ownership or response promises or change rulesets/settings in this documentation slice.
  • Strict MkDocs and focused Markdown lint pass; independent editorial review records the pushed revision and disposition.

Boundaries

Documentation/navigation only. No workflow, ruleset/security settings, ownership assignment, cross-repository rollout, runtime, merge, release or publication changes.
Leaves #628, #1088, #1087 and #1085 open; this documentation slice does not implement their broader testing, API, release or support-matrix work.
Pilot #1176, Unicode fix #1180 and release PR #1178 remain separate.

Source inputs: October 6 candidate standard v0.1, adoption packet and dated inventory prepared in the project-manager task. These are proposals/evidence, not authority to enact policy.

Activity

  1. joshrotenberg commented on Oct 6, 2026

    @joshrotenberg
    CollaboratorAuthor

    Documentation and independent editorial-review checkpoint is complete in draft #1182 at 60c739d0fb3c61f418175de52916957fd2ecb0fe: no actionable review findings; strict local documentation/lint/fmt/Clippy pass; all 15 current-head checks pass with 7 expected skips. Both accepted targets are recorded. Named triage owner, permanent standard owner/home, responsibility assignments and exact settings adoption remain separate decisions. PR remains draft for policy discussion; issue stays open. No settings, CI-gate implementation, merge or release action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions