New packages subsection for Squid-related stuff
-
I have no problem with a separate board, but this wouldn't even be an issue if the Squid packages were in any shape to use when 2.2 was released. A lot of testing and some work from Marcello has largely fixed the teething issues, so I would expect the screams of agony to die down soon enough.
-
What seems better:
- Child board per specific package (each squid variant gets its own, that would be about 4 potential child boards)
- Child board for general package (all squid packages go into one child board)
Well, I think 1/ is an overkill, plus people will fail to use the proper section anyway. :D
Also, snort/suricata would be worth a subsection I guess.
-
I'd say one for squid (and its related bits like lightsquid, squidGuard, etc.), one for snort/suricata (perhaps "IDS/IPS Packages"), but beyond that I'm not sure any warrant a package-specific board. Maybe one for "network monitoring" which could include a group of packages such as ntopng, bandwidthd, etc.
-
It seems child boards based on package function is the way to go.
-
I'd say one for squid (and its related bits like lightsquid, squidGuard, etc.), one for snort/suricata (perhaps "IDS/IPS Packages"), but beyond that I'm not sure any warrant a package-specific board.
+1
-
I created the two categories, let me know if I messed something up.
-
Uhm… can we start using it, please? :D (Moving the recent threads there would be nice, but definitely at least when I report a misplaced thread, I'd appreciate to get it moved to the new subsections when it belongs there. Like, this one: https://forum.pfsense.org/index.php?topic=90078.0)
TIA :D
-
I moved some stickies and posts and created a new announcement sticky in packages about the new child boards. It will probably take some time for full adoption.
-
Cool, thanks ;)
-
I'd second this proposal for all packages.
I agree 100% with:
I for one would prefer to not wade through the tons of posts
For example, now I see there is a package update for freeradius. I like to check first if something is broken before I update, so her comes the cumbersome process of having to wade and wade and wade.
It makes much sense to give each package its own subsection, not only for Squid, just like the main layout of this forum is, where each 'sub system' of pfSense has its own section too.
I'd even help you if it is too much work:
1. I'll create the sub sections
2. I'll mass move topics to their own new sub section via 'search in title' only (provided this forum allows for that mass maintenance stuff of course; I know IPB does).If you want me to waste some time on it, you'll need to temporary assign me to the appropriate moderators group, of course. Now here comes trust :P
( ;D )
-
@Mr.:
For example, now I see there is a package update for freeradius. I like to check first if something is broken before I update, so her comes the cumbersome process of having to wade and wade and wade.
It makes much sense to give each package its own subsection, not only for Squid, just like the main layout of this forum is, where each 'sub system' of pfSense has its own section too.
The current system of "sub-board by function" seems to be working well for now and has reduced the amount of threads to wade through considerably. If there is enough demand and it makes sense we could add an "Authentication" packages sub-board or some other appropriate name.
My worry with the "every package gets a sub-board" system is the maintenance and usability reasons, we already have a few people that don't use the new system (although it is catching on) and we have to move their threads.
You can also report threads that are out of place, with the subcategory you think it belongs to in the report description. We try and catch them as they pop up, but this helps :)
