chore(docs): Add bi-weekly community meeting documentation

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,6 @@
 <!--  Thanks for sending a pull request!  Here are some tips for you:
 
-- If this is your first contribution, read our Getting Started guide https://github.com/iflytek/community/blob/main/contribute.md
+- If this is your first contribution, read our Getting Started guide https://github.com/iflytek/community/blob/main/CONTRIBUTING.md
 
 -->
 

README.md

@@ -17,6 +17,8 @@ To learn more about the project structure and organization, please refer to our
 
 ## Communicating
 
+We hold bi-weekly community meetings to discuss project updates, cross-SIG topics, and community initiatives. All community members are welcome to attend. See [Community Meeting](community-meeting.md) for schedule and participation details.
+
 For more specific topics, try a SIG.
 
 ## Contact

community-meeting.md

@@ -0,0 +1,124 @@
+# Iflytek Opensource Community Bi-weekly Meeting
+
+<!-- toc -->
+- [Purpose](#purpose)
+- [Meeting Structure](#meeting-structure)
+  - [Introduction (5 minutes)](#introduction-5-minutes)
+  - [Announcements (10 minutes)](#announcements-10-minutes)
+  - [Project Updates (15 minutes)](#project-updates-15-minutes)
+  - [Topics for Discussion (20 minutes)](#topics-for-discussion-20-minutes)
+  - [Recognition (5 minutes)](#recognition-5-minutes)
+  - [Open Floor (5 minutes)](#open-floor-5-minutes)
+- [Participation](#participation)
+- [Agenda Management](#agenda-management)
+- [Notetaker Role](#notetaker-role)
+- [Best Practices for Presenters](#best-practices-for-presenters)
+- [Demo Guidelines](#demo-guidelines)
+- [Archives](#archives)
+- [Contact](#contact)
+<!-- /toc -->
+
+We hold bi-weekly community meetings to provide a holistic overview of community activities, project updates, and governance discussions. The meeting also serves as a forum for discussing cross-project concerns that require broader community input.
+
+**Schedule**: Every two weeks, [specify day and time]
+**Platform**: [Zoom/Tencent Meeting/etc.]
+**Recording**: Meetings are recorded and archived
+
+## Purpose
+
+The bi-weekly community meeting provides a community-wide forum for:
+
+- Discussing various community activities and initiatives
+- Sharing critical project updates and release information
+- Reviewing governance updates and proposals
+- Discussing cross-SIG topics that need broader audience
+- Celebrating community contributions and achievements
+
+## Meeting Structure
+
+The meeting typically follows this agenda:
+
+### Introduction (5 minutes)
+- Welcome and introductions by host
+- Review of agenda items
+
+### Announcements (10 minutes)
+- Community-wide announcements
+- Upcoming events and deadlines
+
+### Project Updates (15 minutes)
+- Active project status updates
+- Release schedules and milestones
+- Cross-project coordination items
+
+### Topics for Discussion (20 minutes)
+- Pre-submitted discussion topics
+- Cross-SIG collaboration opportunities
+- Community feedback and suggestions
+
+### Recognition (5 minutes)
+- Community shoutouts and thanks
+- Recognition of recent contributions
+
+### Open Floor (5 minutes)
+- Any other business
+- Action items and next steps
+
+**Total Duration**: Approximately 60 minutes
+
+## Participation
+
+All community members are welcome and encouraged to attend. This includes:
+
+- Maintainers and reviewers
+- Active contributors
+- New community members
+- Users interested in project direction
+
+## Agenda Management
+
+Meeting agendas are maintained in [specify location: shared document/issue tracker/etc.].
+
+To add an item to the agenda:
+
+1. Submit your topic at least 24 hours before the meeting
+2. Include your name and a brief description
+3. Indicate if you will present or just want discussion
+4. Estimate the time needed (5, 10, or 15 minutes)
+
+The host will organize topics and share the final agenda before the meeting.
+
+## Notetaker Role
+
+A volunteer notetaker documents meeting discussions, decisions, and action items. Notes are published to [specify location] after the meeting.
+
+Volunteers are always welcome. Inform the host at the beginning of the meeting if you'd like to help take notes.
+
+## Best Practices for Presenters
+
+If you're presenting or leading a discussion:
+
+- **Be prepared**: Test your audio and screen sharing beforehand
+- **Be concise**: Respect time limits and the large audience
+- **Be clear**: Use clear slides if applicable, share links in the agenda
+- **Be inclusive**: Speak clearly, avoid jargon when possible
+- **Be present**: Arrive 5 minutes early to test equipment
+
+## Demo Guidelines
+
+If you plan to demo a feature or project:
+
+- Demos should be related to community-maintained projects
+- Arrive 10 minutes early to verify audio and screen sharing
+- Use high-quality audio equipment (headset recommended)
+- Ensure you're presenting from a quiet environment
+- Prepare for your time slot (5-10 minutes typical)
+- Have a backup plan if technical issues arise
+
+## Archives
+
+Meeting recordings and notes are archived at [specify location]. This provides a historical record of community decisions and discussions.
+
+## Contact
+
+For questions about the community meeting or to request agenda items, contact the community team via [specify communication channel].

contribute/issue-guidelines.md

@@ -25,7 +25,7 @@ When opening an issue, please include:
 3. **Environment** — Version, OS, relevant configuration
 4. **Screenshots/logs** — If applicable, include supporting evidence
 
-Use our [issue templates](.github/ISSUE_TEMPLATE/) when available.
+Use our [issue templates](../.github/ISSUE_TEMPLATE/) when available.
 
 ## Issue Triage Process