This document defines the structure and conventions for our GitHub organization.
Our goal is to maintain clarity, consistency, and collaboration across all telescope software efforts - from robotic control to data processing and user interfaces.
| Team | Subteams | Description |
|---|---|---|
| Robotics | - | Low-level telescope control and hardware integration. |
| Software | Data Analysis, Telescope, Website, BackEnd, Database |
Main software effort, divided into focused domains. |
Data Analysis |
- | Data processing, SDR signal handling, image analysis. |
Website |
- | Public-facing static site and web interfaces. |
BackEnd |
- | API development, database management, and server-side logic. |
Telescope |
- | Telescope's side of Back End integration and control logic. |
Database |
- | Database design, management, and query optimization. |
- Write: All organization members.
- Admin: Repository maintainers or tech lead. (for now @kesoglidis and @dyka3773)
The knowledgebase repo includes:
/docs
├── architecture/
├── hardware/
├── onboarding/
├── protocols/
├── research-how-tos/
└── software-guidelines/
Recommended pages:
docs/architecture/system-architecture/readme.md- high-level system architecture.docs/onboarding/developer-setup.md- new developer guide.docs/protocols/- telescope comms, SDR formats, telemetry schema.
Document maintained by: Iraklis Konsoulas (@dyka3773) - Software Team
Feedback: Open an issue or PR in the knowledgebase repo.