fix: give specs a reportable Code of Conduct - #72
Merged
Conversation
Its CODE_OF_CONDUCT.md named no enforcement contact, leaving the sentence pointing at nobody, so a violation had nowhere to go. Its LICENSE named OSAPI as copyright holder rather than John Dewey, the holder every other repository names. Also archives require-go-library-examples and ticks the four Go library conversions, whose files, CONTRIBUTING structure, and README structure all verified against the requirements. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Thank you for contributing to this project! 😊🕹️ |
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
1 participant
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.
Archives
require-go-library-examples, ticks the four Go library conversions, and fixes two boilerplate violations that verifying them surfaced.The Code of Conduct could not be acted on
specs/CODE_OF_CONDUCT.mdwas the only one of seven that differed, and the difference was the enforcement contact. The sentence read:The address is simply absent, so the document told a reporter to contact nobody. The requirement says
CODE_OF_CONDUCT.mdSHALL name a working enforcement contact; this restoresjohn@dewey.ws, making all seven byte-identical.specs/LICENSEalso namedOSAPIas copyright holder. The requirement isJohn Deweyin every repository — the other six comply.Neither had a task.
specsis classified (Documentation) and therefore bound by the capability, but section 4 lists only the five product repositories. Added as task 4.7.Go library conversions, verified
Ticked 4.1–4.4 after checking each against the requirements rather than assuming:
contributing.mdanywhereCONTRIBUTING.mdopening and closing sections match the prescribed order exactlyExamplessection arrived with feat: add runnable examples gohai#158, and itsRelated Worksmoved aboveContributingAI_POLICY.mdbyte-identical across all seven; noLICENSEyear expressed as a rangeOn 4.4's noted open question — whether
osapi-orchestratorshould be its own type — the classification requirement records it as a Go library, and the README requirement explicitly permits subject-matter sections beforeContributing, which is whatTargetingandOperationsare. The design.md note is stale relative to the requirement.Archive
require-go-library-examplescloses 7/7, adding Runnable examples togo-library-standards(now 7 requirements). Ten changes archived; three in flight.🤖 Generated with Claude Code