Timeline for Will/Should Serverfault be dropping the "networking support" in the upcoming future?
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 22, 2013 at 4:19 | comment | added | Scott Pack | @voretaq7: The cross-posting problem is tricksome to be sure. Ideally the entire network would be one nebulous glob with some kind of meta tagging and dynamic views to include what's relevant. For instance, even with grumbles of Sec.SE being a complete overlap of SF it's really more a subset of SF, SO, DBA, WebApp, Programmers, NetEng, RE, some others, and some of it's own. With SEI doing the Area51 model they've officially blessed and encourage fragmentation. It's definitely a hard thing for us to figure out how to work in. | |
May 22, 2013 at 3:39 | comment | added | voretaq7 Mod | @ScottPack The main problem I have is that by fragmenting the sites Server Fault is largely deprived of the security perspectives we used to have (and security.SE can lean toward the Ivory Tower, lacking the real world practicality that Server Fault's community could bring -- though that's less of an issue from my casual perusing of security.SE). In a way it encourages cross-posting even though cross-posting is officially frowned upon: If you need more than one viewpoint you need to ask on more than one site... | |
May 21, 2013 at 3:50 | comment | added | Chris S Mod | @gWaldo The only relatively minor reservation I have with that is that theoretical questions are off-topic on SF across the board (though we do entertain them frequently). If we had views and opened SF to theoretical that would allow all the fragments to be complete overlap with SF. Doing so would require better input filtering however, as we already attract enough BS from those who ignore the FAQ. | |
May 16, 2013 at 19:36 | comment | added | Scott Pack | @gWaldo: I waffle quite a lot on that. As a security guy with a systems background I like being able to decide whose viewpoint I can get. Due to the differing responsibilities of the jobs a dedicated security person may give a very different answer from a dedicated systems admin to the same question. Having the different sites allows us to explicitly seek different expertises. However, it also means that people with multiple roles, or multiple interests, have to spread themselves around. Either way you slice it the solutions are non-ideal. | |
May 16, 2013 at 18:50 | comment | added | gWaldo | I hate the site fragmentation. Rather, I hate that they're completely separate sites. If they were, say, views of the same question pool, I could dig that... | |
May 15, 2013 at 16:41 | comment | added | Chris S Mod | @pauska They might not attract attention from the "regular" SF crowd, but that only seems to be true as Network Administrators seem to avoid SF as if they're off-topic here. I really don't understand the dynamic, but if a working site has the numbers who am I to call them out for being cliquey. | |
May 15, 2013 at 11:42 | comment | added | Scott Pack | @pauska That fits with my hope. It'll be worth watching to see how the public beta turns out. | |
May 15, 2013 at 6:56 | comment | added | pauska | I'm in the beta, and trust me - 99% of these questions would never attract any attention on ServerFault. We're talking about pretty high-end networking questions regarding unified fabric, MPLS and so on. Regular sysadmins almost never do the field work on those subjects. | |
May 14, 2013 at 16:26 | comment | added | Scott Pack | @ChrisS: Not nearly as sexy. | |
May 14, 2013 at 15:51 | comment | added | Chris S Mod | Why not "Ignore, Retry, Fail?" | |
May 14, 2013 at 15:45 | comment | added | Scott Pack | @ChrisS: Then I propose we rename the site to be Guru Meditation. | |
May 14, 2013 at 15:19 | comment | added | Chris S Mod | The name is a common error code from back in the day - it's the same source as "Stack Overflow". Unfortunately, few people are still familiar with it - lost in translation I guess. | |
May 14, 2013 at 14:56 | history | answered | Scott Pack | CC BY-SA 3.0 |