3.0 KiB
3.0 KiB
Team Structure - IDE Extensions
Core Team
Extension Leads
| Name | Role | Responsibilities | Skills |
|---|---|---|---|
| TBD | VS Code Lead | TypeScript extension, marketplace, user support | TypeScript, VS Code API, CI/CD |
| TBD | JetBrains Lead | Kotlin plugin, IntelliJ SDK, performance | Kotlin, IntelliJ Platform SDK |
| TBD | Neovim Lead | Lua plugin, async validation | Lua, Neovim API, plenary.nvim |
Shared Resources Team
| Name | Role | Responsibilities | Skills |
|---|---|---|---|
| TBD | Protocol Designer | API contract, OpenAPI, TypeScript types | API design, JSON Schema |
| TBD | UX Designer | Icons, UI/UX patterns, accessibility | Design systems, accessibility |
| TBD | Documentation Lead | READMEs, tutorials, video guides | Technical writing, teaching |
| TBD | QA Lead | Testing strategy, CI/CD, automation | Testing frameworks, DevOps |
Platform Team
| Name | Role | Responsibilities | Skills |
|---|---|---|---|
| TBD | Platform Lead | Coordination, architecture decisions, unblocker | Architecture, communication |
| TBD | Security Reviewer | API key handling, CORS, audits | Security, cryptography |
| SME | MCP Server SME | Backend API knowledge, integration | Go, REST APIs |
Advisory Board
| Name | Role | Expertise |
|---|---|---|
| Community Rep | User Advocate | Real-world usage feedback |
| Product Manager | Prioritization | Feature roadmapping |
Communication
Channels
- Slack/Discord:
#ide-extensions(daily chat) - Weekly Sync: Mondays 10am PT (video call)
- GitHub Issues: Task tracking
- RFCs: Architecture decisions
Meeting Cadence
| Meeting | Frequency | Attendees | Purpose |
|---|---|---|---|
| Standup | Daily | All leads | Blockers, progress |
| Sprint Planning | Bi-weekly | All | Sprint commitment |
| Demo | Bi-weekly | All + stakeholders | Show & tell |
| Architecture | Monthly | Leads + advisors | Tech decisions |
Decision Making
Process
- RFC Draft - Author writes proposal
- Review Period - 3 days for feedback
- Discussion - Address concerns
- Decision - Platform Lead + relevant leads
- Document - Update ADRs
Escalation
- Technical disputes → Platform Lead
- Scope changes → Product Manager
- Resource conflicts → Project Sponsor
Team Onboarding
New Lead Checklist
- Added to Slack channel
- GitHub access granted
- Local dev environment setup
- Read IDE_EXTENSIONS_PLAN.md
- Met with Platform Lead
- Assigned mentor (if needed)
Team Values
- User First - Every decision considers user impact
- Quality Over Speed - Better to delay than ship broken
- Transparent - Blockers surfaced immediately
- Collaborative - Cross-IDE learnings shared
- Pragmatic - Simple solutions preferred
Last Updated: 2026-02-12
Next Review: 2026-02-26