Skip to content

Commit 418dc2b

Browse files
committed
[blog] Roadmap to 2030: The Horizon of Network Management
1 parent 14b371a commit 418dc2b

File tree

2 files changed

+71
-0
lines changed

2 files changed

+71
-0
lines changed

content/blog/roadmap-2030.rst

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
Roadmap to 2030: The Horizon of Network Management
2+
==================================================
3+
4+
:date: 2025-12-29
5+
:author: Federico Capoano
6+
:category: news
7+
:tags: roadmap
8+
:lang: en
9+
:image_url: https://openwisp.org/images/blog/roadmap.webp
10+
:image_width: 713
11+
:image_height: 306
12+
13+
.. image:: {static}/images/blog/roadmap.webp
14+
:alt: Development Roadmap (2030)
15+
16+
For the past 13 years, I have had the privilege of contributing to
17+
OpenWISP and growing alongside this community. During this time, I have
18+
continuously collected feedback from users, contributors, and partners,
19+
reflecting on the long-term direction required to keep open-source network
20+
management at the cutting edge.
21+
22+
I have synthesized these years of notes and community dialogue into a
23+
structured vision for the coming years: the `Roadmap to 2030
24+
<https://openwisp.io/docs/dev/general/roadmap-2030.html>`_.
25+
26+
This roadmap outlines the technical and strategic paths I intend to pursue
27+
to ensure OpenWISP remains a capable, accessible, and versatile system for
28+
modern, heterogeneous networking environments.
29+
30+
Key Strategic Themes
31+
--------------------
32+
33+
1. **Frictionless deployment**: Move toward a day-one ready approach by
34+
simplifying installation workflows and providing clear, sensible
35+
default configurations that work out of the box.
36+
2. **Refined user experience**: Improve the interface of core modules so
37+
that frequent operations, such as device onboarding, configuration,
38+
monitoring, and firmware upgrades, are intuitive and accessible, even
39+
for users with limited technical background.
40+
3. **Community-driven feature parity**: Address long-standing feature
41+
requests from the community and reduce functional gaps compared to
42+
proprietary network management solutions.
43+
4. **Ecosystem agnosticism**: Expand support beyond OpenWrt by improving
44+
compatibility with other operating systems and adopting standard
45+
protocols such as NETCONF, YANG, TR-069, and TR-369. This will allow
46+
OpenWISP to manage a wider range of hardware and software platforms,
47+
making it useful to a larger audience.
48+
49+
Help Us Build the Future
50+
------------------------
51+
52+
While this roadmap represents my personal vision for the project, it can
53+
only be realized through collective effort. We are actively seeking:
54+
55+
- **Technical contributions**: Help us implement these architectural
56+
changes, `start contributing
57+
<https://openwisp.io/docs/dev/developer/contributing.html>`_!
58+
- **Funding and sponsorship**: Financial support is vital to accelerate
59+
development and ensure long-term sustainability. Consider `sponsoring
60+
OpenWISP <https://openwisp.org/sponsorship/>`_.
61+
- **Community feedback**: I invite you to read the `full roadmap document
62+
<https://openwisp.io/docs/dev/general/roadmap-2030.html>`_ and share
63+
your thoughts in the dedicated `GitHub Discussions thread
64+
<https://github.com/orgs/openwisp/discussions/1183>`_ to help refine
65+
these goals.
66+
67+
**Read the full document here:** `Roadmap to 2030
68+
<https://openwisp.io/docs/dev/general/roadmap-2030.html>`_.
69+
70+
I welcome your feedback to help shape the roadmap and make this vision a
71+
reality!

content/images/blog/roadmap.webp

20.5 KB
Loading

0 commit comments

Comments
 (0)