Hi Mikael,
For newcomers http://www.youtube.com/watch?v=mk48xRzuNvA
At 10:06 11-11-2012, Mikael Abrahamsson wrote:
Getting buy-in from management to allow me to go for a week
somewhere and not be available in the office, pay for hotel and
travel, plus the entrence fee, it's hard to justify to management.
What is a good answer to the question "why?".
I don't have an answer to the question. I'd say that it depends on
your company's goals and what it expects from you. It also depends
on your ability to assimilate. If there's a specification that
affects your company's bottom line it would be better to discuss
about it as early as possible. It's up to you to identify what work
will be done or is being done and assess its impact. It's difficult
to justify if management does not have any understanding of what the
IETF does. Here's an argument: "the training course you offered me
will cost you the same amount as my IETF attendance. How about you
sending me to the IETF instead of that training course"? I am not
equating training with IETF attendance. If you are going to attend
an IETF meeting to be trained you will end up being disappointed.
Now, how could your company determine whether you are going to play
solitaire instead of doing work at the meeting? If you have not
showed any interest in remote participation or you have only posted
"+1" on the mailing list the probability that you would do much at
the meeting is, in my humble opinion, very low.
Remote participating works well in some WGs, in some WGs I have had
a hard time getting through. People in different WGs treat the WG
mailing list differently, culture seems to differ quite a lot.
Yes.
So elaborating on what the benefit of being there physically would
probably help. Remote
I'll quote Tom Petch [1]:
"there is a spectrum in communication from the richest, when I am
standing in front of you, looking you in the eye, to the poorest, a
tweet."
On a different thread Ted Hardie commented about trust issues
[2]. That's difficult to establish remotely.
Regards,
-sm
1. http://www.ietf.org/mail-archive/web/ietf/current/msg75764.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg75749.html