On Thu, Apr 05, 2012 at 03:19:13PM +1000, donna ashelford wrote:
> When people sign up to lopsa, don't we sign up to follow code of ethics
> among other things?
Actually I don't think we do. At least, not before it starts asking for
payment information. Maybe it happens after that?
On the other h
Evan Pettrey wrote:
> "What are the primary differentiators between a sys admin with a senior
> level skillset and one with a junior level skillset?"
Putting on my "Hi I'm Tom Limoncelli" hat, I suggest:
http://static.usenix.org/multimedia/lisa10moskowitz/
http://static.usenix.org/events
Carolyn Rowland wrote:
> Is there a way that LOPSA could have one meetup site and all of
> these local meetups could fall under that.
> . . .
> The benefit is, if you go to a strange city, you can look up other
> LOPSA events instead of having to know the secret URL to each LOPSA
> group's meetup p
Is anyone using continuous build or continuous integration tools --
stuff like Jenkins or Bamboo or CruiseControl [1] -- for sysadmin tasks?
If so, can you say what kinds of tasks you're doing with these tools?
I'm a big fan of Jenkins, I use it every day, and I work with / use /
help manage a few
Tom Limoncelli wrote:
> What is Jenkins' security model?
In addition to what Mike Devlin already wrote, it's
worth noting that a very typical way of using Jenkins is to check out
code from a repository (it supports most of the common ones like git and
subversion) then run that code. This lets you
Derek Balling wrote:
> I'm not looking at the page, but are vacant board positions not listed on
> the site as "Vacant, Term ending "?
>
> If not, they should be.
If you scroll down a bit you'll see it says "Re-election year" beside
each candidates name.
__
With LISA '13 [1] right around the corner, I got to thinking about how
"the cool kids" prefer to exchange contact information in a face-to-face
setting. I'd appreciate it if you'd please take a minute or two to
answer a few questions. Again, this is specifically about face-to-face
interactions, typ
On Mon, Oct 28, 2013 at 07:47:55AM -0700, Craig Cook wrote:
> Does LISA have a code-of-conduct policy?
Yes: https://www.usenix.org/conferences/harassment-policy ; I think
there's another one more specific to conferences but I can't find it
right now.
> If not, should one be created?
That's a USE
While reading an almost-recent issue of "Communications of the ACM," I
found a reference to Heilmeier's Catechism [1][2]; I think it's
appropriate to the discussion.
Heilmeier's Catechism
-
A set of questions credited to Heilmeier that anyone proposing a
researc
On Tue, Jan 07, 2014 at 10:15:38AM -0500, Peter Grace wrote:
> I am asking for your opinions
> on all manners of self-help: certification ideas, books that have helped
> you "grok" how a department should work properly
_Team Geek_ by Brian W. Fitzpatrick and Ben Collins-Sussman:
http://shop.o
William Bilancio wrote:
> So I am wondering what you all use for a bag to carry books/stuff in with
> or with out your laptop. So send me links of the bag you use/like and let
> me know why you like it.
Two other people have already said this but I have to repeat it: Pretty
much anything by Tom Bi
Jonathan Nicol wrote:
> Everyone, pretty-please stop double-posting to both lists.
Better yet: Let's use this as an opportunity to combine lopsa-tech and
lopsa-discuss into a single mailing list. Very few people seem to know
(or understand or respect) the difference between the two lists, and
the
Phil Pennock wrote:
> https://github.com/kahun/awesome-sysadmin
>
> . . . it's certainly already a useful list of links worth sharing.
I disagree.
To me, the only value that page has over raw Google results is that it
lists "tools" known to be open source. However, it adds nothing in the
way of
I urge you to take 17 minutes out of your day and watch this:
http://fivethirtyeight.com/features/the-queen-of-code/
It's a brief documentary about Grace Hopper. Whether you know who she is
or not, I think it will be 17 minutes well spent.
Adam
___
Kent C. Brodie wrote:
> my boss informed me this year they will no longer be paying for professional
> memberships.
I'm curious: Is it the case that you went to your boss and said "hey,
will the company cover my dues" or is it that your employer offers
reimbursement of professional dues to all emp
Daniel Rich wrote:
> The LOPSAgram should be up on lopsa.org
*Should* be, but isn't: The last issue available on the web site is from
October 2014 -- which, by the way, wasn't posted until December 16th.
Adam
___
Discuss mailing list
Discuss@lists.lopsa
David wrote:
> Assuming you want a full-time executive director . . . you're looking at
> more like $50k-$60k.
No opinion, just data: Taken from their 990 filings, here's what USENIX
paid their Executive Director(s):
2011:
$243,535 ("Director A")
2012:
David Lang wrote:
> Can you get LISA membership ($45) without also ahving to have USENIX
> membership ($125)?
Yes.
> Which just leaves the short topics books. Are they still publishing these
> on a regular basis?
The last booklet was published sometime in 2012.
> Is this something we should b
David Lang wrote:
> what's the expected size of one of these bookets (wordcount)?
Not counting the job descriptions booklets, I believe mine is the
shortest: 37 pages, roughly 16,000 words. The longest is 134 pages,
average is around 80 pages, which I think is 35,000 - 40,000 words.
Adam
Derek J. Balling wrote:
> I'm a little concerned by this:
>
> "The LC will pick the best questions and the candidates will post
> their answers for you to read."
And Warner replied:
> we have no plans to "filter" the questions.
I feel compelled to point out that "will pick the best questions" i
Back in 2007 I worked for a company with an open floor plan. It covered
the entire company, from the CEO on down to the lowest-paid employee. As
a result, the necessary etiquette and manners required to make an open
floor plan work were part of the company culture -- and it pretty much
worked, incl
Allan Irving wrote:
> How do we feel about trailing Slack instead of discussion lists?
While email may not be perfect, and it doesn't offer many of the
features found in tools such as Slack or Google Plus or Twitter, it has
two big advantages: First, everyone uses email, so no matter how many
foru
Allan Irving wrote:
> given the response for outdated technology which is very insecure
It's a public mailing list, and the archives are available on the
LOPSA.org web site for anyone to see -- no sign in, no password. There's
no need for security because a deliberate decision was made that the
ar
Allan Irving wrote:
> if some of you here would review what Slack offer as premium . . . you
> would find security surpasses this mailing list.
Again: This list was set up to be open, archived, and searchable; there
was never any requirement for security. Anyone may join, and anyone --
including p
Lance,
> Suddenly, no more messages in my elasticsearch inbox folder and I have
> to go to their website to see anything.
You bring up what I think is an important point but I don't think that
point is "Mailing lists vs. New Technologies" so much as having all
communication of a particular type (
Way back in June, Craig Constantine and Ski
Kacoroski and David Lang wrote:
> (stuff about getting a group together to submit to JESE [1]
Did anything ever come of this? Is anyone submitting something with
LOPSA's imprimatur? Or individually?
FYI, the deadline is one week from today.
Adam
[
Atom Powers wrote:
> Can you suggest culture and/or process books that might be more appropriate
> for a craft culture organization? And especially about building or managing
> a craft culture.
Leaving aside any/all discussion of your premise of "business culture"
v. "craft culture" . . . First, I
Craig Constantine wrote:
> how to build a web service directly on the cloud tech
^^
What exactly do you mean by this?
On one hand,you can treat "the cloud" as just a bunch of VMs, in which
case it's the same as building a web service anywhere e
On Wed, Dec 15, 2010 at 11:41:45AM -0500, Jason Qualkenbush wrote:
> I'm being asked to build a 32bit system.
There are times when 32-bit systems are appropriate; in particular, some
(many?) applications run faster on a 32-bit system. There are other times
when a 64-bit system is appropriate. Neit
In the spirit of USENIX and LISA tutorials (and PICC and the Cascadia IT
Conference) . . .
Please come to a class I'll be teaching in March:
Workplace Presentations 101 for IT Professionals
(in other words, sy
Joseph S D Yao wrote:
> Unfortunately, this is a per-state thing. Like the value of pi.
Sorry, no: http://www.snopes.com/religion/pi.asp
___
Discuss mailing list
Discuss@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list
Gilbert Wilson asked:
> (how to cure/relieve back pain)
I injured my back ~20 years ago (totally unrelated to sysadmin). I've
since learned two key things: 1) nothing works for everyone; 2) it's
exceedingly rate that one single thing will do the trick.
I use/do all of the following (in no particu
Paul Graydon wrote:
> Hopefully with a good wide spread of interest and talents we could
> finally get a monitoring tool that doesn't actually suck!
And what color pony do you want with that?
Seriously, given the incredibly wide range of applications, situations,
SLAs, services, constraints, cond
Matt Disney wrote:
> For those of you that will be at LISA next week, I invite you to subscribe
> to the email list we have set up for LISA topics:
> https://lists.lopsa.org/cgi-bin/mailman/listinfo/lopsa-lisa
I strongly urge people to ignore this suggestion.
We already have more LOPSA lists than
Matt Disney wrote:
> Anyone have more suggestions or recommendations for how
> LOPSA can improve communication among attendees at LISA or other events?
Since you asked . . . I think the thing is for LOPSA to present itself
as a resource to be used and not try to "dictate" how the communication
sho
Tom Limoncelli wrote:
> We have disc...@lopsa.org for talking about current events, conferences,
> and so on. Why subdivide it?
Worse -- we have t...@lopsa.org *and* disc...@lopsa.org, and we're
having this discussion ON BOTH LISTS! Why? At a minimum, because no
one knows the difference between th
John Stoffel wrote:
> As for moving to Google Groups or anything like that, please no.
Please allow me to clarify . . . I didn't say or even suggest that LOPSA
should move to Google groups or even that LOPSA should change anything
about how its members communicate.
What I _did_ say was that peopl
One other note about the training materials . . . In the majority of
cases, and unless stated otherwise, those training materials -- whether
on the USB key or printed -- are FOR PERSONAL USE ONLY. That is, you may
use them for yourself, or loan them to people, but you MAY NOT copy them
or post them
In no particular order . . .
I consider Rob Kolstad to be a friend, and I've worked with him on the
quiz show and also on USENIX/SAGE/LOPSA-related stuff for many years;
seeing him and working with him is always fun, and I'm glad I got that
chance again after so many years.. As one of the people w
Speaking as a past LISA Program Chair, as a member of the LISA Steering
Committee, as a LISA attendee for 18 years now, and as someone who
usually pays LISA expenses out of my own pocket, I'd like to put out a
request concerning LISA 2012 while this year's conference is still fresh
in our minds . .
40 matches
Mail list logo
