English | 中文
This document outlines the planned migration of the POSC community from our current communication platforms to a more structured, developer-friendly ecosystem centered around GitHub. This transition will occur gradually over a 12-18 month period to ensure minimal disruption to our community.
Current State: Primary communication on QQ group
Target State: GitHub as core collaboration hub + Telegram for real-time discussion
Migration Principle: Value-driven, gradual transition, community-focused
Timeline: Q3 2025 - Q1 2027
Our current platform has served us well, but as our community grows and becomes more technical, we face several limitations:
| Aspect | Current Platform (QQ) | New Platform (GitHub + Telegram) |
|---|---|---|
| Knowledge Preservation | ❌ Messages get lost, valuable content disappears | ✅ Discussions, Wiki, and READMEs create permanent knowledge base |
| Technical Collaboration | ❌ Difficult to track issues, manage features, or review code | ✅ Issues & Projects provide professional task management tools |
| Openness & Transparency | ❌ Relatively closed ecosystem, hard for newcomers to follow | ✅ Built for open collaboration, attracting more developers |
| Code Integration | ❌ Completely separate from code repositories | ✅ Native integration with Git repositories and CI/CD pipelines |
| Automation | ❌ Limited automation capabilities | ✅ GitHub Actions enable powerful workflow automation |
| Community Discovery | ❌ Hard for new members to find and evaluate our community | ✅ GitHub provides discoverability through stars, forks, and contributions |
In short, this migration is about upgrading our collaboration from "chat" to "action" and building a more sustainable foundation for our growing community.
The migration will occur in phases to ensure community members have adequate time to adapt. The QQ group will remain active throughout phases 1 and 2 as a backup notification channel.
- Objective: Establish new platforms, create initial workflows, attract early adopters
- Key Actions:
- Create GitHub Organization and core repositories
- Develop comprehensive
CONTRIBUTING.mdandREADME.mddocumentation - Set up GitHub Discussions for Q&A and idea discussion
- Establish Telegram group for real-time communication (link in QQ bio)
- Migrate all existing documentation to GitHub Wiki
- Pin new platform links in QQ group announcement
- Community Impact: Minimal changes. QQ remains primary; members encouraged to explore new platforms.
- Objective: Shift core collaboration to GitHub, reduce reliance on QQ
- Key Actions:
- All project tasks, feature discussions, and bug reports must use GitHub Issues
- All official announcements first published on GitHub Releases/Discussions
- Meeting notes, technical documents archived in relevant repositories
- QQ group primarily used for announcements and redirecting to GitHub
- Regular "office hours" on Telegram for real-time help
- Community Impact: Active members should be using GitHub daily; QQ becomes secondary channel.
- Objective: Complete migration, archive QQ group as read-only
- Key Actions:
- Assess community activity to confirm successful migration
- Post final archival notice in QQ group
- Set QQ group to "read-only" mode or maintain as backup channel
- All new members directly onboarded to GitHub and Telegram
- Community Impact: GitHub becomes primary platform; QQ group archived.
- Short-term: No immediate changes. Your QQ access remains active.
- Medium-term: Gradually shift your activity to GitHub. We'll provide tutorials and support.
- Long-term: Enjoy a better organized, more valuable community experience.
- Benefits: Proper issue tracking, code review tools, continuous integration, and recognition through commit history.
- Action: Star our repositories, set up watch notifications for relevant projects.
- Benefits: Better organized knowledge base, clearer guidelines for participation, preserved community history.
- Action: Learn to use GitHub Discussions for questions and ideas—it's similar to forum software!
Q1: Will I lose access to the QQ group? A: No. The QQ group will remain active throughout 2024 and most of 2025. It will only become read-only after most community activity has naturally shifted to the new platforms.
Q2: I'm not a developer. Is GitHub still relevant for me? A: Absolutely! GitHub isn't just for code. You can use Discussions for ideas, Issues for reporting problems, and Wiki for documentation—all without writing a line of code.
Q3: What about our history and files in the QQ group? A: We will systematically archive valuable content from QQ to GitHub Wiki and relevant repositories before phase 3 begins.
Q4: Is the Telegram group mandatory? A: No. Telegram is optional for real-time conversation. All official content and decisions will be on GitHub, which remains the source of truth.
Q5: What if I need help with the new platforms? A: We'll provide tutorial resources, host onboarding sessions, and maintain a help channel in Telegram for questions about using GitHub.
- For technical help with GitHub: Open an issue in the help repository
- For general questions: Join our Telegram discussion group
- For urgent matters: DM administrators on QQ (during transition period)
Community evolution requires adaptation from all members. We believe this platform migration will bring renewed vitality and brighter future for POSC. We appreciate your patience and participation during this transition.
This document will be updated regularly. Last updated: April 2025