Development will progress incrementally, according to the available capabilities & resources. This roadmap should therefore not be understood as a fixed schedule or a rigid development plan. It is a living roadmap, which will be continuously reviewed and adapted as the project evolves, new ideas & requirements emerge, and contributions become available.
Nevertheless, maintaining a global view of the roadmap is valuable. It helps us understand where we are, what has already been accomplished, and what the next steps are. It also provides a framework for organizing the work ahead, establishing priorities [See MoSCoW methodology], identifying dependencies, and coordinating the different tasks involved in building the platform. [Canvas deck]
The roadmap is also intended to make the development process easier to understand for anyone interested in the project: what is being built, in what order, and where contributions may be most useful. This is an open and collaborative effort, and everyone interested in contributing to the construction and evolution of the platform is welcome to join.
Legend
✅ Completed 🚧 In progress ⏳ Pending ❌ Cancelled ⚠️ Attention1) Foundation and Preparation
Back to topa.- Core Development Environment
- ✅ Preparation of the core development VM and development environment.
b.- Multi-domain and Multilingual Support
- ✅ Implementation of the initial multi-domain architecture.
- ✅ Preparation of multilingual support.
c.- Life-cycle
- ⏳ Load source to gitlab
- ⏳ Establish and document a Development _> Staging -> Prod process
d.- Panorama (NMS)
- 🚧 Deployment for development & testing
- 🚧 Pilot NMS for current beta countries & sites. Currently with Zabbix:
e.- Initial Data Model
- 🚧 Design and preparation of the initial database and data model.
f.- Identity Management (IdM)
- 🚧 Preparation of the identity management architecture and basic functionality.
g.- IP Address Management (IPAM)
- ⏳Preparation of the IPAM architecture and basic functionality.
h.- Initial Core Functionality
✅ Network Zones and Navigation
- ✅ Breadcrumb navigation and representation of the network's geographical structure.
🚧 Access Control and Permissions
- 🚧 Definition and implementation of the initial access control and permissions model.
Back to top
2) Consolidation of the Legacy guifi.net Platform (Drupal 6)
The objective of this phase is to progressively incorporate into the new platform the information and essential functionality currently provided by the legacy guifi.net Drupal 6 platform.
Phase will be completed when minimum feature set is complete enough to deliver all the features available at the legacy system, so commons can become the live platform, and the legacy set archive/read-only. In the meantime will co-exist in parallel.
a.- Support for Core Legacy Functionality
- Identification of the essential functionality that must be preserved or redesigned.
- Progressive implementation of the required functionality in the new platform.
b.- Identity Migration
- Mapping of legacy identities to the new identity model.
- Migration and consolidation of user and organizational identities.
c.- Data Migration
- Definition of mappings between the legacy and new data models.
- Progressive migration, validation, and consolidation of existing network data.
Back to top
3) Consolidation of networks.guifi.net (Drupal 9)
The functionality and data currently provided through networks.guifi.net will be reviewed and progressively integrated into the common platform.
This phase will include the identification of functionality that should be preserved, redesigned, merged with existing components, or replaced by the new platform architecture.
Back to top
4) Further Development
Additional development phases will be defined and prioritized as the previous stages progress and the requirements of the platform become clearer.
The roadmap will continue to evolve accordingly, incorporating new functionality, integrations, migration needs, and contributions from the community.
Legend
✅ Completed 🚧 In progress ⏳ Pending ❌ Cancelled ⚠️ Attention