Skip to content

docs: update team management and contributor tracking documentation#318

Open
MohamedFazil1406 wants to merge 1 commit into
OpenSource-Communities:mainfrom
MohamedFazil1406:patch-2
Open

docs: update team management and contributor tracking documentation#318
MohamedFazil1406 wants to merge 1 commit into
OpenSource-Communities:mainfrom
MohamedFazil1406:patch-2

Conversation

@MohamedFazil1406

@MohamedFazil1406 MohamedFazil1406 commented Jun 25, 2026

Copy link
Copy Markdown

Description

This PR replaces deprecated OpenSauced references in the maintainer documentation with GitHub-native alternatives.

Changes made

  • Replaced OpenSauced Repository Insights and Contributor Insights references with GitHub Insights.
  • Updated the "Identify New Talents" section to recommend GitHub Insights, Pull Requests, Issues, Discussions, and Contributor.info.
  • Removed deprecated OpenSauced workflows and instructions that are no longer supported.
  • Preserved the educational guidance for identifying and nurturing potential maintainers using currently available tools.

Related Issues

Fixes #272

Mobile & Desktop Screenshots/Recordings

Documentation only. No UI changes.

Steps to QA

  1. Open docs/becoming-a-maintainer/your-team.md.
  2. Verify that deprecated OpenSauced Repository Insight and Contributor Insight instructions have been removed.
  3. Confirm the documentation recommends GitHub Insights, GitHub Teams, GitHub Actions, and Contributor.info where appropriate.
  4. Open docs/becoming-a-maintainer/building-community.md.
  5. Verify the "Identify New Talents" section references GitHub-native tools instead of OpenSauced features.
  6. Ensure all removed OpenSauced references have been replaced with accurate, working alternatives.

Updated references from OpenSauced to GitHub for identifying new talents and reviewing contributor activity. Revised sections on utilizing GitHub's built-in tools and insights for community building.
@netlify

netlify Bot commented Jun 25, 2026

Copy link
Copy Markdown

Deploy Preview for learn-open-source ready!

Name Link
🔨 Latest commit 59c7411
🔍 Latest deploy log https://app.netlify.com/projects/learn-open-source/deploys/6a3cdf8ffbc19c000818dc17
😎 Deploy Preview https://deploy-preview-318--learn-open-source.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Compliance Checks Passed!

@MohamedFazil1406 MohamedFazil1406 changed the title Revise community building guidance to use GitHub tools update team management and contributor tracking documentation Jun 25, 2026
@MohamedFazil1406 MohamedFazil1406 changed the title update team management and contributor tracking documentation docs: update team management and contributor tracking documentation Jun 25, 2026
@MohamedFazil1406

Copy link
Copy Markdown
Author

Hi! I've updated the PR and fixed the issues. Could you please review it when you have time? Thank you!

@adiati98 adiati98 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MohamedFazil1406 thanks for your PR! ✨

It's a good start! However, can you please read the issue carefully and see what the requirements needed to update below pages?

We also have some screenshots and screen recordings that need to be updated or removed.

You need to explore and play around with GitHub and other tools mentioned in the issue yourself to understand about them so you can update these pages and validate the content.

#### 2. Using Contributor Insights

After identifying potential new talents for your projects, you can select and add them to the list of a new or existing Contributor Insights Page. This feature enables you to monitor and analyze your contributors' activity levels and contributions more deeply, such as tracking the number of commits and pull requests they have made. You can read more about Contributor Insights for maintainers and how to create one on [OpenSauced Docs](https://opensauced.pizza/docs/maintainers/maintainers-guide-to-open-sauced/#contributor-insights-connecting-with-contributors).
After identifying promising contributors within your repository, you can review their broader open source activity using **Contributor.info**. This provides additional context about their public contributions across repositories and can complement GitHub's native repository insights when evaluating potential maintainers or long-term collaborators.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The contributor.info that mentioned in the issue is this: https://contributor.info/

Then explain how this tool works and why it's useful to monitor and analize contributors activity or repo health.

#### 1. Using GitHub Repository Insights

You can list the projects you maintain on a Repository Insights Page. This feature allows you to monitor your projects' activity and identify contributors who actively contribute to and impact them.
GitHub's **Insights → Contributors** and **Insights → Pulse** pages provide an overview of repository activity and contributor participation. Reviewing pull requests, issues, and discussions can help you identify contributors who consistently submit high-quality work, collaborate effectively, and remain active over time.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the last sentence because it's a manual labor. As the title stated "Identify New Talents with GitHub", we want to explore what tools on GitHub that can help maintainers to identify new talents.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace deprecated team management features with GitHub native tools

2 participants