Request to join as team member/maintainer

[KushalLukhi]

Hi @mckaywrigley and team,

I've been actively contributing to chatbot-ui and wanted to express interest in joining as a team member or maintainer to help with ongoing development and maintenance.

Contributions Summary

I've submitted 6 PRs over the past period:

1. fix: disable next-pwa in development mode #1998 - Fix: Disable next-pwa in development mode (Issue Propuesta: deshabilitar next-pwa en dev (next.config.js) #1978)
2. feat: allow custom OpenAI-compatible base URL via OPENAI_BASE_URL #1999 - Feat: Add OPENAI_BASE_URL for OpenAI-compatible APIs (Issue Could we add support for specifying a custom base URL for OpenAI-compatible APIs? #1990)
3. docs: clarify Supabase status values mapping in setup guide #2000 - Docs: Clarify supabase status values mapping (Issue Why the outputs of the 'supabase status' are different from the readme.md #1983)
4. feat: add GPT-4o mini support #2001 - Feat: Add GPT-4o mini support
5. feat: add CometAPI as LLM provider #2002 - Feat: Add CometAPI as LLM provider (Issue Feature request: Add CometAPI as an LLM provider #1975)
6. feat: add OpenAI o1 and GPT-4o mini models #2003 - Feat: Add OpenAI o1-preview, o1-mini, and GPT-4o mini models

Areas of Focus

• Model integrations: Adding latest OpenAI models and new providers
• Developer experience: Improving local development setup
• Documentation: Clarifying setup instructions
• Feature parity: Ensuring latest LLM capabilities are available

Why Me?

• Consistent contributor with high-quality, well-tested PRs
• Follows project patterns and conventions
• Provides comprehensive PR descriptions with testing steps
• Available for ongoing maintenance, issue triage, and community support
• Actively maintains a fork synced with upstream

Happy to Help With

• Reviewing open issues and prioritizing backlog
• Bug fixes and feature requests
• Documentation maintenance
• Community support and issue triage

Let me know if there's a process for joining the team or if you'd like to discuss further.

Thanks for consideration!

---

Kushal Lukhi
GitHub: @KushalLukhi

[KushalLukhi]

Update: I've continued contributing actively and have now submitted 10 quality PRs covering multiple improvement areas:

Bug Fixes:

• fix: disable next-pwa in development mode #1998 - Disable next-pwa in development mode (Issue Propuesta: deshabilitar next-pwa en dev (next.config.js) #1978)
• fix: update Perplexity models to match current API #2005 - Update Perplexity models to match current API (Issue Perplexity Models Not Supported #1836)
• fix: disable next-pwa in development to prevent stale SW cache #2006 - Disable next-pwa in development to prevent stale SW cache (Issue Propuesta: deshabilitar next-pwa en dev (next.config.js) #1978)
• fix: update Perplexity types and remove deprecated models #2007 - Update Perplexity types and remove deprecated models
• fix: use CHAT_SETTING_LIMITS for max_tokens instead of hardcoded values #2008 - Use CHAT_SETTING_LIMITS for max_tokens instead of hardcoded values

Feature Additions:

• feat: allow custom OpenAI-compatible base URL via OPENAI_BASE_URL #1999 - Allow custom OpenAI-compatible base URL via OPENAI_BASE_URL (Issue Could we add support for specifying a custom base URL for OpenAI-compatible APIs? #1990)
• feat: add GPT-4o mini support #2001 - Add GPT-4o mini support
• feat: add CometAPI as LLM provider #2002 - Add CometAPI as LLM provider
• feat: add OpenAI o1 and GPT-4o mini models #2003 - Add OpenAI o1 and GPT-4o mini models

Documentation:

• docs: clarify Supabase status values mapping in setup guide #2000 - Clarify Supabase status values mapping (Issue Why the outputs of the 'supabase status' are different from the readme.md #1983)

All PRs include proper testing, follow project conventions, and address real user issues. Ready to help with ongoing maintenance and reviews.

cc @mckaywrigley