I’m seeing many forum topics being closed quickly. It feels like some discussions are just not welcome here, despite no obvious violation of forum rules etc. Just one example is discussion of release schedules - just a short answer that when done they are posted on the blog (which I already knew, and that wasn’t my question), and topic immediately closed without further explanation. One reason I asked was that I’d like to know how much time I have left to test a bugfix before submitting a PR - want it well tested (not “move fast and break things”), but don’t want to miss the deadline for the next release. I do understand there might be no good answer yet, but even just a rough estimate (what is planned, even if subject to change) would have been a much more friendly answer than immediately closing the topic. I’m also on other forums where closing topics does happen too, but is done much more sparingly and not automatically.
I closed the post you’re complaining about. It wasn’t automatically closed. It was a single sentence “There have been quite a lot of changes in the sagitta branch since 1.4.0 - is the 1.4.1 release coming soon?”
In my experience moderating open-source forums/communities, it’s standard procedure to delete “Excuse me, *I* need to know when the next release is coming because <reasons>” posts. Which isn’t what I did here, I just locked it. I realise you’ve since edited it, and posted this complaint, to provide context. I moderated it as the single sentence it was at the time.
Otherwise in my experience these posts start out as “Excuse me I need to know because <reasons>” but soon devolve into “C’mon guys it’s been X months since you released Y, what’s the hold up, there’s this urgent patch/fix/feature I need, stop delaying.” I’m sure I don’t need to explain why this isn’t acceptable.
Honestly I’ll probably end up having to lock this thread as well, because I know it’s just going to now turn into everyone politely telling me just how wrong I was, and providing justification why their post shouldn’t have been locked.
It can be a pretty thankless task moderating forums, deleting the spam, looking at all the spam accounts trying to sign up and manually approving the few people that aren’t spammers. Realising you’ve accidentally approved a spammer, having to go back and clean up the mess.
Tim
Why not admit that this was a bad moderation from your side and reopen that thread?
Threatening to close this thread aswell is just as showcase on a forum going downhill when moderators starts to have some kind of personal vendetta against users because the moderator have had a bad day for whatever reason.
Honestly I’ll probably end up having to lock this thread as well
My experience from moderating forums is that you dont lock and/or delete posts just because somebody asked you about something.
The question is valid - there have been some time since 1.4.0 was released, alot of changes have since passed through and no info about of any future release of 1.4.1 is available at the blog - which gives, what are the plans? Can the community and paid customers expect an update for lets say before end of year? Or is the plan to release 1.5.0 as the next LTS release so dont hold your breath on any 1.4.1 update any time soon?
With Ubuntu we know a new release is scheduled every 6 month (in april (xx.04) and in october (xx.10)) with betas available along the road but with VyOS its like some of the VyOS people gets offended if something about VyOS itself is being asked or criticized?
And thats a big red flag for me… because I really like VyOS as a concept with latest Debian as a base, a readonly filesystem using overlay to have a persistent storage, single config through vyos-configd, FRR as routing backend etc.
So @tjh, you were right; all ■■■■ storm just moved to this post instead of being in that one that locked.
Good job!
Why not close the whole forum while you are at it?
This way you wont have to deal with questions regarding VyOS at all.
Seems like unfortunately the history is repeating itself…
Originally, Vyatta used an open core model: open-source and freely-available Vyatta Core and Vyatta Subscription Edition with proprietary addons. In its last months before getting acquired by Brocade, Vyatta inc. quietly discontinued the open-source version, deleted the “Hackers” section of the forum with all its content (including a lot of community-made patches they never merged), and finally took down the git repo server with its source code.
If you don´t like something, you are welcome to leave.
As simple as that
Please dont be that guy have you seen @Apachez contributions in this forum posts ,he genuinely helps people here…
I miss the old days when it used to be “if you don’t like something, you are welcome to help improving it” - or the classic Cathedral vs Bazaar thing.
As for the fix I can of course apply it myself and run my local fork rebuilt from sources, but I thought it would be better if it was merged and could help someone else as well.
My closed topic was just one example, but not the only one (many recent threads locked, much more than say on the MikroTik or UBNT forums) - it’s a more general trend and I’m not alone in seeing it. Sorry for any “storm” I may have caused, and for not providing enough context initially (would provide it if asked, no problem).
Wow, just wow…
Imagine saying the same thing to residents of a country being invaded.
“If you dont like being bombed at then you are welcome to leave - as simple as that”.
No I dont have any plans to leave - Im more in favour of “if you don’t like something, you are welcome to help improving it”…
And Im a bit worried about the hostality towards the community currently seen from some of the moderators/maintainers of VyOS.
Hopefully its just a matter of having a bad day and not something more sinister going on.
please come down, this toxic writing helps no one, it kills Vyos forum.
since April there were no new changelogs for version 1.5 or 1.4, that is normal that people ask whats going on.
I have to leave now this forum, my work has ended with Vyos.
The forum has developed badly in the last few months. That’s not so nice. I wish you continued success with Vyos
The auto-locking started relatively recently (about April 2024), many older threads are still open and that’s a good thing, sometimes you want to go back to add to some older discussion, not all become outdated quickly. It would be nice if at least the non-controversial topics (not about building from source etc. - point taken, will continue on github not here) could be exempt from auto-locking.
Also, and this is where I don’t have much hope left, but asking politely anyway - how about a ceasefire in the form on restoring access to those people who were banned (on this forum and on the github org), this benefits no one really and would show that some open source spirit is still here. I’m still open for discussion even though I got many harsh words (too harsh to make public), but let’s try to forget about that, stop fighting and work together for the common good, I’m sure we all still share some values. Thank you.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.