Fix: added mentor info for The P4 Language Consortium

[praphulln19]

Contribution Program

NSOC

Description

Verified the P4 Language Consortium GSoC 2026 ideas page and updated their mentor contact entry in data/mentors.json.

The P4 Language Consortium: Corrected ideasUrl from the old p4c wiki page to the actual 2026 GSoC ideas list (github.com/p4lang/gsoc/blob/main/2026/ideas_list.md). Added all 15 named mentors with their GitHub handles, cross-referenced directly from the official ideas list. Added the P4 Forum as a mailing list resource. Both Zulip channels (community chat + joining link) were already present and confirmed reachable. Set status to ok.

Sources verified:

• Ideas page: https://github.com/p4lang/gsoc/blob/main/2026/ideas_list.md
• Zulip: https://p4lang.zulipchat.com/
• P4 Forum: https://forum.p4.org/
• All 15 mentor GitHub handles confirmed from the "Potential mentors" section of the ideas list

Related Issue

Closes #423

Type of Change

• Data fix
• Bug fix
• Feature
• Documentation
• Refactor

How to Test

Run:

node agent/scripts/validate-mentors.js

Expected result:

Mentor data validation passed

Checklist

• Issue is assigned to me
• PR is linked to an issue
• Changes are minimal and focused
• No unnecessary dependencies added
• Code follows the zero-build philosophy
• I understand the change I submitted

[vercel]

Someone is attempting to deploy a commit to the s3dfx-cyber's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

⚠️ PR Validation Warning

Hi @praphulln19, thanks for contributing 🚀

• ⚠️ PR title should follow Conventional Commits.

---

Please update the PR accordingly.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR populates The P4 Language Consortium's mentor contact information in data/mentors.json with verified details: an updated GSoC 2026 ideas URL, Zulip community channel links, multiple named mentors with GitHub handles, a P4 Forum mailing list entry, and refreshed contributor guidance.

Changes

P4 Language Consortium mentor contact info

Layer / File(s)	Summary
P4 Language Consortium contact and mentor data update data/mentors.json	The P4 Language Consortium entry is updated with ideasUrl for the GSoC 2026 ideas page, channels array with two Zulip links and updated labels, mentors array populated with named mentors including GitHub handles and URLs, mailingLists entry for the P4 Forum, and tip text updated to reference joining the Zulip community and posting in the GSoC stream.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• S3DFX-CYBER/GSoC-Org-Finder-#237: Both PRs modify the same data/mentors.json mentor dataset; this PR populates contact and mentor fields for The P4 Language Consortium while PR #237 addresses the extraction/validation pipeline.

Suggested labels

level1, nsoc26

Suggested reviewers

• S3DFX-CYBER
• cubic-dev-ai

Poem

🐰 A rabbit hops through data fields so bright,
With mentor names and Zulip links in sight,
The P4 path now clearly marked with care,
For GSoC dreamers seeking counsel there! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is well-structured and comprehensively documents the changes made, including verification sources, mentor count, and testing instructions, all directly related to the changeset.
Linked Issues check	✅ Passed	The PR successfully fulfills all coding-related requirements from issue #423: corrected the ideas page URL, added 15 named mentors with GitHub handles, added mailing list information, verified communication channels, and set status to 'ok'.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly scoped to the objectives of issue #423—exclusively updating The P4 Language Consortium entry in data/mentors.json with verified mentor contact information.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately summarizes the main change: adding mentor information for The P4 Language Consortium to the data/mentors.json file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Pull Request Opened

Hi @praphulln19! Here's your current ranking:

Rank	User	Merged PRs	Score
31	@BhelPuriPanda	0	1
32	@praphulln19 ✨	0	1
33	@NguyenTuMinhLong	0	1

Current Rank: #32

Current Score: 1

Keep contributing to climb the leaderboard 📈

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Auto-approved: This change updates mentor data in a JSON configuration file with verified information from the official GSoC ideas page, involving no business logic, infrastructure, or security risk, making it safe to merge without human review.}

[praphulln19]

Please merge this PR it passed all the validation test @S3DFX-CYBER

[github-actions]

⚠️ Maintainer Ping Warning

Hi @praphulln19, please avoid repeatedly pinging maintainers for assignment, review, or merge requests.

Maintainers review contributions in queue order whenever possible.

Excessive pinging or spam comments may result in:

• spam labeling
• assignment removal
• moderation escalation

Recommended waiting times:

• Assignments: 12–24 hours
• PR reviews: 24–72 hours

[github-actions]

⚠️ DCO Sign-off Missing

Hi @praphulln19 👋

Some commits in this PR are missing a Signed-off-by line required by the Developer Certificate of Origin (DCO).

Fix

git commit --amend --signoff
git push --force

For multiple commits:

git rebase --signoff HEAD~N
git push --force

Example:

Signed-off-by: Your Name <you@example.com>

After fixing the commits, this comment will automatically update.

[github-actions]

✅ PR Format Check Passed

Hi @praphulln19, the PR structure and formatting checks passed successfully.

This does not mean the PR is approved or ready to merge.
Maintainer review is still required.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[S3DFX-CYBER]

@praphulln19 fix pr title

[praphulln19]

@praphulln19 fix pr title

Done