On Mon, Jul 1, 2013 at 6:11 PM, Chris Ess <[email protected]> wrote:
> On 7/1/2013 3:26 PM, Matt Simmons wrote: > > 3) Lack of codification > > Several professions have established a Body of Knowledge(BoK). > > Interestingly enough, there IS a System Administration Body of > > Knowledge. Geoff Halprin (a member of USENIX and founder of LOPSA) > > compiled it circa 1997. Several of the people reading this email already > > know this fact, and I would estimate that they are probably 99% of the > > system administrators in the world who are aware of it. Personally, I > > don't know if it was complete at the time of its compilation. I know > > that it has not been maintained by the profession, or added to by any > > groups, and I'm unsure as to exactly which group should be the party to > > maintain it. > > I think Aleksey Tsalolikhin wanted to do something with SA-BOK. See > https://lopsa.org/content/sabok (As an aside, does anyone know of a > mirror for SA-BOK? The links at that URL don't appear to be working.) > > If LOPSA shouldn't maintain something like SA-BOK, who would? > this sounds like something has finally really hit the sweet spot of my interest in #sysadmin and my love for documentation. Aleksey, I'd love to help expand/update this, collate everyone's interest and links, and keep it up to date. I think this would get LOPSA on the road to being more respected and having more to offer our profession, at a minimum. > > > Other things I think LOPSA could do: > > * Will Dennis mentioned a recommended reading list, which I think is a > great idea. > > * We could also document practices and, if possible, explain why and > when they're good and why and when they're bad. If we could document > this, we could possibly get to the point of having a system > administration pattern language, or at least relatively uniform pattern > terminology. (This might fall under SA-BOK. SWEBOK looks awfully > process-oriented. Maybe it's because I'm tired but I can't read it for > very long before my eyes glaze over.) > *seriously* interested in documenting best practices. Maybe we could set up a working group to throw together an outline, expand it, grow the explanations of good and bad practices. > > * We could maintain a curated collection of experiences or thoughts. > This is inspired by Lawrence Chen's "Knowledge lost in time" email from > about a week ago. Each of us probably knows something obscure that, > some day, might be useful to someone else. (Yes, this sounds an awful > lot like a blog, doesn't it? In theory, if someone else is curating it, > it might be easier for people to contribute.) I'd say we should set up an obscure thoughts/knowledge wiki, making it easy for everyone to contribue whatever tidbit, whenever the moment struck. ---pam
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
