Skip to content

docs: update mentor information for TARDIS RT Collaboration, The Honeynet Project, and Uramaki LAB#2001

Merged
S3DFX-CYBER merged 1 commit into
S3DFX-CYBER:mainfrom
shrutisd739:fix-uramaki-lab
Jul 15, 2026
Merged

docs: update mentor information for TARDIS RT Collaboration, The Honeynet Project, and Uramaki LAB#2001
S3DFX-CYBER merged 1 commit into
S3DFX-CYBER:mainfrom
shrutisd739:fix-uramaki-lab

Conversation

@shrutisd739

@shrutisd739 shrutisd739 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

📝 Description

This PR updates mentor information for multiple organizations by manually verifying their official GSoC 2026 ideas pages and communication channels. It includes updates for TARDIS RT Collaboration, The Honeynet Project, and Uramaki LAB by adding mentor details, communication channels, updating ideas page URLs where needed, and setting the organization status after verification.

🔗 Related Issue

Closes #412
Closes #414
Closes #430


🚀 Program Classification

  • GSSoC26
  • NSoC26
  • General Contribution

🔄 Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • 🔍 SEO improvement
  • 🎨 Style / UI improvement
  • ♿ Accessibility improvement
  • 📝 Documentation
  • ⚙️ CI / configuration
  • 🧹 Refactor / cleanup

🧪 How to Test

  1. Open data/mentors.json.
  2. Verify the updated entries for:
    • TARDIS RT Collaboration
    • The Honeynet Project
    • Uramaki LAB
  3. Confirm that the ideas page URLs, mentor information, communication channels, mailing lists (where applicable), and status fields have been updated correctly.
  4. Ensure the JSON file remains valid.

📸 Screenshots (if applicable)

Not applicable.


✅ Checklist

  • My code follows the project's existing style
  • I have tested my changes in a browser
  • I have linked the related issue above
  • My PR title follows Conventional Commits format (e.g. feat: add scroll button)
  • I have not introduced any new dependencies or build tools

Review in cubic

@shrutisd739
shrutisd739 requested a review from S3DFX-CYBER as a code owner July 6, 2026 19:03
@vercel

vercel Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@shrutisd739 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 github-actions Bot added size/m good first issue Good for newcomers gssoc26 GirlScript Summer of Code 2026 labels Jul 6, 2026
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

💬 Faster Reviews & Assignments

Hi @shrutisd739, for faster coordination and smoother communication, consider joining our Discord community:

👉 https://discord.gg/MmZGG2ee

Useful Channels

  • #issue-links-for-assignment → Share issue links for assignment help
  • #pr-links-for-review → Share PR links for mentor/maintainer review

Please avoid spamming channels or repeatedly pinging mentors/maintainers.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

👋 Thanks for opening a PR, @shrutisd739!

Your PR has entered the 🚦 PR Review Pipeline.

🟢 GSSOC PR detected — your PR will be routed through the GSSOC mentor review pipeline.

⚠️ Dual-label notice: Both GSSOC and NSOC signals were detected in your PR. GSSoC takes priority and your PR has been classified as a GSSoC PR only. If this is incorrect, please remove the unintended program keyword from your PR description and push a new commit.


🔄 Review Flow

Stage Reviewer Purpose
Stage 1 🤖 Automation Validation · Duplicate Detection · AI/Slop Checks · Formatting · PR Analysis
Stage 2 🧑‍🏫 GSSOC Mentor Code Review · Scope Validation · Quality Check
Stage 3 🔑 Project Admin / Maintainer Final Approval & Merge Decision

The automated PR analysis system will verify issue linkage, PR relevance, and contribution quality.

A pipeline status comment may appear automatically as your PR progresses.


✅ Contributor Checklist

  • Sign commits using git commit -s
  • Link a valid issue (Closes #123)
  • Keep changes focused and relevant
  • Do not include unrelated modifications
  • Ensure workflows/build/tests are passing
  • Read the appropriate contributor guide:

⚠️ Important Notes

  • Low-quality, spammy, or AI-generated PRs may be closed
  • PRs without linked issues may fail automated checks
  • Large unrelated PRs are likely to be rejected
  • Review times may vary depending on mentor/reviewer availability

Happy contributing 🚀

This message is posted automatically and only once.

@github-actions github-actions Bot added gssoc26 GirlScript Summer of Code 2026 and removed gssoc26 GirlScript Summer of Code 2026 labels Jul 6, 2026
@github-project-automation github-project-automation Bot moved this to Todo in GSSOC 26 Jul 6, 2026
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

✅ DCO Sign-off Verified

Hi @shrutisd739 👋

All commits in this PR contain valid Signed-off-by lines.

Thank you for following the DCO requirements 🚀

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

⚠️ Dual Program Label Detected

Hi @shrutisd739,

Your PR description mentions both GSSOC and NSOC.

Detected Labels Resolution
gssoc, nsoc GSSoC priority applied — classified as a GSSoC PR

ℹ️ Only one program label may be active at a time. GSSoC takes priority when both are present.

If this is incorrect, please:

  1. Remove the unintended program keyword from your PR description
  2. Push a new commit or re-open the PR to re-trigger classification

📖 See our Contributing Guide for labeling details.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🚦 PR Review Pipeline

🟢 GSSOC PR

Stage Status
Stage 1 — Automated Checks ✅ All automated checks passed
Stage 2 — Mentor/Reviewer ⏳ Awaiting GSSOC mentor review
Stage 3 — Maintainer 🔒 Blocked until Stage 2 passes

No active issues


Last updated: Mon, 06 Jul 2026 19:03:57 GMT

@github-actions github-actions Bot added gssoc26 GirlScript Summer of Code 2026 and removed gssoc26 GirlScript Summer of Code 2026 labels Jul 6, 2026
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

✅ PR Validation Passed

Hi @shrutisd739, automated PR validation checks passed.

Your PR is ready for review.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🤖 TENET Agent Review

📋 Summary

This pull request updates the data/mentors.json file, adding detailed mentor, communication channel, and ideas page information for "TARDIS RT Collaboration", "The Honeynet Project", and "Uramaki LAB". It also updates the status field for these organizations to "ok" after verification. The changes are documentation-focused and appear to align with the described manual verification process.

🔐 Security Findings

No security issues found. This PR modifies a static JSON data file and does not introduce any code that could lead to prompt injection, hardcoded secrets, insecure dependencies, or other vulnerabilities relevant to the TENET AI project's core functionality.

🧹 Code Quality

  • data/mentors.json - Inconsistent population of github and githubUrl fields within the mentors arrays. For "TARDIS RT Collaboration" (L4752-L4775) and "The Honeynet Project" (L4799-L4814), all mentor github and githubUrl fields are empty strings. For "Uramaki LAB" (L5589-L5612), some are populated while others are empty. It's recommended to either consistently populate these fields if the data is available, or use null instead of empty strings for truly absent data to maintain clarity and consistency.
  • data/mentors.json - The mailingLists field for "Uramaki LAB" (L5614) contains a Discord invite URL. While Discord serves as a communication channel, the field name mailingLists typically implies email-based lists. Consider if the channels array would be a more semantically appropriate place for this type of link, or if the definition of mailingLists should be clarified in the project's data schema documentation.

✅ What's Done Well

  • The PR accurately updates the ideasUrl, channels, mentors, and status fields for the specified organizations, improving the completeness of the data.
  • The JSON formatting and indentation are consistent and correctly applied throughout the modified file.
  • The PR description is clear, detailed, and adheres to the project's contribution guidelines, including linking related issues and providing testing instructions.

📝 Overall Verdict

[REQUEST CHANGES] - Address the inconsistency in mentor GitHub details and clarify the semantic use of the mailingLists field for non-email channels.

@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6721a927-9cb6-48c9-8a08-15db9820180d

📥 Commits

Reviewing files that changed from the base of the PR and between 322bbdb and 10a64fe.

📒 Files selected for processing (1)
  • data/mentors.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • data/mentors.json
📜 Recent review details
⚠️ CI failures not shown inline (1)

Commit Status: Vercel: Vercel

Conclusion: failure

Authorization required to deploy.

📝 Walkthrough

Summary by CodeRabbit

  • New Features
    • Added complete mentor contact details for three organizations, including updated communication channels, mentor names, and refreshed availability status.
    • Improved discoverability by replacing placeholder entries with valid contact information and updating ideas links where applicable.

Walkthrough

Updates data/mentors.json with verified contact channels, mentor lists, ideas URLs, refreshed fetch dates, and ok statuses for three organizations.

Changes

Mentor contact info updates

Layer / File(s) Summary
Verified mentor contact records
data/mentors.json
Populates channels and mentor lists, updates ideas URLs and fetch dates, and changes TARDIS RT Collaboration, The Honeynet Project, and Uramaki LAB to status: "ok".

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related issues

  • Issue 376: Similar manual verification and population of mentor contact data.
  • Issue 378: Similar updates to organization contact records and ok statuses.
  • Issue 375: Similar mentor contact verification in data/mentors.json.
  • Issue 310: Similar organization mentor-data updates.

Possibly related PRs

Suggested labels: area:data, type:docs, research

Suggested reviewers: tarunyaprogrammer, 12fahed, saurabh24thakur, sparshm8, s3dfx-cyber

Poem

Three records bloom in JSON bright,
With mentor names and channels light.
Fresh ideas paths and dates now flow,
Their statuses proudly say “ok”!
A bunny hops through data’s glow. 🐰

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the mentor information updates for the three organizations.
Description check ✅ Passed The description follows the template with all required sections filled in and relevant details provided.
Linked Issues check ✅ Passed The changes match the linked issues by updating mentor contacts, channels, ideas URLs, and status for #412, #414, and #430.
Out of Scope Changes check ✅ Passed The PR only updates data/mentors.json for the three requested organizations, with no clear unrelated changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai
coderabbitai Bot requested review from 12fahed and saurabh24thakur July 6, 2026 19:04
@greptile-apps

greptile-apps Bot commented Jul 6, 2026

Copy link
Copy Markdown

Greptile Summary

This PR updates mentor data for three organizations. The main changes are:

  • Adds TARDIS RT Collaboration mentor names and a Gitter channel.
  • Adds The Honeynet Project mentor names while keeping its Discord contact.
  • Adds Uramaki LAB mentors, GitHub Issues, and Discord contact details.

Confidence Score: 5/5

This looks safe to merge.

  • No blocking issues found in the changed data.
  • The updated entries keep the existing mentor JSON shape.

Important Files Changed

Filename Overview
data/mentors.json Updates mentor, contact channel, mailing list, and status fields for TARDIS RT Collaboration, The Honeynet Project, and Uramaki LAB.

Reviews (1): Last reviewed commit: "Update mentor information for multiple o..." | Re-trigger Greptile

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@data/mentors.json`:
- Around line 5625-5631: The Discord invite is incorrectly categorized under
mailingLists in the mentor data. Update the mentor entry so the Discord object
is moved from mailingLists to channels, keeping the same type, url, and label
fields. Use the mailingLists and channels fields in the mentor record to locate
and reclassify this contact method.
- Line 5585: The Uramaki LAB entry’s ideasUrl is pointing to the GSoC
organization profile instead of the ideas page; update the value in the
mentors.json record for Uramaki LAB to use the organization’s ideas dashboard
URL, and verify the ideasUrl field references https://ruxailab.github.io/gsoc/
rather than the profile page.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a8ebd760-9e21-4ee3-9ceb-2bde363b2324

📥 Commits

Reviewing files that changed from the base of the PR and between b094586 and b9b5241.

📒 Files selected for processing (1)
  • data/mentors.json
📜 Review details
⏰ Context from checks skipped due to timeout. (1)
  • GitHub Check: cubic · AI code reviewer
⚠️ CI failures not shown inline (1)

Commit Status: Vercel: Vercel

Conclusion: failure

Authorization required to deploy.
🔇 Additional comments (2)
data/mentors.json (2)

4740-4784: LGTM!

Also applies to: 4796-4832


4749-4780: 🗄️ Data Integrity & Integration

Check whether James Gillanders belongs in the TARDIS mentors array.

Comment thread data/mentors.json Outdated
Comment thread data/mentors.json Outdated
@github-project-automation github-project-automation Bot moved this from Todo to In progress in GSSOC 26 Jul 6, 2026

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

All reported issues were addressed across 1 file

Confidence score: 5/5

  • Safe to merge after the addressed issues were fixed.
Architecture diagram
sequenceDiagram
    participant Dev as Developer
    participant Repo as GitHub Repo
    participant CI as CI Pipeline
    participant Site as Static Site Builder
    participant App as Web Application
    
    Note over Dev,App: Mentor data update flow

    Dev->>Repo: PR: Update mentors.json for 3 orgs
    Repo->>CI: Trigger validation
    
    CI->>CI: JSON schema validation
    alt Valid JSON
        CI-->>Repo: Pass checks
    else Invalid JSON
        CI-->>Repo: Fail checks
        Repo-->>Dev: Request fix
    end
    
    Repo-->>Dev: Merge to main
    
    Repo->>Site: Trigger site rebuild
    Site->>Site: Read mentors.json
    Site->>App: Build pages with updated data
    
    Note over App: Runtime display
    
    App->>App: Load organization data
    App->>App: TARDIS RT Collaboration<br/>- Ideas URL updated<br/>- 6 mentors added<br/>- Gitter channel added<br/>- Status: ok
    App->>App: The Honeynet Project<br/>- 4 mentors added<br/>- Status unchanged
    App->>App: Uramaki LAB<br/>- 6 mentors added<br/>- GitHub channel added<br/>- Discord mailing list added<br/>- Status: ok
    
    App-->>User: Display updated org info with mentors, channels & ideas links
Loading

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread data/mentors.json Outdated
Comment thread data/mentors.json Outdated
Comment thread data/mentors.json Outdated
Comment thread data/mentors.json Outdated

@greptile-apps greptile-apps 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.

Your trial has ended. Reactivate Greptile to resume code reviews.

@github-actions github-actions Bot added gssoc26 GirlScript Summer of Code 2026 and removed gssoc26 GirlScript Summer of Code 2026 labels Jul 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🤖 TENET Agent Review

📋 Summary

This PR updates mentor and organization details within the data/mentors.json file for "TARDIS RT Collaboration", "The Honeynet Project", and "Uramaki LAB". The changes include updating ideas page URLs, adding communication channels, populating mentor information, and setting the organization status to 'ok'. The approach of updating a static data file based on manual verification is sound for this type of documentation change.

🔐 Security Findings

No security issues found. This PR modifies a static JSON data file and does not introduce executable code, new dependencies, or changes to the core LLM security middleware logic. The data itself (mentor names, URLs) does not present direct prompt injection or jailbreak vectors for the TENET AI system.

🧹 Code Quality

  • data/mentors.json - Inconsistent Mentor GitHub Details: For "TARDIS RT Collaboration" and "The Honeynet Project", all mentor entries have empty github and githubUrl fields. For "Uramaki LAB", some mentors have these fields populated while others are empty. For consistency and completeness, it would be beneficial to either populate these fields where possible or clarify the policy for their inclusion.
  • data/mentors.json - Future lastFetched Timestamp: The lastFetched timestamp is set to 2026-06-30T16:45:00.000Z for all updated entries. While a valid format, this is a future date. The lastFetched field should ideally reflect the actual date and time the data was last verified or fetched, which would be the current date of the PR.

✅ What's Done Well

  • The PR correctly updates the status field from no-contact-found to ok for organizations where contact information has been added, accurately reflecting the improved data quality.
  • The ideasUrl fields have been updated to more specific and current URLs, enhancing the accuracy and utility of the documentation.
  • The PR adheres to the Conventional Commits format and provides a clear description with detailed testing instructions.

📝 Overall Verdict

REQUEST CHANGES - Address the inconsistency in mentor GitHub details and correct the lastFetched timestamp to reflect the actual date of verification.


Review powered by TENET Agent 🛡️ | Triggered automatically on PR #2001

@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown
Contributor

⏰ Mentor Review Timeout

The following reviewer(s) did not respond within 24 hours:

Replacement reviewer(s) assigned:


Mentors are expected to review within 24 hours. This is an automated rotation.

@S3DFX-CYBER S3DFX-CYBER left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Lgtm

@S3DFX-CYBER
S3DFX-CYBER merged commit 1174c7d into S3DFX-CYBER:main Jul 15, 2026
51 of 62 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🎉 Pull Request Merged

Hi @shrutisd739! Here's your current ranking:

Rank User Merged PRs Score
10 amrita-a-menon @amrita-a-menon 4 40
11 shrutisd739 @shrutisd739 4 40
12 arpit2006 @arpit2006 4 40

Congratulations on getting your PR merged 🚀

Current Rank: #11

Current Score: 40

Keep contributing to climb the leaderboard 📈

@github-actions

Copy link
Copy Markdown
Contributor

🏆 Mentor Review Leaderboard

Top mentor reviewers of all time:

Rank Mentor Reviews Score
🥇 @KumarNirupam1 38 168
🥈 @TarunyaProgrammer 23 92
🥉 @nitinog10 16 69
4 @Anushreebasics 20 52
5 @deepak0x 9 38

Review scoring:

  • Detailed review → 5 pts
  • Medium review → 3 pts
  • Quick review → 2 pts
  • Changes requested bonus → +1 pt

🔗 Leaderboard Update PR: #2018

Thank you to all mentors reviewing PRs! 🚀

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

Projects

Status: Done

5 participants