Dns-operations mailing list

[Jon Plews <general AT plews.pro>]

On 01/05/14 09:11, Quinn Wood wrote:
> Yes, if you refuse to get up and walk to the water cooler where your 
> coworkers are standing you won't get invited to the bar after work and 
> won't be able to keep up with what's going on in the workplace outside your 
> own projects. Tough shit.


Are you serious? I know I'm a quiet member but I have a young family and
run my own business which takes most of my time, plus I have no real
capacity for small talk and other social things. And I'm an odd guy, you
probably don't want to talk to me anyway.


If this was work, and your project was significant to the company I'd
expect to know about it, because you should be interested in letting
other people know about the important stuff your doing, regardless of
your personal opinions of who cares or who you care about.

In a community with a commitment to openness, its should even be your
_obligation_ to summarize these things, cut and paste the IRC logs, or
if they're archived link to the day, something.

I'd _expect_ an inner circle to form in groups like this, when they
loose interest in the community around them, that community will dissolve.

Regards

Jon



> On 01/05/14 03:56, Julian DeMarchi wrote:

>I propose the following ideas to deal with unresponsive operators.
>> 
>> - must idle in IRC
>> - 1 week to communicate with community on any issues that are
>> occurring(server failure, etc...)
>> - 2 weeks to fix an issue

Idling doesn't make sense, and excludes anyone who's not familiar or
comfortable with that particular, IMO, niche communication tech.

1 week to respond to a complaint on mailing lists - YES. If your
operating a T1 and your not able to keep a weekly eye on a mailing list
you've either lost interest or having a really hard time. Either way
your unable to honor your commitments, love you, but all the same, bye.

Fixed limits on resolving issues? also unrealistic, and not needed. If
your having problems keep posting to operations list saying "I can't fix
this yet" eventually you'll miss a week and get kicked, or we'll work
out you've set up a cron job and take some action.

Fixed limits for deprecating and removing TLDs that do not function?
absolutely (fundamentally different to previous paragraph, work it out
if you don't get it)

-- 
Plews Technology Ltd.