growth: contributor spotlight — monthly contributor recognition

[masukai]

Summary

Add a Contributors section to the README and set up a monthly recognition flow.

What to do

Step 1: Add Contributors section to README

Add an auto-generated contributors grid to README.md using all-contributors or a simple GitHub avatar grid.

Example using GitHub API:
```markdown

Contributors

\`\`\`

Step 2: Document the spotlight process

Add a section to CONTRIBUTING.md explaining that active contributors may be highlighted in monthly X posts.

Acceptance criteria

• README has a Contributors section with auto-generated avatars
• CONTRIBUTING.md mentions contributor recognition

Difficulty

⭐⭐ Easy — README + CONTRIBUTING.md edits, < 1 hour

Reference

• contrib.rocks — auto-generates contributor grid
• all-contributors — more detailed contributor table

[masukai]

Scope update — recommend all-contributors as the primary approach

With GOVERNANCE.md (#310) introducing a contributor ladder and recognition philosophy, this issue gains a clearer purpose: make non-code contributions visible too, not just commit history.

Recommended approach: all-contributors bot (over the simpler contrib.rocks image)

Why all-contributors fits better:

• Recognizes 33 contribution types (code, docs, design, review, ideas, translation, talks, blog posts, etc.) — directly supports the "any contribution counts" message in GOVERNANCE.md
• Comment-driven workflow (@all-contributors please add @user for code, doc) makes recognition a community ritual, not a maintainer chore
• Auto-opens PRs to update README — every recognition becomes a visible, celebratory event
• Complements the monthly Contributor Spotlight (this issue) by providing the always-on baseline list

Updated acceptance criteria

• Install all-contributors GitHub App on the repo
• Add .all-contributorsrc config + Contributors section placeholder in README.md
• Bulk-import existing contributors (script available in all-contributors CLI)
• Document the recognition workflow in CONTRIBUTING.md (one paragraph + link)
• (Optional, nice-to-have) Mirror Contributors section in README.ja.md

Difficulty

⭐⭐ — config + one-time bulk import. ~1–2 hours.

Anyone interested in picking this up after #310 merges? 🙌

[Muawiya-contact]

Hi @masukai, since #310 is merged, I'd like to take this on!

I'll be setting up the all-contributors bot to ensure we capture all 33 contribution types
as mentioned in the updated scope. My plan is to:

1. Initialize .all-contributorsrc.
2. Perform a bulk-import of existing contributors via the CLI.
3. Update the README.md and CONTRIBUTING.md with the new workflow.

I'll link a PR here as soon as the configuration is ready for review.

[masukai]

Thanks @Muawiya-contact! Go for it 🚀

Your plan looks solid. A few things to keep in mind:

• Bulk import accuracy: The CLI picks up commit authors, but non-code contributors (issue reporters, reviewers) need manual @all-contributors please add calls. Don't worry about being exhaustive in the first PR — we can add people incrementally.
• README.ja.md: Let's skip the Japanese README in the first PR. I'll handle the sync separately.
• Config: Please set contributorsPerLine to 7 (default) in .all-contributorsrc — keeps it clean as we grow.
• GitHub App install: I'll install the all-contributors app on the org before your PR. Ping me when you're ready.

[Muawiya-contact]

Proposed Implementation Plan

Hi @masukai,

Following up on our last sync, here is the step-by-step approach I’ll be taking to implement the all-contributors workflow. I've kept it focused on the core requirements we discussed:

1. Project Initialization

I’ll start by initializing the CLI in the root directory.

• Tooling: Using all-contributors-cli.
• Configuration: I will set contributorsPerLine to 7 in the .all-contributorsrc file to ensure the README remains clean as the community grows.

2. Base Contributor Sync

To ensure we don't lose our existing history:

• I'll run a bulk import to capture all current code contributors from the Git history.
• I will manually add any prominent non-code contributors I can identify from recent issues/discussions.
• I'll then run the generate command to populate the initial grid in the Contributors section of README.md.

3. Documentation Update

I'll add a "Recognition" section to CONTRIBUTING.md that explains:

• How the bot works.
• The command syntax: @all-contributors please add @username for <contribution-type>.
• A link to the contribution type legend so people know they can be recognized for docs, ideas, reviews, etc.

4. Final Handoff

Once the PR is ready:

• I'll skip README.ja.md as requested.
• I'll ping you here to confirm the GitHub App is installed so we can test the bot's automated PR generation on the first live call.

I'll have the PR linked here shortly! 🚀

[masukai]

Thanks for the detailed plan @Muawiya-contact — this looks exactly right 🙌

GitHub App: installed ✅ I've installed all-contributors on the drt repo (scoped to this repo only, for least-privilege reasons). The bot should respond to @all-contributors commands now.

Your plan covers everything we discussed:

• contributorsPerLine: 7 ✅
• Bulk import + manual additions for non-code contributors ✅
• Recognition section in CONTRIBUTING.md with command syntax + type legend ✅
• Skip README.ja.md (I'll sync later) ✅

One small addition to consider: since the bot will auto-open a PR every time someone is recognized, please add a note in CONTRIBUTING.md that these auto-generated PRs are safe to merge without full review — just CI pass + visual check of the README grid. Otherwise we'll create unnecessary review burden on ourselves.

Ready whenever you are — ping me once the PR is up! 🚀