Didar Platform v1.0

Development Roadmap & Status Report

6
Total Phases
16w
Est. Remaining
5
Core FRs
50%
Current Progress
Phase 0: Infrastructure & Base Architecture
2 Weeks Completed

Established the foundational environment, database design, and service boundaries.

  • Deploy docker-jitsi-meet baseline across dev/staging.
  • Design custom user/room data layer (PostgreSQL).
  • Define service boundaries between Didar and Jitsi core.
Phase 1: Authentication Layer
1 Week Left In Progress (50%)

Implementing local authentication and directory service integration.

  • FR-AUTH-01: Configurable password policy & lockout state machine (Backend).
  • FR-AUTH-02: Database schema and model fields prepared for LDAP.
  • FR-AUTH-01: Prosody Lua auth module (Bridge Jitsi to Didar API).
  • FR-AUTH-02: LDAP bind-auth and group synchronization.

🎯 Immediate Next Step

Write the mod_auth_didar.lua module for Prosody. This will bridge the Jitsi client with the Didar custom database, allowing users created via the Didar API to log in directly to Jitsi.

Phase 2: RBAC, Room Lifecycle & Guest Allow-list
4-5 Weeks Upcoming

High-risk engineering phase focusing on server-side enforcement and custom room provisioning.

  • FR-AUTH-08: Design 4-role permission matrix (Admin, Host, User, Guest).
  • FR-ROOM-01/02: Build provisioning layer for temporary/permanent rooms & auto-end hooks.
  • FR-AUTH-06: Implement persistent, list-based guest allow-list mechanism.
Phase 3: Admin Panel (Built from Scratch)
3-4 Weeks Upcoming

Development of the graphical management interface. (Requires Phase 1 & 2 completion).

  • FR-ADM-01: User management UI (Create, edit, deactivate).
  • FR-ADM-01: Room & Meeting list management.
  • Secure API endpoints (Resolve current authentication tech debt).
Phase 4: Theming, Fonts & Bilingual Support
2-3 Weeks Parallel to Phase 3

UI customization and localization pass.

  • FR-UI-01: Build theme/config layer (Logo, colors, favicon).
  • FR-I18N-01/02: Swap default fonts (Shabnam/Vazirmatn) & full RTL/LTR QA.
Phase 5: Security Hardening & NFRs
2 Weeks Upcoming

Hardening security measures and performance validation.

  • NFR-SEC-05: Rate limiting and abuse protection on auth endpoints.
  • NFR-PERF-03: Load testing for 50-100 concurrent participants.
  • NFR-DEPLOY-02: Hardware sizing guide documentation.
Phase 6: Integration, UAT & Documentation
3-4 Weeks Final Stage

End-to-end testing, bug fixing, and final documentation handoff.

  • End-to-end testing across all SRS functional flows.
  • Browser and device compatibility matrix testing.
  • Delivery of installation and admin/user guides.