@Discourse I would like to thank you for supporting #opensource. You have helped people connect around #opennms with your "Free Hosting for Open Source" program since 4th December 2018. Thank you very much!

The brick we bought at the Chatham County Library in Pittsboro is faded, but still there, much like the project. #opennms

I certainly don't have all the answers. I don't know that I even have a good answer.

But I *do* know that pissing away the community and thinking only about how to extract value from the codebase without thinking about what sustains a project like #OpenNMS is going to Capital-F Fail.

Not only that, but for the 6 months before I left, NantHealth didn't manage to execute on *anything* that moved the needle, and they haven't done it in the almost-6 months *since*.

All they're doing is bleeding.

Some of this is, of course, out of spite. *Righteous* spite, IMHO, but spite nonetheless.

And some of it is out of actually caring about this thing I put 2 decades into that is being destroyed by someone who doesn't understand it, and hoping the example can be useful to others in a similar situation in the future.

#OpenNMS

Also, can I just say how much I love that I managed to not have to sign any NDA, non-disparagement, or PIPA type stuff?

I feel like in a lot of these cases where a commercial entity is defacto owner of an #OpenSource piece of software, people aren't able to talk about the gritty details for various reasons.

I have the luxury of not being forced to be silent, and I have the hubris and/or lack of self-preservation to say "fuck it" and talk about them as openly as I can.

#OpenNMS #FLOSS #FOSS

That said, the glory of open-source software is that even if NantHealth manages to completely destroy #OpenNMS the company, the code lives on.

OpenNMS has a lot of code debt after nearly 25 years of development, but there’s a *ton* of good stuff in there too.

I'm sure someone with the willingness to do some major surgery and refocusing could transform it into something useful. It has one of the only open-source engines for handling flow data, and it still has a best-in-clase SNMP engine.

Just had a thought, as I watch OpenNMS's parent company slowly ruin them.

#OpenNMS was started by former HP #OpenView consultants who were tired of having to work around shitty proprietary monitoring tools and said, “surely we can do better than this!" and set out to make their own.

In 2015, HP spun off their enterprise business into HPE. HPE eventually became a customer of OpenNMS.

So really, we won! We completed our mission. Anything remaining after is just rolling credits.

RIP

I wrote a blog post for the first time in a billion years about the iTerm2 AI fiasco (but not *really* about the iTerm2 AI fiasco).

https://dev.to/rangerrick/iterm2-and-the-gap-between-developers-and-users-2g1h

#AI #iTerm2 #floss #OpenSource #OpenNMS #NetBox #NetBoxLabs

So thank you, again, to anyone who has been involved with OpenNMS along the way. You have all been a huge part of my life, and a significant portion of my professional career. I will still be around, just not officially. Maybe I’ll even still make a pull request or two, you never know. 😅

#FOSS #OpenNMS

This somehow turned out more sappy *and* formal than I intended, but it’s true. I’m excited that Netbox appears to be doing things right, letting the open-source project thrive on its own terms while building a business around it, much like Grafana. (In fact a co-founder of Grafana is on the board.)

#FOSS #OpenNMS

It’s weird and scary to be moving on after such a long time with OpenNMS, but it’s exciting to join a company that’s taking me back closer to my roots, focusing on providing support and integrations guided by the community’s needs.

#FOSS #OpenNMS

All of this is to say that I may be leaving a company, but I’m still going to be part of many online communities. And later this week I am joining Netbox Labs, where I’ll be working on a variety of things around providing enterprise support for this growing open-source project.

#FOSS #OpenNMS

I’ve watched #FOSS go from a thing weird hobbyists do all the way through becoming the entire foundation of modern computing, and I’ve been lucky to be able to call open-source development my job for nearly all of that time.

I’ve met countless amazing folks across the spectrum of community, coworkers, and everything in-between, plenty of whom are still friends I keep in touch with and all of whom were a huge part of making work rewarding and fun.

#OpenNMS

It is hard to put into words how weird it is that today is my last day at #OpenNMS. I have been with this incarnation of the company that maintains it since 2007, and I have been in this codebase one way or another since being the first technical hire at Oculan, the startup that first developed it.

#FOSS

@RangerRick wow. You posting about #opennms has been a regular feature previously in my twitter feed and now mastodon timeline. Gonna be strange to not see that anymore.
A bit sad I couldn't make it happen that you found a role at my $dayjob but excited for you nonetheless.

Wow, Ivory tells me I made this thread 137 days ago.

Monday is my last day at #OpenNMS and wow does it feel weird. I’m excited to go where I’m going next (more soon) but even though I’m not the last of the old guard to leave, I’m the one who has been with the codebase the longest. It feels a little like shutting off the lights and closing the door.

So much of my life, so many memories, spent with a bunch of nerds doing fun stuff with networking.

The decision to go was the right one though.

Damn, 12k commits to the #OpenNMS GitHub repo. That's a lot of commits.

And it doesn't look like it counts the ones I did in SVN before it got imported. And the ones I did in CVS before that got imported to SVN. 😅

#FOSS

#OpenNMS #Vulnerabilities: Securing Code against Attackers’ Unexpected Ways

// by @SonarResearch

https://www.sonarsource.com/blog/opennms-vulnerabilities-securing-code-against-attackers-unexpected-ways/