QCX Open Source

[ngoiyaeric]

Extending multiple offers for undergraduate students to get hands-on experience working on cutting edge agent powered open source software starting 5th of May.

Asynchronous & Remote

Roadmap.

Frontend

• Account account settings page.
• System Instructions & Model Setting.

Backend

• Database Migrations. (Supabase)
• Structured Data (Zod Schema + Postgres (PostGIS) (PGVector)

Mapping

• Mapbox entire functionality accessible contextually via chat using Model context protocol.
• Model Protocol Utility Extension Guide.

Full Stack

• Mapbox Rendering and Interaction optimizations.
• Text editor with Embeddings,

Agents

• Dynamic Prompt Recommendations.
• Reasoning Model integrations.
• Multi Step Functions

[VaibhavSain]

how i can join this is open source project

[ngoiyaeric]

Here are clear, concise open source contributor guidelines you can follow (or adapt into a project's CONTRIBUTING.md file). These draw from best practices used by successful projects on GitHub and elsewhere.

1. Start small and read first
   Always begin by reading the project's README.md, CONTRIBUTING.md (if it exists), and CODE_OF_CONDUCT. Understand the project's goals, scope, and current issues before jumping in. Look for "good first issue," "help wanted," or beginner-friendly labels.

2. Communicate early
   Comment on an issue to express interest, ask questions, or propose your approach before starting work. This avoids duplicate effort and ensures alignment with maintainers.

3. Set up your environment
   Follow the project's setup instructions exactly (e.g., install dependencies, run tests locally). Verify everything works before coding.

4. Follow coding & commit standards
   Adhere to the project's style guide, linting rules, and commit message conventions (e.g., conventional commits like "fix: resolve bug X"). Write clear, focused commits.

5. Test thoroughly
   Add or update tests for your changes. Run the full test suite locally and ensure nothing breaks. Include edge cases where relevant.

6. Submit clean pull requests

   • Keep PRs small and focused on one thing.
   • Use a descriptive title and detailed body (what, why, how; link to related issues).
   • Include screenshots, before/after examples, or test results if applicable.
   • Request review politely and respond to feedback promptly.

7. Be patient and respectful
   Maintainers are often volunteers—reviews can take time. Stay polite in discussions, thank people for feedback, and learn from rejections.

8. Contribute beyond code
   Fix typos/docs, improve README, report bugs with clear reproduction steps, or help triage issues—these are valuable too!

Following these makes your contributions more likely to be merged and welcomed. For project maintainers creating guidelines, place them in a CONTRIBUTING.md file at the repo root (GitHub auto-links it for new issues/PRs). Great templates exist from GitHub's Open Source Guides, nayafia's contributing-template, or The Good Docs Project. Happy contributing! 🚀