Skip to content

[gsoc25] Added blog post for firmware upgrader project#134

Merged
nemesifier merged 6 commits intomasterfrom
gsoc/firmware-upgrader
Sep 27, 2025
Merged

[gsoc25] Added blog post for firmware upgrader project#134
nemesifier merged 6 commits intomasterfrom
gsoc/firmware-upgrader

Conversation

@youhaveme9
Copy link
Copy Markdown
Member

No description provided.

@nemesifier nemesifier changed the title [docs] Added blog post for firmware upgrader project gsoc-2025 [gsoc25] Added blog post for firmware upgrader project Sep 25, 2025
Copy link
Copy Markdown
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On track, see my comments below.

I'd suggest to try removing some bloat and be more direct in some passages, I found a number of typos and broken syntax/formatting, please read and review the text line by line in full making sure these issues are fixed.


Over the past three months, I had the opportunity to work on my Google
Summer of Code project under the guidance of Federico Capoano (nemesifier)
<https://github.com/nemesifier>, Aryaman (Aryamanz29)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link syntax is not right

features address common pain points that network administrators face:
uncertainty about upgrade progress, inability to stop problematic
upgrades, and lack of granular control over which devices to upgrade in
large deployments.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are mentioning the key pain points, I think using a list would allow faster reading. I'd try to reduce the amount of words. Less is more.


The solution uses WebSocket connections to deliver real-time progress
updates directly to the admin interface, eliminating the need for manual
page refreshes. Progress tracking is implemented at multiple levels - from
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's avoid hyphens which are too chatgpty, use commas instead.


The mass upgrade filtering system integrates with OpenWISP's existing
device group and location management, allowing administrators to target
specific subsets of devices with surgical precision.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After reading this section I think we'd be better of to moving this info to each feature subsection below. Let's go straight to the point and avoid sections without images as people don't like blobs of texts.

targeting, such as "Access Points in Building A" or "Edge devices in the
European region".

**Use Cases**: - **Staged Rollouts**: Upgrade devices gradually by
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

You can follow the development process and explore the implementation
details in the following pull requests:

- `how upgrade progress for single upgrade operations in real time
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was it meant to be show?

Current state
-------------

We are maintaining the ``gsoc25`` branch of openwisp-firmware-upgrader
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link the repo please.

My Experience
-------------

Working on the OpenWISP firmware upgrader during GSoC has been an
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Working on the OpenWISP firmware upgrader during GSoC has been an
Working on `OpenWISP Firmware Upgrader <https://github.com/openwisp/openwisp-firmware-upgrader>`__ during GSoC has been an

- `Allow cancelling firmware upgrade operations
<https://github.com/openwisp/openwisp-firmware-upgrader/pull/329>`_
- `Allow mass upgrade by their group or location
<https://github.com/openwisp/openwisp-firmware-upgrader/pull/343>`_
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's mention the docs updates too

Copy link
Copy Markdown
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@youhaveme9 is this supposed to be a list?

Image

I ask you to fully read the blog post line by line and check the formatting and the output

The header image you are proposing is inconsistent with what we're using, we need to maintain consistency as always. I will give you instructions in the chat.

Please take care of the QA checks, running yarn prettify should be enough.

The firmware upgrader enhancements address key pain points network
administrators face:

- **Uncertainty about upgrade progress** - No real-time feedback
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Punctuation is weird:

Suggested change
- **Uncertainty about upgrade progress** - No real-time feedback
- **Uncertainty about upgrade progress**: No real-time feedback.

Please apply the same suggestion to the whole article.

.. image:: {static}/images/blog/gsoc25/firmware-upgrader/mass-upgrade-by-group-and-location.gif
:alt: Mass Upgrade by Group and Location

Mass upgrade operations now support precise device targeting through
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please let's link the PRs in their respective sections. It's ok to also have a summary at the end.

Not sure if other blog posts did the same, I will check, but it makes it easier for readers to quickly find the github PR while reading about the feature.

Roshan Kumar and others added 3 commits September 27, 2025 16:07
@nemesifier nemesifier merged commit ad823eb into master Sep 27, 2025
2 checks passed
@nemesifier nemesifier deleted the gsoc/firmware-upgrader branch February 4, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

2 participants