You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/09/27 14:35:24 UTC

[PR] feat(contributor-growth): community signals with a separate indicator, and contract:chat [magpie]

potiuk opened a new pull request, #1425:
URL: https://github.com/apache/magpie/pull/1425

   Stacked on the PR from `contributor-growth/3-calibrate` (part 3); the whole stack starts at #1417. Part 4 of 5.
   
   ## Summary
   
   - Step 3 of `contributor-nomination` and `contributor-to-committer` now **collects** community evidence instead of only asking the nominator (`nomination/community-signals.md`): dev/users-list presence and release testing, chat answers, GitHub Discussions answers, and posts about the project on accounts the contributor linked from their own GitHub profile. No open web search for a person.
   - Identities count only when confirmed by a commit email, the people directory, a link from the contributor's own GitHub profile, or the maintainer; a chat profile that merely names the handle is that account's own claim and is listed as a *possible match, not used*. Items are classified constructive / neutral / unconstructive — **reasoned criticism is constructive**, disagreement alone never unconstructive. The classification and the community indicator never change counts, thresholds or the band; the confirmed dev-list count is an activity metric (`mailing_list_posts`), and any confirmed collected row counts as an off-GitHub signal.
   - New `contract:chat` (read-only, public channels only) with a Slack adapter over the Slack MCP; Discord is an extension point (#1421).
   - Separate commit: `contributor-to-committer` Step 4 now states that the off-GitHub signal is always mandatory. The step-4 injection eval failed on every run on `main` because an absent off-GitHub signal was read as "undeclared → advisory → MET".
   
   ## Type of change
   
   - [x] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
   - [x] Tool / bridge contract (`tools/<system>/*.md`)
   - [x] CI / dev loop (`prek`, workflows, validators) — `contract:chat` in the validator and the vendor-neutrality policy
   
   ## Test plan
   
   - [x] `prek run --all-files` passes
   - [x] `contributor-nomination`: new cases — unconfirmed identity not used, reasoned criticism constructive, injection in a chat message, a chat profile's own claim not treated as identity
   - [x] `contributor-to-committer`: 21/21 (step-4 case 5 fails 3/3 on `main`; passes after the Step 4 fix; new case: collected rows satisfy the off-GitHub signal)
   - [x] validator and vendor-neutrality pytest green
   
   ## RFC-AI-0004 compliance
   
   - [x] **Write-access discipline** — the chat contract has no write verb; the adapter lists the Slack tools it never calls
   - [x] **Vendor neutrality** — chat behind a contract; the scorer honestly reports it single-vendor until Discord lands
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(contributor-growth): community signals with a separate indicator, and contract:chat [magpie]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #1425:
URL: https://github.com/apache/magpie/pull/1425


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org