Why Isn't the Skywarn Operators Console Open Source?

It's a question we get fairly often, and it's a fair one to ask. A lot of the tools our community relies on are open source, and there are good reasons people default to expecting that. So we wanted to take a minute and explain where we're coming from on this, rather than just leaving it as an unanswered FAQ.

We're not going anywhere

One of the biggest arguments for open-sourcing a project is continuity — if the developer disappears, the community can keep the software alive. We get it, and we respect it. But that's not a concern here. Wilmington Skywarn has no plans to step away from this project, and there's no "hit by a bus" clause we're trying to write into the software's future and there are several developers involved. We're actively developing, releasing, and supporting the Console, and that's not changing. It is not our ego, or search for fame, free stuff, recognition or hyper ownership driving this. We just want to make sure it is serving the intended purpose, SkyWarn and any other operations needing these functions.

We want the Console entrenched in the Skywarn community first

Before anything else changes about how this project is run, we want the Skywarn Operators Console to be genuinely entrenched in the storm spotter and amateur radio community — something spotters and nets rely on and trust, with a track record behind it. That's our priority right now: building something solid, well-supported, and widely used. Decisions about the project's structure down the road will be made with that foundation already in place, not before it.

Add-ins are welcome — profiting off them isn't

We know one of the appeals of open source is the ability to build on top of a project. We don't want to shut that door. If you've got an idea for an add-in, or you want to build one yourself, we genuinely want to hear about it. Extending what the Console can do for the community is a good thing, and we're happy to work with people who want to contribute that way.

What we're not interested in is people using the platform as a way to make money off the Skywarn community — charging for add-ins, gating features behind a paywall, that sort of thing. This project exists to serve spotters and hams, not to become a storefront. Any add-in development happens at no cost to the community, we would be very interested in.

Yes, we know that the Boondock Echo Transcriptions cost money if you use the Boondock EDGE API, you can keep it at "Local Transcriptions" (The Default), it is free. That was one thing we did work on with BoonDock Echo to make sure it wasn't going to go against what our intent was. Yes, Boondock-API is faster and more accurate, they are a business and need it not to cost them money, but the option is there to run it local for free.

If you've got an idea, reach out. We'd rather have that conversation than have someone quietly try to monetize something built on top of free software.

We're free, and we don't take cash donations

The Skywarn Operators Console is, and will remain, completely free. We don't accept cash donations for it, and that's intentional — we don't want this project to be about money in either direction. It's built to support the community, not to generate income, and keeping it that way keeps our motivations clean and simple.

Bottom line

Closed-source doesn't mean closed-off. It means we're keeping control over the core software while it grows into something the community can depend on, while still leaving the door open for people who want to contribute ideas and add-ins in good faith. As the project matures and its place in the community solidifies, some of these decisions may get revisited — but for now, this is the approach that makes the most sense.

As always, if you've got questions, ideas, or feedback, we want to hear it. Thanks for using and supporting the Skywarn Operators Console.

73, Wilmington Skywarn