What if LOPSA started generating documents akin to the RFC/STD documents? The board could commission a few specific documents -- for example, charge a small committee with creating a BOK reading list document. Documents specifically approved by the board would be our standards docs. Members could freely submit RFC documents on topics of their choosing -- for example, someone might write a best practice document about backups. There'd be some sort of minimal peer review scheme; But basically it would have a low barrier to entry to get it going.
The documents are then published in a public library section on the web site (or perhaps even a separate web site designed just for this purpose.) That way everyone, everywhere, can start using them and referring to them. So it's a grass-roots "write it and it will become the professional standard" without our trying to give birth to one monolithic product that attempts to define the profession. --Craig Constantine, http://constantine.name On Jul 9, 2013, at 8:51 AM, Will Dennis <[email protected]> wrote: On Monday, July 08, 2013 11:17 PM, Atom Powers said: “Perhaps if LOPSA could sell itself as the authoritative place for professional systems administration information we could built the mind-share that builds membership that builds the organization.” ^ | THIS. _______________________________________________ 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/ _______________________________________________ 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/
