Contributing to rocket.chat

[Mubashir2611]

Hi I’m Muberser, starting early for GSoC 2026 and looking for mentors or maintainers who can guide me in open-source. My main tech stack is JavaScript and React, and I’m eager to contribute through real code—fixing bugs, improving UI/UX, writing docs, or picking up beginner-friendly issues. I’d love suggestions on which JS/React-based codebases are good to start with and how to move from small contributions toward a strong GSoC proposal. Any guidance or direction would be really appreciated. Thanks!

[smirk-dev]

Hi Mubashir! Great to see you preparing for GSoC 2026! I can share some concrete guidance based on my contribution experience with Rocket.Chat:

Best Starting Points for JS/React Contributors:

1. Ideal Beginner Issues:

   • Issues labeled "good-first-issue" or "help-wanted"
   • UI/UX bugs in Rocket.Chat React components
   • Bug fixes in smaller components vs entire systems
   • Documentation improvements

2. Recommended Repositories:

   • Rocket.Chat/fuselage - Design system/component library (perfect for React learners)
   • Rocket.Chat/Rocket.Chat.ReactNative - Mobile development
   • Rocket.Chat/Rocket.Chat - Main repo (focus on frontend directory)

3. Getting Your First PR Merged:

   • Start with issues having 0-2 comments (less competitive)
   • Pick issues 1-2 days old (before heavy competition)
   • Post detailed approach comment showing deep analysis
   • Build relationship with maintainers early

4. Path to GSoC Selection:

   • Claim 5-8 issues with comprehensive technical approaches
   • Actively engage in GitHub Discussions (like this one!)
   • Get at least 1-2 PRs merged before GSoC application
   • Document your learning journey publicly

5. Technical Skills to Develop:

   • Master React hooks (useCallback, useEffect, useState)
   • Understand RxJS observables (used in Rocket.Chat)
   • Learn TypeScript patterns
   • Get comfortable with testing frameworks (Jest, React Testing Library)

6. Direct Next Steps:

   • Check /RocketChat/Rocket.Chat/issues?q=is%3Aissue+is%3Aopen+no%3Aassignee+no%3Acomments
   • Look for issues opened in last 3-7 days
   • Pick one that matches your expertise level
   • Post a detailed approach before any code
   • Engage with maintainers on that issue

The key insight: Visibility > Speed. Make yourself known through quality participation, not just quick fixes.

Happy to discuss specific issue selection or technical approaches! Feel free to reach out if you have questions.

[smirk-dev]

Great question about GSoC 2026! Building on the excellent guidance above, here's a strategic roadmap specifically tailored for GSoC success:

1. Qualification Strategy:

• Issue Selection Priority: Focus on "good first issue" tags and "beginner-friendly" tags first
• Visibility Approach: Actively participate in discussions (like this one!) to demonstrate domain expertise
• Approach Documentation: Always post detailed technical approaches in issue comments before coding
• Mentorship Connection: Engage with issue authors and maintainers early to build relationships

2. GSoC-Specific Technical Focus Areas:

• Frontend (React): Modal/UI component improvements, theme system enhancements, accessibility fixes
• Backend (TypeScript/Node.js): API endpoint optimizations, database query improvements, security hardening
• DevOps/Infrastructure: Docker/Kubernetes configuration, CI/CD pipeline improvements

3. Building Your GSoC Portfolio:
Small fixes (accessibility, UI tweaks) - 1-2 PRs
Medium features (component enhancements) - 2-3 PRs
Complex implementation (backend optimization) - 1-2 PRs

4. Pre-GSoC Timeline:

• Now to December: Claim 5-10 diverse issues, demonstrate technical depth
• January-February: Submit comprehensive proposals for 3-5 projects
• March: Engage with mentors, refine proposals based on feedback

5. Critical Success Factors:

• Communication: Propose solutions before coding, ask questions in discussions
• Quality over Quantity: 3 excellent PRs > 10 mediocre ones
• Persistence: Some issues will be competitive - don't give up on good ones
• Documentation: Write clear commit messages and PR descriptions

I'm actively working on this myself for GSoC 2026 and happy to discuss specific issue selection or technical approaches. Feel free to reach out!

[Mubashir2611]

Hey so how to setup? Can you guide me please!

[smirk-dev]

Great question! Here's the quickest path to get started:

Official Documentation

Start with the Rocket.Chat Developer Guide: https://developer.rocket.chat/

The main repository README has detailed setup instructions: https://github.com/RocketChat/Rocket.Chat

Setup Options:

Option 1: Docker (Recommended for beginners)

Fastest way to run Rocket.Chat locally:

docker run -d -p 3000:3000 rocket.chat

Then visit http://localhost:3000

Option 2: Native Setup

If you want to contribute to the code:

1. Clone: git clone https://github.com/RocketChat/Rocket.Chat.git
2. Install Node.js (v16+ recommended)
3. Run: npm install && npm start
4. Visit http://localhost:3000

For Specific Component Setup:

• Frontend (React): Check /RocketChat/fuselage repo
• Main App: See /apps/meteor directory setup
• Mobile: Clone /RocketChat/Rocket.Chat.ReactNative

Next Steps:

1. Follow the official Contributing Guide in the repo
2. Pick an issue you want to tackle
3. Set up the specific component you'll be working on
4. Run tests locally before submitting PR

The official docs will have all environment variables and dependencies specific to your setup. Feel free to ask follow-ups if you hit any blockers!

[masonearl]

Great that you're starting early for GSoC! Here's a practical path:

Getting Started with Rocket.Chat

1. Set up the dev environment locally - Follow their development guide. This alone teaches you a lot about the architecture.
2. Look for good first issue labels - These are specifically tagged for newcomers.
3. Start with docs or tests - Lower barrier to entry, still counts as contribution.

Tool Recommendation

For navigating large codebases like Rocket.Chat, try Cursor IDE. It's VS Code with AI built-in - you can ask it "how does the message sending flow work?" and it'll search the codebase and explain the architecture. Super helpful for understanding unfamiliar React codebases.

GSoC-Specific Tips

• Join their communication channels (Discord/Slack/Open Server)
• Engage with maintainers early - they remember active contributors
• Document your contributions in a spreadsheet - makes your proposal stronger
• Look at past GSoC projects for Rocket.Chat to understand scope expectations

Good luck with GSoC 2026!

[Mubashir2611]

Thanks.