If everyone had the priorities that you described, no volunteering would ever
happen :-)
There are probably a bunch of people who could help with specific tasks or who
could fill in for someone else, but how do they find out what needs to be done?
How much work is needed to get them access to
On Wed, Feb 25, 2015 at 4:21 PM, Doug Hughes wrote:
>
> (today) to contribute a new description. You could possibly pull some
> nuggets from this with respect to communication skills, but all references
> to technology are woefully dated.
>
> e.g. ability to port C programs from one environment to
Maybe we should turn this around. I don't think we have a project
management problem, I think we have a doer problem. So it makes more sense
to wedge someone into the org chart at the bottom, who can be thrown into
any project that's currently short handed.
Manpower is a resource and LOPSA is comp
On Wed, Feb 25, 2015 at 5:21 PM, Doug Hughes wrote:
>
>
> e.g. ability to port C programs from one environment to another.
>
>
s/C/perl or python//
SHIP IT!
___
Discuss mailing list
Discuss@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listin
On Tue, 24 Feb 2015, Craig Constantine wrote:
(disclosure: I'm not a proj mgr, I am not good at pm, and I do not want to be
a pm for lopsa.)
The more I try to help actually do things, the more I'm working with other
volunteers who seem to be very over-worked. (Mind you, it seems they bring
t
IMHO, the old sage descriptions are quite dated (see another recent thread
in the archives relating planning for sysadmin/machine ratios that has some
intersection) and responsibilities have expanded beyond that, but also
changed significantly in some ways. Unfortunately, I'm not helpful enough
(to
Our current relationships notwithstanding, what was wrong with the old SAGE job
descriptions, or andy LISA materials we have on the matter. This has been
hammered out ad-nauseum years ago.
> On Feb 25, 2015, at 4:15 PM, Dan Ritter wrote:
>
> On Wed, Feb 25, 2015 at 02:45:26PM -0600, Mark Hon
On Wed, Feb 25, 2015 at 02:45:26PM -0600, Mark Honomichl wrote:
> As a new board member, one of the tasks that I have taken on is to create a
> definition of what a System Administrator is, especially in the context of
> LOPSA, so I am curious to here what the membership thinks a SysAdmin is.
> You
Mark,
In the epilogue of The Practice of System and Network Administration you
may find a pretty good definition (actually frustrating):
“Makes things work."
Beyond that story, I liked that the whole book gave a really broad
definition of sysadmin.
Cheers
Jean-Marie
On Wed, Feb 25, 2015 at 5:
As a new board member, one of the tasks that I have taken on is to create a
definition of what a System Administrator is, especially in the context of
LOPSA, so I am curious to here what the membership thinks a SysAdmin is.
You can respond on the list, directly to my inbox, or via Reddit (
http://w
10 matches
Mail list logo
