
From acooper@cdt.org  Mon May 13 09:51:18 2013
Return-Path: <acooper@cdt.org>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172E721F8EB9 for <mentoring-coordinators@ietfa.amsl.com>; Mon, 13 May 2013 09:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.619
X-Spam-Level: 
X-Spam-Status: No, score=-100.619 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKas2nJxW6tB for <mentoring-coordinators@ietfa.amsl.com>; Mon, 13 May 2013 09:51:11 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 2778621F8960 for <mentoring-coordinators@ietf.org>; Mon, 13 May 2013 09:51:06 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)) for mentoring-coordinators@ietf.org; Mon, 13 May 2013 12:51:04 -0400
From: Alissa Cooper <acooper@cdt.org>
Content-Type: multipart/mixed; boundary="Apple-Mail=_DA58169D-984D-4AF4-8FBC-F30C7D4CEFE9"
Message-Id: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org>
Date: Mon, 13 May 2013 12:51:09 -0400
To: "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 16:51:18 -0000

--Apple-Mail=_DA58169D-984D-4AF4-8FBC-F30C7D4CEFE9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi all,

Welcome to the mentoring-coordinators@ietf.org mailing list. These are =
the folks who have signed up as coordinators and who are on this list:

Ron Bonica
Ralph Droms
Lars Eggert
Leif Johansson
Murray Kucherawy
Robert Sparks

Brian Haberman and myself are also subscribed and will be helping to get =
the program going. Here is a sketch of how we envision the program =
working:

The secretariat will be building an IETF Mentoring page linked from the =
main IETF site. The site will contain FAQs about the program and web =
forms that allow people to sign up to be mentors or to be prot=E9g=E9s. =
Our current thinking is to limit the prot=E9g=E9 pool to anyone who has =
attended three or fewer IETF meetings, and to limit the mentor pool to =
anyone who is nomcom eligible. We could change the prot=E9g=E9 limit in =
the future, but since this is an experiment we'd like to keep it =
somewhat limited for now and see how it works. Both the FAQs and the web =
form fields are attached for your review and comment.

IETF registration is already open. Our thinking was that we can start =
soliciting mentors any time by sending a message to IETF-Announce. =
Suggested text for that is included below. Once registration has been =
open for awhile, we can then start soliciting prot=E9g=E9s by emailing =
the IETF 87 newcomers' mailing list, and sending the same mail to =
individuals who have attended fewer than 3 meetings (the secretariat can =
determine who is in this group for us).

It probably makes sense to set a deadline by which mentors and prot=E9g=E9=
s need to sign up, after which you all can get to work doing the =
matchings. Suggestions for a deadline? The secretariat will be building =
a database to capture all of the info from the web forms. We're still =
working out how to make that a collaborative tool so that you all can =
work together on the matchings and see who has been matched already, =
etc. If you have thoughts about good tools for this, feel free to share.

Whether you want to stick to 1:1 matches or allow some 1:more-than-1 is =
up to you and might depend on who you get signed up in both groups.

Brian and I have also discussed opportunities to help mentors and =
prot=E9g=E9s meet at the beginning of IETF week, perhaps in designated =
areas at the newcomers' meet-and-greet. We're still mulling that over =
but would appreciate your thoughts about that.

One last question is whether the fact that you all are coordinating the =
program should be made public. On one hand, it might be helpful for =
people to not know that you're doing the matching, so that no one tries =
to lobby you. Brian and I could certainly front all complaints/lobbying =
in that regard. On the other hand, you will be spending some time on =
this and so I can appreciate that you might want some recognition for =
it. Would be interested in your thoughts about that.

Let us know if you have questions.

Thanks,
Alissa

-----------

Subject: IETF Mentor Program

Hi all,
    Based on discussions during IETF 86, we are trialing an IETF =
mentoring program.  During this trial period, we would like to pair =
those who are new to the IETF (people who have attended 3 or fewer =
meetings) with existing IETF participants.  The goal is to provide a =
resource for the new people who can assist them with integrating into =
the IETF community.  Mentors and prot=E9g=E9s (who express an interest =
in being mentored) will be paired prior to IETF 87. We cannot guarantee =
that every mentor or prot=E9g=E9 will be matched, but we'll do our best. =
If the trial goes well, there may be a variety of ways to expand the =
program in the future.

    What we need is for people to volunteer to be mentors. As a mentor, =
we would ask that you be willing to assist your prot=E9g=E9 before, =
during, and (hopefully) after IETF 87.  The actual level of interaction =
will be driven by an agreement between the mentor and the mentee. =
Additionally, we would need a brief description of your areas of =
expertise, technical interests, and conversational languages.

    People interested in acting as mentors can volunteer by filling at =
the form at ???.  An FAQ for this trial program is available here: ???.

Regards,
Alissa & Brian


--Apple-Mail=_DA58169D-984D-4AF4-8FBC-F30C7D4CEFE9
Content-Disposition: attachment;
	filename=mentor_faq.txt
Content-Type: text/plain;
	name="mentor_faq.txt"
Content-Transfer-Encoding: quoted-printable

1. What is the IETF Mentoring Program?

The goal of the IETF Mentoring Program is to match experienced IETF =
participants
with newcomers in order to aid their integration into the IETF community =
through
advice, help, and collected wisdom. The guidance provided by the mentors =
should
speed up the time it takes for newcomers to become active, contributing =
members
of the IETF.

2. What is an IETF mentor?

A mentor plays the role of advisor, coach, teacher, and guide. The =
combinations of
roles allows a mentor to provide the guidance needed to assist his/her =
protege in
developing the skills needed to participate effectively within the IETF =
standards
process.

3. What skills are needed to be a mentor?

The biggest skill needed is a willingness to share your knowledge of the =
IETF with
a protege. This can include explaining: 1) the IETF standards =
development process,
2) the IETF management structure, 3) other IETF participants' skill =
sets, and
4) the working group creation process.

4. How much time will being a mentor take?

The amount of time is variable based on an agreement between the mentor =
and the protege.
It is hoped that the mentor/protege relationship extends beyond the =
interactions
during the face-to-face meetings.

5. Is the mentoring program restricted to certain kinds of people?

Initially, the program is focused on proteges who are newcomers to the =
IETF (people who
have participated in three or fewer face-to-face meetings). If the =
program progresses
in a positive direction, we will explore opening up the program to all =
participants.
Anyone currently involved in the IETF is eligible to be a mentor.

6. How do I know if I am eligible to be a protege?

When you register for a face-to-face meeting, the registration form will =
determine if
you are eligible and, if so, ask if you are interested in having a =
mentor.

7. How are matches made between mentors and proteges?

A small group of IETF participants have volunteered to act as =
coordinators. The coordinators
have areas of expertise and will work with the characteristics =
identified by the protege
to match them with a mentor who has similar interests and areas of work.

8. What makes a good mentor?

A successful mentor will be flexible, responsive, and willing to take =
the initiative to
provide guidance to a protege. A mentor should have the confidence that =
they have useful
knowledge that will aid a protege. Experience in the IETF culture will =
allow the mentor
to recognize areas where newcomers will struggle within the IETF and =
allow the mentor
to pass along constructive information.  This is especially key in the =
areas of cultural
norms and the IETF environment.

9. What happens after a mentor and protege are matched?

Once a match has been made, the mentor should initiate contact with the =
protege. After
that, the interactions are up to the mentor and protege. Useful =
interactions will vary
based on the needs of the protege and the skills of the mentor.  In the =
event that a
mentor/protege is unresponsive or the pair decide that the match is not =
constructive,
the coordinators can be contacted to request a new pairing.

10. What if my protege has a question that I cannot answer?

When someone volunteers to be a mentor, they will be added to a mentors =
mailing list.
One of the goals of this list is to provide a discussion forum for the =
mentors to
brainstorm over problems raised by a protege that couldn't be =
immediately answered. It
is also expected that mentors will not know all the answers, but should =
be in a good
position to point the protege in the right direction.  This includes =
assisting the protege
in searching out the answer to the question.

11. How does the mentoring program work?

During IETF meeting registration, newcomers will be identified and given =
the opportunity
to request a mentor. After the request is made, the mentor coordinators =
will assess the
areas of interest of the newcomer and select a mentor from a pool of =
volunteers. The
mentor will be selected based on areas of common interest between the =
mentor and protege.
After the match is made, an introductory e-mail will be sent to the =
mentor and protege
in order to provide contact information.  After that, it is up to the =
mentor and protege
to determine how the relationship will progress.  After the face-to-face =
IETF meeting, the
mentor program will send out a brief questionnaire to determine how well =
the program is
functioning.

12. As a protege, what should I get out of the relationship?

Ideally, a protege will come away with a better understanding of the =
IETF, knowledge of
the standards development process, and someone to turn to when questions =
arise. Each
protege's needs will be different and the mentoring program should be =
flexible enough to
assist with those needs.

13. What does it take to be a good protege?

The biggest key is being willing to learn. The IETF community can be =
different, so a
protege should be willing to listen to a different perspective (the =
mentor's). A protege
should also be proactive in asking questions so that the relationship is =
driven by the
protege's needs and not the mentor's view.

--Apple-Mail=_DA58169D-984D-4AF4-8FBC-F30C7D4CEFE9
Content-Disposition: attachment;
	filename="mentor and mentee forms.txt"
Content-Type: text/plain;
	name="mentor and mentee forms.txt"
Content-Transfer-Encoding: quoted-printable

Protege sign-up

First name:
Last name:
Email address:
Affiliation:
Country in which you are based:

Is this your first IETF?
If not, how many IETF meetings have you attended?

What technical topic(s) brought you to the IETF?
IETF area(s) of interest, if known (see =
http://www.ietf.org/iesg/area.html for more info):
IETF working groups of interest, if known: (see http://www.ietf.org/wg/ =
for more info):

What are your preferred conversational language(s), if not English?
Would you like to be paired with a mentor who speaks your preferred =
language(s), if possible? [Yes/No/Indifferent]

Do you have a preference as to your mentor's gender? [M/F/Either]

Do you plan to attend the newcomers' meet-and-greet on Sunday at 16:00?
Do you plan to attend the welcome reception on Sunday at 17:00?

Any other info you'd like to share:

---------

Mentor sign-up

First name:
Last name:
Email address:
Affiliation:
Country in which you are based:
Gender: [M/F]

IETF area(s) of expertise:
IETF WGs that you are familiar with:
How many years have you been participating in the IETF?

What languages other than English would you be comfortable conversing in =
with your protege?

Do you plan to attend the newcomers' meet-and-greet on Sunday at 16:00?
Do you plan to attend the welcome reception on Sunday at 17:00?

Any other info you'd like to share:





--Apple-Mail=_DA58169D-984D-4AF4-8FBC-F30C7D4CEFE9--


From rjsparks@nostrum.com  Mon May 13 11:12:43 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02BBC21F90EE for <mentoring-coordinators@ietfa.amsl.com>; Mon, 13 May 2013 11:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KOVz5gQNoKU2 for <mentoring-coordinators@ietfa.amsl.com>; Mon, 13 May 2013 11:12:41 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 931A721F90C1 for <mentoring-coordinators@ietf.org>; Mon, 13 May 2013 11:12:40 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-071-029.mycingular.net [166.147.71.29]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4DICcsB087186 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <mentoring-coordinators@ietf.org>; Mon, 13 May 2013 13:12:39 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51912D11.8030904@nostrum.com>
Date: Mon, 13 May 2013 13:12:33 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mentoring-coordinators@ietf.org
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org>
In-Reply-To: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org>
Content-Type: multipart/alternative; boundary="------------010702070001060603070603"
Received-SPF: pass (shaman.nostrum.com: 166.147.71.29 is authenticated by a trusted mechanism)
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 18:12:43 -0000

This is a multi-part message in MIME format.
--------------010702070001060603070603
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 5/13/13 11:51 AM, Alissa Cooper wrote:
> Hi all,
>
> Welcome to the mentoring-coordinators@ietf.org mailing list. These are the folks who have signed up as coordinators and who are on this list:
>
> Ron Bonica
> Ralph Droms
> Lars Eggert
> Leif Johansson
> Murray Kucherawy
> Robert Sparks
>
> Brian Haberman and myself are also subscribed and will be helping to get the program going. Here is a sketch of how we envision the program working:
>
> The secretariat will be building an IETF Mentoring page linked from the main IETF site. The site will contain FAQs about the program and web forms that allow people to sign up to be mentors or to be protégés. Our current thinking is to limit the protégé pool to anyone who has attended three or fewer IETF meetings, and to limit the mentor pool to anyone who is nomcom eligible. We could change the protégé limit in the future, but since this is an experiment we'd like to keep it somewhat limited for now and see how it works. Both the FAQs and the web form fields are attached for your review and comment.
>
> IETF registration is already open. Our thinking was that we can start soliciting mentors any time by sending a message to IETF-Announce. Suggested text for that is included below. Once registration has been open for awhile, we can then start soliciting protégés by emailing the IETF 87 newcomers' mailing list, and sending the same mail to individuals who have attended fewer than 3 meetings (the secretariat can determine who is in this group for us).
>
> It probably makes sense to set a deadline by which mentors and protégés need to sign up, after which you all can get to work doing the matchings. Suggestions for a deadline?
I'm not sure we would need the whole set before we started matching - 
maybe we have, and advertise, a date at which we would start
(to drive early signup), but do matching up to and at the IETF meeting? 
I would suggest that start date be 1 or two weeks before the -00 deadline.

> The secretariat will be building a database to capture all of the info from the web forms. We're still working out how to make that a collaborative tool so that you all can work together on the matchings and see who has been matched already, etc. If you have thoughts about good tools for this, feel free to share.
It's dangerous to build too much tool when you're still trying to figure 
out what you really want to be doing - it can cause you to accidentally 
get stuck with a behavior you don't really need. I would strongly 
suggest just starting with a wiki and more manual effort than you want 
in the long run until we know what a tool really needs to help with.
>
> Whether you want to stick to 1:1 matches or allow some 1:more-than-1 is up to you and might depend on who you get signed up in both groups.
>
> Brian and I have also discussed opportunities to help mentors and protégés meet at the beginning of IETF week, perhaps in designated areas at the newcomers' meet-and-greet. We're still mulling that over but would appreciate your thoughts about that.
>
> One last question is whether the fact that you all are coordinating the program should be made public. On one hand, it might be helpful for people to not know that you're doing the matching, so that no one tries to lobby you. Brian and I could certainly front all complaints/lobbying in that regard. On the other hand, you will be spending some time on this and so I can appreciate that you might want some recognition for it. Would be interested in your thoughts about that.
When in doubt, fail open.

>
> Let us know if you have questions.
>
> Thanks,
> Alissa
>
> -----------
>
> Subject: IETF Mentor Program
>
> Hi all,
>      Based on discussions during IETF 86, we are trialing an IETF mentoring program.  During this trial period, we would like to pair those who are new to the IETF (people who have attended 3 or fewer meetings) with existing IETF participants.  The goal is to provide a resource for the new people who can assist them with integrating into the IETF community.  Mentors and protégés (who express an interest in being mentored) will be paired prior to IETF 87. We cannot guarantee that every mentor or protégé will be matched, but we'll do our best. If the trial goes well, there may be a variety of ways to expand the program in the future.
>
>      What we need is for people to volunteer to be mentors. As a mentor, we would ask that you be willing to assist your protégé before, during, and (hopefully) after IETF 87.  The actual level of interaction will be driven by an agreement between the mentor and the mentee. Additionally, we would need a brief description of your areas of expertise, technical interests, and conversational languages.
>
>      People interested in acting as mentors can volunteer by filling at the form at ???.  An FAQ for this trial program is available here: ???.
>
> Regards,
> Alissa & Brian

On the signup forms - consider asking both mentors and protoges (I'm 
worried how the community will react to the term btw) are active in any 
other SDOs, and if they have any non-IETF activities they are passionate 
about.

RjS
>
>
>
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators


--------------010702070001060603070603
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 5/13/13 11:51 AM, Alissa Cooper
      wrote:<br>
    </div>
    <blockquote cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
      type="cite">
      <pre wrap="">Hi all,

Welcome to the <a class="moz-txt-link-abbreviated" href="mailto:mentoring-coordinators@ietf.org">mentoring-coordinators@ietf.org</a> mailing list. These are the folks who have signed up as coordinators and who are on this list:

Ron Bonica
Ralph Droms
Lars Eggert
Leif Johansson
Murray Kucherawy
Robert Sparks

Brian Haberman and myself are also subscribed and will be helping to get the program going. Here is a sketch of how we envision the program working:

The secretariat will be building an IETF Mentoring page linked from the main IETF site. The site will contain FAQs about the program and web forms that allow people to sign up to be mentors or to be prot&eacute;g&eacute;s. Our current thinking is to limit the prot&eacute;g&eacute; pool to anyone who has attended three or fewer IETF meetings, and to limit the mentor pool to anyone who is nomcom eligible. We could change the prot&eacute;g&eacute; limit in the future, but since this is an experiment we'd like to keep it somewhat limited for now and see how it works. Both the FAQs and the web form fields are attached for your review and comment.

IETF registration is already open. Our thinking was that we can start soliciting mentors any time by sending a message to IETF-Announce. Suggested text for that is included below. Once registration has been open for awhile, we can then start soliciting prot&eacute;g&eacute;s by emailing the IETF 87 newcomers' mailing list, and sending the same mail to individuals who have attended fewer than 3 meetings (the secretariat can determine who is in this group for us).

It probably makes sense to set a deadline by which mentors and prot&eacute;g&eacute;s need to sign up, after which you all can get to work doing the matchings. Suggestions for a deadline? </pre>
    </blockquote>
    I'm not sure we would need the whole set before we started matching
    - maybe we have, and advertise, a date at which we would start<br>
    (to drive early signup), but do matching up to and at the IETF
    meeting? I would suggest that start date be 1 or two weeks before
    the -00 deadline.<br>
    <br>
    <blockquote cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
      type="cite">
      <pre wrap="">The secretariat will be building a database to capture all of the info from the web forms. We're still working out how to make that a collaborative tool so that you all can work together on the matchings and see who has been matched already, etc. If you have thoughts about good tools for this, feel free to share.</pre>
    </blockquote>
    It's dangerous to build too much tool when you're still trying to
    figure out what you really want to be doing - it can cause you to
    accidentally get stuck with a behavior you don't really need. I
    would strongly suggest just starting with a wiki and more manual
    effort than you want in the long run until we know what a tool
    really needs to help with.<br>
    <blockquote cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
      type="cite">
      <pre wrap="">

Whether you want to stick to 1:1 matches or allow some 1:more-than-1 is up to you and might depend on who you get signed up in both groups.

Brian and I have also discussed opportunities to help mentors and prot&eacute;g&eacute;s meet at the beginning of IETF week, perhaps in designated areas at the newcomers' meet-and-greet. We're still mulling that over but would appreciate your thoughts about that.

One last question is whether the fact that you all are coordinating the program should be made public. On one hand, it might be helpful for people to not know that you're doing the matching, so that no one tries to lobby you. Brian and I could certainly front all complaints/lobbying in that regard. On the other hand, you will be spending some time on this and so I can appreciate that you might want some recognition for it. Would be interested in your thoughts about that.</pre>
    </blockquote>
    When in doubt, fail open.<br>
    <br>
    <blockquote cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
      type="cite">
      <pre wrap="">

Let us know if you have questions.

Thanks,
Alissa

-----------

Subject: IETF Mentor Program

Hi all,
    Based on discussions during IETF 86, we are trialing an IETF mentoring program.  During this trial period, we would like to pair those who are new to the IETF (people who have attended 3 or fewer meetings) with existing IETF participants.  The goal is to provide a resource for the new people who can assist them with integrating into the IETF community.  Mentors and prot&eacute;g&eacute;s (who express an interest in being mentored) will be paired prior to IETF 87. We cannot guarantee that every mentor or prot&eacute;g&eacute; will be matched, but we'll do our best. If the trial goes well, there may be a variety of ways to expand the program in the future.

    What we need is for people to volunteer to be mentors. As a mentor, we would ask that you be willing to assist your prot&eacute;g&eacute; before, during, and (hopefully) after IETF 87.  The actual level of interaction will be driven by an agreement between the mentor and the mentee. Additionally, we would need a brief description of your areas of expertise, technical interests, and conversational languages.

    People interested in acting as mentors can volunteer by filling at the form at ???.  An FAQ for this trial program is available here: ???.

Regards,
Alissa &amp; Brian</pre>
    </blockquote>
    <br>
    On the signup forms - consider asking both mentors and protoges (I'm
    worried how the community will react to the term btw) are active in
    any other SDOs, and if they have any non-IETF activities they are
    passionate about.<br>
    <br>
    RjS<br>
    <blockquote cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
      type="cite">
      <pre wrap="">

</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
mentoring-coordinators mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mentoring-coordinators@ietf.org">mentoring-coordinators@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mentoring-coordinators">https://www.ietf.org/mailman/listinfo/mentoring-coordinators</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010702070001060603070603--

From leifj@mnt.se  Tue May 14 05:37:20 2013
Return-Path: <leifj@mnt.se>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F1121F8F53 for <mentoring-coordinators@ietfa.amsl.com>; Tue, 14 May 2013 05:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qsAQ7FL8U9A2 for <mentoring-coordinators@ietfa.amsl.com>; Tue, 14 May 2013 05:37:19 -0700 (PDT)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 25CAA21F8F7B for <mentoring-coordinators@ietf.org>; Tue, 14 May 2013 05:37:18 -0700 (PDT)
Received: by mail-bk0-f53.google.com with SMTP id mx1so281899bkb.26 for <mentoring-coordinators@ietf.org>; Tue, 14 May 2013 05:37:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:x-gm-message-state; bh=0vYIudfb7ZBLcIOTSYB0AA1EzsxKE2RV0aOydyhx3Fc=; b=iTctS4EolH9lZj6sLIqa0RyvN2ATPl7kj7XjJA5zrO/7xUSGZDenJJKF3uBe3p142Y 2p1csdlZU1lXxtIiizrd6pOzQIh15I4ZY6L/hVEtRenNZD3xRPuI7f3xy1k6c436V7CJ 3J2eBHgmZvk1bnDNTYDtFIxX1xvqJbMINUE3MjDvYEMY5bFKsqX8EtkAEKnPEuceMxBw xN5T2/3YeTWyRmAHTzixaZYWtdseutnFLT87K7AkG457w5KbaxZfiNzUeAJCd/6E+ulR P77Vk1mI4+CTdIq/FXAlU/syWHhwph5UBkYIOCgIqmJga1IgoQRz/tupfpTeMFv7cDa8 ta0Q==
X-Received: by 10.204.200.193 with SMTP id ex1mr8090988bkb.39.1368535038132; Tue, 14 May 2013 05:37:18 -0700 (PDT)
Received: from ?IPv6:2001:6b0:7:0:cd46:9d41:616d:a623? ([2001:6b0:7:0:cd46:9d41:616d:a623]) by mx.google.com with ESMTPSA id jz9sm3579226bkb.1.2013.05.14.05.37.16 for <mentoring-coordinators@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 May 2013 05:37:17 -0700 (PDT)
Message-ID: <51922FFB.4070302@mnt.se>
Date: Tue, 14 May 2013 14:37:15 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: mentoring-coordinators@ietf.org
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com>
In-Reply-To: <51912D11.8030904@nostrum.com>
Content-Type: multipart/alternative; boundary="------------030402040202050304010307"
X-Gm-Message-State: ALoCoQlxI2Uc8uV8Fmljt7HtN+0eBZFwAY2dff2iHEDXEAfCv1XFADUMVrcSiHRAiQsvyUVmcidY
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 12:37:20 -0000

This is a multi-part message in MIME format.
--------------030402040202050304010307
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

On 05/13/2013 08:12 PM, Robert Sparks wrote:
> On 5/13/13 11:51 AM, Alissa Cooper wrote:
>> Hi all,
>>
>> Welcome to the mentoring-coordinators@ietf.org mailing list. These are the folks who have signed up as coordinators and who are on this list:
>>
>> Ron Bonica
>> Ralph Droms
>> Lars Eggert
>> Leif Johansson
>> Murray Kucherawy
>> Robert Sparks
>>
>> Brian Haberman and myself are also subscribed and will be helping to get the program going. Here is a sketch of how we envision the program working:
>>
>> The secretariat will be building an IETF Mentoring page linked from the main IETF site. The site will contain FAQs about the program and web forms that allow people to sign up to be mentors or to be protégés. Our current thinking is to limit the protégé pool to anyone who has attended three or fewer IETF meetings, and to limit the mentor pool to anyone who is nomcom eligible. We could change the protégé limit in the future, but since this is an experiment we'd like to keep it somewhat limited for now and see how it works. Both the FAQs and the web form fields are attached for your review and comment.
>>
>> IETF registration is already open. Our thinking was that we can start soliciting mentors any time by sending a message to IETF-Announce. Suggested text for that is included below. Once registration has been open for awhile, we can then start soliciting protégés by emailing the IETF 87 newcomers' mailing list, and sending the same mail to individuals who have attended fewer than 3 meetings (the secretariat can determine who is in this group for us).
>>
>> It probably makes sense to set a deadline by which mentors and protégés need to sign up, after which you all can get to work doing the matchings. Suggestions for a deadline? 
> I'm not sure we would need the whole set before we started matching -
> maybe we have, and advertise, a date at which we would start
> (to drive early signup), but do matching up to and at the IETF
> meeting? I would suggest that start date be 1 or two weeks before the
> -00 deadline.

sounds reasonable, how many mentorees are we expecting?


>
>> The secretariat will be building a database to capture all of the info from the web forms. We're still working out how to make that a collaborative tool so that you all can work together on the matchings and see who has been matched already, etc. If you have thoughts about good tools for this, feel free to share.
> It's dangerous to build too much tool when you're still trying to
> figure out what you really want to be doing - it can cause you to
> accidentally get stuck with a behavior you don't really need. I would
> strongly suggest just starting with a wiki and more manual effort than
> you want in the long run until we know what a tool really needs to
> help with.

agree fully.

>> Whether you want to stick to 1:1 matches or allow some 1:more-than-1 is up to you and might depend on who you get signed up in both groups.
>>
>> Brian and I have also discussed opportunities to help mentors and protégés meet at the beginning of IETF week, perhaps in designated areas at the newcomers' meet-and-greet. We're still mulling that over but would appreciate your thoughts about that.
>>
>> One last question is whether the fact that you all are coordinating the program should be made public. On one hand, it might be helpful for people to not know that you're doing the matching, so that no one tries to lobby you. Brian and I could certainly front all complaints/lobbying in that regard. On the other hand, you will be spending some time on this and so I can appreciate that you might want some recognition for it. Would be interested in your thoughts about that.
> When in doubt, fail open.
>

+1
>> Let us know if you have questions.
>>
>> Thanks,
>> Alissa
>>
>> -----------
>>
>> Subject: IETF Mentor Program
>>
>> Hi all,
>>     Based on discussions during IETF 86, we are trialing an IETF mentoring program.  During this trial period, we would like to pair those who are new to the IETF (people who have attended 3 or fewer meetings) with existing IETF participants.  The goal is to provide a resource for the new people who can assist them with integrating into the IETF community.  Mentors and protégés (who express an interest in being mentored) will be paired prior to IETF 87. We cannot guarantee that every mentor or protégé will be matched, but we'll do our best. If the trial goes well, there may be a variety of ways to expand the program in the future.
>>
>>     What we need is for people to volunteer to be mentors. As a mentor, we would ask that you be willing to assist your protégé before, during, and (hopefully) after IETF 87.  The actual level of interaction will be driven by an agreement between the mentor and the mentee. Additionally, we would need a brief description of your areas of expertise, technical interests, and conversational languages.
>>
>>     People interested in acting as mentors can volunteer by filling at the form at ???.  An FAQ for this trial program is available here: ???.
>>
>> Regards,
>> Alissa & Brian
>
> On the signup forms - consider asking both mentors and protoges (I'm
> worried how the community will react to the term btw) are active in
> any other SDOs, and if they have any non-IETF activities they are
> passionate about.
>
> RjS
>>
>>
>> _______________________________________________
>> mentoring-coordinators mailing list
>> mentoring-coordinators@ietf.org
>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>
>
>
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators


--------------030402040202050304010307
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 05/13/2013 08:12 PM, Robert Sparks
      wrote:<br>
    </div>
    <blockquote cite="mid:51912D11.8030904@nostrum.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">On 5/13/13 11:51 AM, Alissa Cooper
        wrote:<br>
      </div>
      <blockquote
        cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
        type="cite">
        <pre wrap="">Hi all,

Welcome to the <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mentoring-coordinators@ietf.org">mentoring-coordinators@ietf.org</a> mailing list. These are the folks who have signed up as coordinators and who are on this list:

Ron Bonica
Ralph Droms
Lars Eggert
Leif Johansson
Murray Kucherawy
Robert Sparks

Brian Haberman and myself are also subscribed and will be helping to get the program going. Here is a sketch of how we envision the program working:

The secretariat will be building an IETF Mentoring page linked from the main IETF site. The site will contain FAQs about the program and web forms that allow people to sign up to be mentors or to be prot&eacute;g&eacute;s. Our current thinking is to limit the prot&eacute;g&eacute; pool to anyone who has attended three or fewer IETF meetings, and to limit the mentor pool to anyone who is nomcom eligible. We could change the prot&eacute;g&eacute; limit in the future, but since this is an experiment we'd like to keep it somewhat limited for now and see how it works. Both the FAQs and the web form fields are attached for your review and comment.

IETF registration is already open. Our thinking was that we can start soliciting mentors any time by sending a message to IETF-Announce. Suggested text for that is included below. Once registration has been open for awhile, we can then start soliciting prot&eacute;g&eacute;s by emailing the IETF 87 newcomers' mailing list, and sending the same mail to individuals who have attended fewer than 3 meetings (the secretariat can determine who is in this group for us).

It probably makes sense to set a deadline by which mentors and prot&eacute;g&eacute;s need to sign up, after which you all can get to work doing the matchings. Suggestions for a deadline? </pre>
      </blockquote>
      I'm not sure we would need the whole set before we started
      matching - maybe we have, and advertise, a date at which we would
      start<br>
      (to drive early signup), but do matching up to and at the IETF
      meeting? I would suggest that start date be 1 or two weeks before
      the -00 deadline.<br>
    </blockquote>
    <br>
    sounds reasonable, how many mentorees are we expecting?<br>
    <br>
    <br>
    <blockquote cite="mid:51912D11.8030904@nostrum.com" type="cite"> <br>
      <blockquote
        cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
        type="cite">
        <pre wrap="">The secretariat will be building a database to capture all of the info from the web forms. We're still working out how to make that a collaborative tool so that you all can work together on the matchings and see who has been matched already, etc. If you have thoughts about good tools for this, feel free to share.</pre>
      </blockquote>
      It's dangerous to build too much tool when you're still trying to
      figure out what you really want to be doing - it can cause you to
      accidentally get stuck with a behavior you don't really need. I
      would strongly suggest just starting with a wiki and more manual
      effort than you want in the long run until we know what a tool
      really needs to help with.<br>
    </blockquote>
    <br>
    agree fully. <br>
    <br>
    <blockquote cite="mid:51912D11.8030904@nostrum.com" type="cite">
      <blockquote
        cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
        type="cite">
        <pre wrap="">
Whether you want to stick to 1:1 matches or allow some 1:more-than-1 is up to you and might depend on who you get signed up in both groups.

Brian and I have also discussed opportunities to help mentors and prot&eacute;g&eacute;s meet at the beginning of IETF week, perhaps in designated areas at the newcomers' meet-and-greet. We're still mulling that over but would appreciate your thoughts about that.

One last question is whether the fact that you all are coordinating the program should be made public. On one hand, it might be helpful for people to not know that you're doing the matching, so that no one tries to lobby you. Brian and I could certainly front all complaints/lobbying in that regard. On the other hand, you will be spending some time on this and so I can appreciate that you might want some recognition for it. Would be interested in your thoughts about that.</pre>
      </blockquote>
      When in doubt, fail open.<br>
      <br>
    </blockquote>
    <br>
    +1<br>
    <blockquote cite="mid:51912D11.8030904@nostrum.com" type="cite">
      <blockquote
        cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
        type="cite">
        <pre wrap="">
Let us know if you have questions.

Thanks,
Alissa

-----------

Subject: IETF Mentor Program

Hi all,
    Based on discussions during IETF 86, we are trialing an IETF mentoring program.  During this trial period, we would like to pair those who are new to the IETF (people who have attended 3 or fewer meetings) with existing IETF participants.  The goal is to provide a resource for the new people who can assist them with integrating into the IETF community.  Mentors and prot&eacute;g&eacute;s (who express an interest in being mentored) will be paired prior to IETF 87. We cannot guarantee that every mentor or prot&eacute;g&eacute; will be matched, but we'll do our best. If the trial goes well, there may be a variety of ways to expand the program in the future.

    What we need is for people to volunteer to be mentors. As a mentor, we would ask that you be willing to assist your prot&eacute;g&eacute; before, during, and (hopefully) after IETF 87.  The actual level of interaction will be driven by an agreement between the mentor and the mentee. Additionally, we would need a brief description of your areas of expertise, technical interests, and conversational languages.

    People interested in acting as mentors can volunteer by filling at the form at ???.  An FAQ for this trial program is available here: ???.

Regards,
Alissa &amp; Brian</pre>
      </blockquote>
      <br>
      On the signup forms - consider asking both mentors and protoges
      (I'm worried how the community will react to the term btw) are
      active in any other SDOs, and if they have any non-IETF activities
      they are passionate about.<br>
      <br>
      RjS<br>
      <blockquote
        cite="mid:C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org"
        type="cite">
        <pre wrap="">
</pre>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
mentoring-coordinators mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mentoring-coordinators@ietf.org">mentoring-coordinators@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mentoring-coordinators">https://www.ietf.org/mailman/listinfo/mentoring-coordinators</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
mentoring-coordinators mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mentoring-coordinators@ietf.org">mentoring-coordinators@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mentoring-coordinators">https://www.ietf.org/mailman/listinfo/mentoring-coordinators</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030402040202050304010307--

From lars@netapp.com  Wed May 15 04:38:44 2013
Return-Path: <lars@netapp.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63EE421F8EBE for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 04:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.85
X-Spam-Level: 
X-Spam-Status: No, score=-7.85 tagged_above=-999 required=5 tests=[AWL=2.749,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXCBxUqpQsOy for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 04:38:39 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4A93821F856D for <mentoring-coordinators@ietf.org>; Wed, 15 May 2013 04:38:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,677,1363158000"; d="scan'208";a="53630655"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 15 May 2013 04:38:38 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4FBcb9V001967; Wed, 15 May 2013 04:38:38 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Wed, 15 May 2013 04:38:36 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Mentoring-coordinators] Kicking off mentoring-coordinators
Thread-Index: AQHOT/of6cYtNbCh30WAuPm+ROTrEZkD4EWAgAK2mAA=
Date: Wed, 15 May 2013 11:38:36 +0000
Message-ID: <8DD4EB91-1051-4BBC-BCF3-A881F7ADAC1B@netapp.com>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com>
In-Reply-To: <51912D11.8030904@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <70B84BF61C7A30468B54FC943CB0426E@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mentoring-coordinators@ietf.org>" <mentoring-coordinators@ietf.org>
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 11:38:44 -0000

Hi,

On May 13, 2013, at 20:12, Robert Sparks <rjsparks@nostrum.com> wrote:
> On 5/13/13 11:51 AM, Alissa Cooper wrote:
>> The secretariat will be building an IETF Mentoring page linked from the =
main IETF site. The site will contain FAQs about the program and web forms =
that allow people to sign up to be mentors or to be prot=E9g=E9s. Our curre=
nt thinking is to limit the prot=E9g=E9 pool to anyone who has attended thr=
ee or fewer IETF meetings, and to limit the mentor pool to anyone who is no=
mcom eligible. We could change the prot=E9g=E9 limit in the future, but sin=
ce this is an experiment we'd like to keep it somewhat limited for now and =
see how it works. Both the FAQs and the web form fields are attached for yo=
ur review and comment.

during the IAB retreat, the point was brought up that it would be helpful t=
hat mentors could recall their first exposure to the IETF clearly, i.e., ma=
ybe not the folks who have been coming for 20 years. But we don't need to h=
ave a hard rule here, we can just take this into account when we do the mat=
ching.

>> IETF registration is already open. Our thinking was that we can start so=
liciting mentors any time by sending a message to IETF-Announce. Suggested =
text for that is included below. Once registration has been open for awhile=
, we can then start soliciting prot=E9g=E9s by emailing the IETF 87 newcome=
rs' mailing list, and sending the same mail to individuals who have attende=
d fewer than 3 meetings (the secretariat can determine who is in this group=
 for us).

As I said during the retreat, I think a personalized message from the IETF =
chair to each individual potential protege would probably look better than =
(just) an email to the attendee list (which not all are on anyway). Being o=
ffered a mentor needs to be seen as something of value, which is more stron=
gly conveyed in a message sent in Jari's name IMO.

>> It probably makes sense to set a deadline by which mentors and prot=E9g=
=E9s need to sign up, after which you all can get to work doing the matchin=
gs. Suggestions for a deadline?

> I'm not sure we would need the whole set before we started matching - may=
be we have, and advertise, a date at which we would start
> (to drive early signup), but do matching up to and at the IETF meeting? I=
 would suggest that start date be 1 or two weeks before the -00 deadline.

Sounds reasonable.

>> The secretariat will be building a database to capture all of the info f=
rom the web forms. We're still working out how to make that a collaborative=
 tool so that you all can work together on the matchings and see who has be=
en matched already, etc. If you have thoughts about good tools for this, fe=
el free to share.
> It's dangerous to build too much tool when you're still trying to figure =
out what you really want to be doing - it can cause you to accidentally get=
 stuck with a behavior you don't really need. I would strongly suggest just=
 starting with a wiki and more manual effort than you want in the long run =
until we know what a tool really needs to help with.

+1 on this, a (private) wiki is fine

>> Whether you want to stick to 1:1 matches or allow some 1:more-than-1 is =
up to you and might depend on who you get signed up in both groups.

IMO 1:1 makes the most sense, except for corner cases (two new attendees fr=
om the same company interested in the same topic, etc.)

>> Brian and I have also discussed opportunities to help mentors and prot=
=E9g=E9s meet at the beginning of IETF week, perhaps in designated areas at=
 the newcomers' meet-and-greet. We're still mulling that over but would app=
reciate your thoughts about that.

Definitely at the newcomer's beer. Maybe they can open 30 min early for men=
tors and proteges?

>> One last question is whether the fact that you all are coordinating the =
program should be made public. On one hand, it might be helpful for people =
to not know that you're doing the matching, so that no one tries to lobby y=
ou. Brian and I could certainly front all complaints/lobbying in that regar=
d. On the other hand, you will be spending some time on this and so I can a=
ppreciate that you might want some recognition for it. Would be interested =
in your thoughts about that.

> When in doubt, fail open.

No problem with that.

>> Subject: IETF Mentor Program
>>=20
>> Hi all,
>>     Based on discussions during IETF 86, we are trialing an IETF mentori=
ng program.  During this trial period, we would like to pair those who are =
new to the IETF (people who have attended 3 or fewer meetings) with existin=
g IETF participants.  The goal is to provide a resource for the new people =
who can assist them with integrating into the

s/a resource/a contact person/

>> IETF community.  Mentors and prot=E9g=E9s (who express an interest in be=
ing mentored) will be paired prior to IETF 87. We cannot guarantee that eve=
ry mentor or prot=E9g=E9 will be matched, but we'll do our best. If the tri=
al goes well, there may be a variety of ways to expand the program in the f=
uture.
>>=20
>>     What we need is for people to volunteer to be mentors. As a mentor, =
we would ask that you be willing to assist your prot=E9g=E9 before, during,=
 and (hopefully) after IETF 87.  The actual level of interaction will be dr=
iven by an agreement between the mentor and the mentee. Additionally, we wo=
uld need a brief description of your areas of expertise, technical interest=
s, and conversational languages.

I think we want to say a bit more than just "the actual level of interactio=
n will be driven by an agreement between the mentor and the mentee". We can=
 say that examples of mentoring include accompanying the mentee during the =
week, introducing them to folks they want to meet, explaining what's going =
on both in session and elsewhere, taking them to dinners, etc.

>>     People interested in acting as mentors can volunteer by filling at t=
he form at ???.  An FAQ for this trial program is available here: ???.
>>=20
>> Regards,
>> Alissa & Brian
>=20
> On the signup forms - consider asking both mentors and protoges (I'm worr=
ied how the community will react to the term btw) are active in any other S=
DOs, and if they have any non-IETF activities they are passionate about.

+1 on the term protege, but mentee is also bad. We need a good term here th=
at sounds selective. (I want proteges to be able to say to their bosses "I =
got picked for this special thing, so you should send me again")

Lars=

From lars@netapp.com  Wed May 15 05:40:38 2013
Return-Path: <lars@netapp.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2437121F8696 for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 05:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.224
X-Spam-Level: 
X-Spam-Status: No, score=-9.224 tagged_above=-999 required=5 tests=[AWL=1.375,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oZaKngNBqT1 for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 05:40:33 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id E893C21F8629 for <mentoring-coordinators@ietf.org>; Wed, 15 May 2013 05:40:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,677,1363158000"; d="scan'208";a="53664737"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 15 May 2013 05:39:07 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4FCd77Y013992 for <mentoring-coordinators@ietf.org>; Wed, 15 May 2013 05:39:07 -0700 (PDT)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht04-prd.hq.netapp.com (10.106.77.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 15 May 2013 05:39:07 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Wed, 15 May 2013 05:39:06 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
Thread-Topic: students
Thread-Index: AQHOUWkwh+xl86PPAUOK9DDFl4uiZg==
Date: Wed, 15 May 2013 12:39:06 +0000
Message-ID: <D27C1FD6-F944-4A66-956D-E0B4C857FDCD@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E518160AC4F1904EB874D156A43A56E7@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Mentoring-coordinators] students
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 12:40:38 -0000

Hi,

I'd like to add an addition/modification to the mentoring program. That is,=
 everyone who registers at the student rate gets offered a mentor, independ=
ent of if they have attended more than three times.

I think that makes sense, because these are young folks that would benefit =
a lot from mentoring, maybe more so than someone new with a company affilia=
tion. And we have to few young folks and too few university folks.

Lars=

From acooper@cdt.org  Wed May 15 08:39:41 2013
Return-Path: <acooper@cdt.org>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029CF11E80CC for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 08:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.764
X-Spam-Level: 
X-Spam-Status: No, score=-101.764 tagged_above=-999 required=5 tests=[AWL=0.835, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25kvcwEATvlf for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 08:39:36 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9D72821F90BB for <mentoring-coordinators@ietf.org>; Wed, 15 May 2013 08:39:36 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Wed, 15 May 2013 11:39:33 -0400
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <51922FFB.4070302@mnt.se>
Date: Wed, 15 May 2013 11:39:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE5873CF-043E-48D3-801D-7C900EF8B005@cdt.org>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <51922FFB.4070302@mnt.se>
To: Leif Johansson <leifj@mnt.se>
X-Mailer: Apple Mail (2.1499)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 15:39:41 -0000

On May 14, 2013, at 8:37 AM, Leif Johansson <leifj@mnt.se> wrote:

>>>=20
>>> It probably makes sense to set a deadline by which mentors and =
prot=E9g=E9s need to sign up, after which you all can get to work doing =
the matchings. Suggestions for a deadline?=20
>>>=20
>> I'm not sure we would need the whole set before we started matching - =
maybe we have, and advertise, a date at which we would start
>> (to drive early signup), but do matching up to and at the IETF =
meeting? I would suggest that start date be 1 or two weeks before the =
-00 deadline.
>=20
> sounds reasonable, how many mentorees are we expecting?

No idea. We'll know better after this trial!

So, let's say July 1 for start date?

>=20
>=20
>>=20
>>> The secretariat will be building a database to capture all of the =
info from the web forms. We're still working out how to make that a =
collaborative tool so that you all can work together on the matchings =
and see who has been matched already, etc. If you have thoughts about =
good tools for this, feel free to share.
>> It's dangerous to build too much tool when you're still trying to =
figure out what you really want to be doing - it can cause you to =
accidentally get stuck with a behavior you don't really need. I would =
strongly suggest just starting with a wiki and more manual effort than =
you want in the long run until we know what a tool really needs to help =
with.
>=20
> agree fully.=20

Alright, will let the secretariat know.

>=20
>>> Whether you want to stick to 1:1 matches or allow some 1:more-than-1 =
is up to you and might depend on who you get signed up in both groups.
>>>=20
>>> Brian and I have also discussed opportunities to help mentors and =
prot=E9g=E9s meet at the beginning of IETF week, perhaps in designated =
areas at the newcomers' meet-and-greet. We're still mulling that over =
but would appreciate your thoughts about that.
>>>=20
>>> One last question is whether the fact that you all are coordinating =
the program should be made public. On one hand, it might be helpful for =
people to not know that you're doing the matching, so that no one tries =
to lobby you. Brian and I could certainly front all complaints/lobbying =
in that regard. On the other hand, you will be spending some time on =
this and so I can appreciate that you might want some recognition for =
it. Would be interested in your thoughts about that.
>>>=20
>> When in doubt, fail open.
>>=20
>=20
> +1

Sounds good. In that case I think it would make sense to include your =
names in the mentor solicitation below.

Alissa

>>> Let us know if you have questions.
>>>=20
>>> Thanks,
>>> Alissa
>>>=20
>>> -----------
>>>=20
>>> Subject: IETF Mentor Program
>>>=20
>>> Hi all,
>>>     Based on discussions during IETF 86, we are trialing an IETF =
mentoring program.  During this trial period, we would like to pair =
those who are new to the IETF (people who have attended 3 or fewer =
meetings) with existing IETF participants.  The goal is to provide a =
resource for the new people who can assist them with integrating into =
the IETF community.  Mentors and prot=E9g=E9s (who express an interest =
in being mentored) will be paired prior to IETF 87. We cannot guarantee =
that every mentor or prot=E9g=E9 will be matched, but we'll do our best. =
If the trial goes well, there may be a variety of ways to expand the =
program in the future.
>>>=20
>>>     What we need is for people to volunteer to be mentors. As a =
mentor, we would ask that you be willing to assist your prot=E9g=E9 =
before, during, and (hopefully) after IETF 87.  The actual level of =
interaction will be driven by an agreement between the mentor and the =
mentee. Additionally, we would need a brief description of your areas of =
expertise, technical interests, and conversational languages.
>>>=20
>>>     People interested in acting as mentors can volunteer by filling =
at the form at ???.  An FAQ for this trial program is available here: =
???.
>>>=20
>>> Regards,
>>> Alissa & Brian
>>>=20
>>=20
>> On the signup forms - consider asking both mentors and protoges (I'm =
worried how the community will react to the term btw) are active in any =
other SDOs, and if they have any non-IETF activities they are passionate =
about.
>>=20
>> RjS
>>>=20
>>>=20
>>> _______________________________________________
>>> mentoring-coordinators mailing list
>>>=20
>>> mentoring-coordinators@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>>=20
>>=20
>>=20
>> _______________________________________________
>> mentoring-coordinators mailing list
>>=20
>> mentoring-coordinators@ietf.org
>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>=20
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators



From acooper@cdt.org  Wed May 15 08:41:09 2013
Return-Path: <acooper@cdt.org>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98F8321F8ED8 for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 08:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.931
X-Spam-Level: 
X-Spam-Status: No, score=-101.931 tagged_above=-999 required=5 tests=[AWL=0.668, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xA+E2+Rz-dx for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 08:41:04 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 7642721F8EC1 for <mentoring-coordinators@ietf.org>; Wed, 15 May 2013 08:41:04 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Wed, 15 May 2013 11:41:03 -0400
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <51912D11.8030904@nostrum.com>
Date: Wed, 15 May 2013 11:41:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1499)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 15:41:09 -0000

On May 13, 2013, at 2:12 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

>> On the signup forms - consider asking both mentors and protoges (I'm =
worried how the community will react to the term btw) are active in any =
other SDOs, and if they have any non-IETF activities they are passionate =
about.

We have gone around a few times on the term for people being mentored -- =
"mentees," "proteges," "newcomers." None of them seem quite right. Send =
suggestions if you have them.

Agree on asking about other SDOs and non-IETF activities.

Alissa




From rjsparks@nostrum.com  Wed May 15 10:44:05 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2459F21F9051 for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 10:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROcdP0fHXeV8 for <mentoring-coordinators@ietfa.amsl.com>; Wed, 15 May 2013 10:44:04 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 948C621F901D for <mentoring-coordinators@ietf.org>; Wed, 15 May 2013 10:44:04 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-071-029.mycingular.net [166.147.71.29]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4FHhjQn009689 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Wed, 15 May 2013 12:43:46 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5193C94C.3070405@nostrum.com>
Date: Wed, 15 May 2013 12:43:40 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org>
In-Reply-To: <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org>
Content-Type: multipart/alternative; boundary="------------080505020900030704020209"
Received-SPF: pass (shaman.nostrum.com: 166.147.71.29 is authenticated by a trusted mechanism)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 17:44:05 -0000

This is a multi-part message in MIME format.
--------------080505020900030704020209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 5/15/13 10:41 AM, Alissa Cooper wrote:
> On May 13, 2013, at 2:12 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>
>>> On the signup forms - consider asking both mentors and protoges (I'm worried how the community will react to the term btw) are active in any other SDOs, and if they have any non-IETF activities they are passionate about.
> We have gone around a few times on the term for people being mentored -- "mentees," "proteges," "newcomers." None of them seem quite right. Send suggestions if you have them.
Brainstorming (assisted by a random walk through a few thesaurus sites):

rookie, tenderfoot, enthusiast, scholar, learner

(fwiw - several sites went out of their way to show different gender 
forms for protégé)
>
> Agree on asking about other SDOs and non-IETF activities.
>
> Alissa
>
>
>


--------------080505020900030704020209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 5/15/13 10:41 AM, Alissa Cooper
      wrote:<br>
    </div>
    <blockquote cite="mid:154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org"
      type="cite">
      <pre wrap="">On May 13, 2013, at 2:12 PM, Robert Sparks <a class="moz-txt-link-rfc2396E" href="mailto:rjsparks@nostrum.com">&lt;rjsparks@nostrum.com&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">On the signup forms - consider asking both mentors and protoges (I'm worried how the community will react to the term btw) are active in any other SDOs, and if they have any non-IETF activities they are passionate about.
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
We have gone around a few times on the term for people being mentored -- "mentees," "proteges," "newcomers." None of them seem quite right. Send suggestions if you have them.</pre>
    </blockquote>
    Brainstorming (assisted by a random walk through a few thesaurus
    sites):<br>
    <br>
    rookie, tenderfoot, enthusiast, scholar, learner<br>
    <br>
    (fwiw - several sites went out of their way to show different gender
    forms for prot&eacute;g&eacute;)
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <blockquote cite="mid:154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org"
      type="cite">
      <pre wrap="">

Agree on asking about other SDOs and non-IETF activities.

Alissa



</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080505020900030704020209--

From lars@netapp.com  Thu May 16 00:02:09 2013
Return-Path: <lars@netapp.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E15A21F905F for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 00:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.683
X-Spam-Level: 
X-Spam-Status: No, score=-9.683 tagged_above=-999 required=5 tests=[AWL=0.916,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZQFjTvJ6BX8 for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 00:02:04 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id A04531F0D11 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 00:02:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,681,1363158000"; d="scan'208";a="25320674"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 16 May 2013 00:02:00 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4G71x6K015310; Thu, 16 May 2013 00:02:00 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Thu, 16 May 2013 00:01:59 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Mentoring-coordinators] Kicking off mentoring-coordinators
Thread-Index: AQHOT/of6cYtNbCh30WAuPm+ROTrEZkD4EWAgAL6WICAACI/AIAA3w4A
Date: Thu, 16 May 2013 07:01:59 +0000
Message-ID: <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org> <5193C94C.3070405@nostrum.com>
In-Reply-To: <5193C94C.3070405@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <533104A1E3D50A4E8C5091B6EEF00E8D@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mentoring-coordinators@ietf.org>" <mentoring-coordinators@ietf.org>, Alissa Cooper <acooper@cdt.org>
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 07:02:09 -0000

On May 15, 2013, at 19:43, Robert Sparks <rjsparks@nostrum.com> wrote:
> rookie, tenderfoot, enthusiast, scholar, learner

talent
newbie
hopeful
fellow
trainee

Another thought: For new hires at NetApp, we assign a buddy. Both the mento=
r and the protege are simply called buddies. It's kinda nice, because it im=
plies some sort of equivalence between the two rather than a hierarchy.

Lars=

From leifj@mnt.se  Thu May 16 01:19:54 2013
Return-Path: <leifj@mnt.se>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B84421F8F24 for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 01:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ME40PSkyKv3l for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 01:19:52 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6C22E21F8733 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 01:19:50 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id fg20so469034lab.15 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 01:19:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=1zXA5hznimOmCI1x34kH2zBDiUmYB67Fdc6XCdSVDXI=; b=Je6fRDQVd5gHBP8MIvsQGqknnYw6n34RcaxSw6h01QyMotp8yQfcMPvVt6j64Gh/4i KBpneBHPN3uDaB3wTur+7AM1Gra7WFtW4pLxeAu+b9E4UMUrU4NNgFfUIU4TtStExQa3 yS0YlKLbLDhxigHut6xuRipEn95Mhywss8EolPMO30isQimh8IeQDqwY6WcB1CD5y5hI sp4Ysi5eUj2MKMfYmCjjfZcCZm824WwR0KnZ849mjSLn9QqiCoQbdbKzCPfBUE+i8gGB 9bzU/xaEIpL1NjDFsRGkIUSgTftOpsqZWEAeJOEzUTTxi9GmaaXc5q4Sevx3989Ooyza gM9Q==
X-Received: by 10.112.156.133 with SMTP id we5mr19553203lbb.22.1368692389839;  Thu, 16 May 2013 01:19:49 -0700 (PDT)
Received: from [193.11.93.223] (eduroam-93-223.public.su.se. [193.11.93.223]) by mx.google.com with ESMTPSA id c5sm2703559lbe.1.2013.05.16.01.19.47 for <mentoring-coordinators@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 01:19:48 -0700 (PDT)
Message-ID: <519496A3.8050402@mnt.se>
Date: Thu, 16 May 2013 10:19:47 +0200
From: Leif Johansson <leifj@mnt.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: mentoring-coordinators@ietf.org
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org> <5193C94C.3070405@nostrum.com> <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com>
In-Reply-To: <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQmDFNLkYH9PSWxDmhlOouu/roHwbpuvUZOqgtIO3zUGmXdbUjArWqh+QSfDRFjhr0+nuIdx
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 08:19:54 -0000

On 05/16/2013 09:01 AM, Eggert, Lars wrote:
> On May 15, 2013, at 19:43, Robert Sparks <rjsparks@nostrum.com> wrote:
>> rookie, tenderfoot, enthusiast, scholar, learner
> talent
> newbie
> hopeful
> fellow
> trainee
>
> Another thought: For new hires at NetApp, we assign a buddy. Both the mentor and the protege are simply called buddies. It's kinda nice, because it implies some sort of equivalence between the two rather than a hierarchy.
>
>
The social context of an employee is quite different from that of an IETF
"greenhorn". I think we want to avoid terms that could have (even the
slightest) perojative connotation.

        MVH leifj

From acooper@cdt.org  Thu May 16 06:28:19 2013
Return-Path: <acooper@cdt.org>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F20A21F8D71 for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level: 
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwG6Em-jon-v for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:28:15 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 13CE021F89A6 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:28:15 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Thu, 16 May 2013 09:28:13 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <519496A3.8050402@mnt.se>
Date: Thu, 16 May 2013 09:28:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DA0404A-B1E5-4CC4-A2D7-AAEE7EB46B0B@cdt.org>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org> <5193C94C.3070405@nostrum.com> <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com> <519496A3.8050402@mnt.se>
To: Leif Johansson <leifj@mnt.se>
X-Mailer: Apple Mail (2.1499)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:28:19 -0000

What if we just call them participants? We could have mentors and =
mentoring participants.

On May 16, 2013, at 4:19 AM, Leif Johansson <leifj@mnt.se> wrote:

> On 05/16/2013 09:01 AM, Eggert, Lars wrote:
>> On May 15, 2013, at 19:43, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>>> rookie, tenderfoot, enthusiast, scholar, learner
>> talent
>> newbie
>> hopeful
>> fellow
>> trainee
>>=20
>> Another thought: For new hires at NetApp, we assign a buddy. Both the =
mentor and the protege are simply called buddies. It's kinda nice, =
because it implies some sort of equivalence between the two rather than =
a hierarchy.
>>=20
>>=20
> The social context of an employee is quite different from that of an =
IETF
> "greenhorn". I think we want to avoid terms that could have (even the
> slightest) perojative connotation.
>=20
>        MVH leifj
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>=20



From leifj@mnt.se  Thu May 16 06:37:50 2013
Return-Path: <leifj@mnt.se>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6DA21F934B for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSswvpn6Owfq for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:37:50 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id EC79121F9347 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:37:49 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id fg20so776735lab.15 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:37:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=0vL/3/TZcyexYDPz+0mHMDfo40G2gAg3y3u/MtDHLJE=; b=obTSspDTrZwxN8O0ezk3YJia0BS24SyMzep2nj6lzS4DSDPos9QE1oq26EHRWFm1zB h/hgII0rPncveChTGY3rwSRTW2j0fWjTgze9qL6eqGXaBkxz2K6sVrtlXknuJXyJRu4l /qvwPFTqnuB0khQENbrHEYnwYFzkqphwpTk2/0lC9LhuYjoKTncIVDUKCtcIfsUvjLja tKGsNmtjvk0pZ8Wk9t4KSO8fKjt8HaqOdXai8r6NHD+S2npu9o8HJp3EyUl0G/5aWcYG BKGTYzmqRuEB6z1UPR3g991ujrVXJqq8tBGV0f8vsflFavLLK85LCFnYy22evnwT5VgL jLFA==
X-Received: by 10.152.8.37 with SMTP id o5mr13025843laa.1.1368711468798; Thu, 16 May 2013 06:37:48 -0700 (PDT)
Received: from [77.238.32.74] (eduroam-32-74.public.su.se. [77.238.32.74]) by mx.google.com with ESMTPSA id n5sm3148010lbe.15.2013.05.16.06.37.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 06:37:47 -0700 (PDT)
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org> <5193C94C.3070405@nostrum.com> <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com> <519496A3.8050402@mnt.se> <4DA0404A-B1E5-4CC4-A2D7-AAEE7EB46B0B@cdt.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <4DA0404A-B1E5-4CC4-A2D7-AAEE7EB46B0B@cdt.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB30CC2E-4B9A-4C48-A1FF-DC60B9FD8728@mnt.se>
X-Mailer: iPhone Mail (10B350)
From: Leif Johansson <leifj@mnt.se>
Date: Thu, 16 May 2013 15:37:45 +0200
To: Alissa Cooper <acooper@cdt.org>
X-Gm-Message-State: ALoCoQlUElGPKfO7fmwRfPsp+ZmuaX1MrVsnEBtE2CpGIRaRaYXiHueZ4b1Fau5GV4VCIc5UCbMz
Cc: "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:37:50 -0000

16 maj 2013 kl. 15:28 skrev Alissa Cooper <acooper@cdt.org>:

> What if we just call them participants? We could have mentors and mentorin=
g participants.

good & simple

>=20
> On May 16, 2013, at 4:19 AM, Leif Johansson <leifj@mnt.se> wrote:
>=20
>> On 05/16/2013 09:01 AM, Eggert, Lars wrote:
>>> On May 15, 2013, at 19:43, Robert Sparks <rjsparks@nostrum.com> wrote:
>>>> rookie, tenderfoot, enthusiast, scholar, learner
>>> talent
>>> newbie
>>> hopeful
>>> fellow
>>> trainee
>>>=20
>>> Another thought: For new hires at NetApp, we assign a buddy. Both the me=
ntor and the protege are simply called buddies. It's kinda nice, because it i=
mplies some sort of equivalence between the two rather than a hierarchy.
>> The social context of an employee is quite different from that of an IETF
>> "greenhorn". I think we want to avoid terms that could have (even the
>> slightest) perojative connotation.
>>=20
>>       MVH leifj
>> _______________________________________________
>> mentoring-coordinators mailing list
>> mentoring-coordinators@ietf.org
>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>=20
>=20

From rdroms.ietf@gmail.com  Thu May 16 06:46:11 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3FB921F8FFA for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VzCxI15VK0xH for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:46:07 -0700 (PDT)
Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) by ietfa.amsl.com (Postfix) with ESMTP id 2BAA321F8F28 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:46:07 -0700 (PDT)
Received: by mail-gh0-f181.google.com with SMTP id z12so613959ghb.12 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=9jw2EHCB0UMLEL32KFfw50QY6XhNkXLfnH+LoG4uG70=; b=jUpQtIFhgg2WWUTvCKWHEkDdTik3yJsEsezYLh8xSjW1V937IZVhEHe1ZnE1q90+Ql gK1mT2Pq2JoGZQ4BNd7gw4EeMdlqjNAZe/dq4jGaR8ZpmUeX0a7a3JwpHstKk9vItSzT jcJuepZ1vKcnClzzidTmXnQ6sbEeWAoh+21+0JBrprcgO47CDvyBcn13mLvRyhn2QyPU 81Wb96dnM4sh+YdGbQxBbTao/EN7KCNqGAmcx5du5DFIvhontreq+mOu3czUZXP7Cx/2 Pke/CWpzgILDJ8yefD2rEWa0h030btJJMSN0h9Kq+hDNb6o0ehPf7CvCFyABxUu+KXDv gwCQ==
X-Received: by 10.236.121.172 with SMTP id r32mr21571253yhh.2.1368711966661; Thu, 16 May 2013 06:46:06 -0700 (PDT)
Received: from che-vpn-cluster-1-51.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id w12sm9720085yhj.19.2013.05.16.06.46.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 06:46:05 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <FB30CC2E-4B9A-4C48-A1FF-DC60B9FD8728@mnt.se>
Date: Thu, 16 May 2013 09:45:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC0258C7-B076-495B-938D-BCFFCD65AE62@gmail.com>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org> <5193C94C.3070405@nostrum.com> <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com> <519496A3.8050402@mnt.se> <4DA0404A-B1E5-4CC4-A2D7-AAEE7EB46B0B@cdt.org> <FB30CC2E-4B9A-4C48-A1FF-DC60B9FD8728@mnt.se>
To: Alissa Cooper <acooper@cdt.org>
X-Mailer: Apple Mail (2.1503)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:46:12 -0000

On May 16, 2013, at 9:37 AM 5/16/13, Leif Johansson <leifj@mnt.se> =
wrote:

>=20
>=20
> 16 maj 2013 kl. 15:28 skrev Alissa Cooper <acooper@cdt.org>:
>=20
>> What if we just call them participants? We could have mentors and =
mentoring participants.
>=20
> good & simple

I agree ... I haven't been able to come up with a better alternative. =20=


- Ralph

>=20
>>=20
>> On May 16, 2013, at 4:19 AM, Leif Johansson <leifj@mnt.se> wrote:
>>=20
>>> On 05/16/2013 09:01 AM, Eggert, Lars wrote:
>>>> On May 15, 2013, at 19:43, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>>>>> rookie, tenderfoot, enthusiast, scholar, learner
>>>> talent
>>>> newbie
>>>> hopeful
>>>> fellow
>>>> trainee
>>>>=20
>>>> Another thought: For new hires at NetApp, we assign a buddy. Both =
the mentor and the protege are simply called buddies. It's kinda nice, =
because it implies some sort of equivalence between the two rather than =
a hierarchy.
>>> The social context of an employee is quite different from that of an =
IETF
>>> "greenhorn". I think we want to avoid terms that could have (even =
the
>>> slightest) perojative connotation.
>>>=20
>>>      MVH leifj
>>> _______________________________________________
>>> mentoring-coordinators mailing list
>>> mentoring-coordinators@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>>=20
>>=20
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators


From rdroms.ietf@gmail.com  Thu May 16 06:48:35 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC1521F8C23 for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SI9ZRWws00pL for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:48:34 -0700 (PDT)
Received: from mail-gg0-x230.google.com (mail-gg0-x230.google.com [IPv6:2607:f8b0:4002:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 9618821F8B2B for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:48:34 -0700 (PDT)
Received: by mail-gg0-f176.google.com with SMTP id o5so592885ggn.35 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:48:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=2DiflHbuu3nquCiuljcljpVCG7lFzKICuXNhj8sz+T8=; b=WZCjsw6PdbsMXdd0jdMfvegLjcQzdzpHU0yo/m22BomL05xdFOCzdBpDayKff3lUDv Xh2vdukvOgNUh0x7ze9CCVUqtHvH16Si5zwsOGnpYJ9pwEVb/Sor2qQ/odkJHe0fm0Tk WDWCxQv/WnBpipYXSf7gMHVo2IhxPS/GMDF27crTzUt3ZEoRjT1McDPb0yzgmGGxudyi fTnQr4DYo8anNux8AzWeRHff/q1+Nm5xObwm00tzh1vlOeZ8OHQyGhjcmZIcf7vFIPDG ji3rGM8RNEcnQTY4wAv8rUFOkkIO5uu1KUNUZPPxC/BAj6NUi6bjitvMrMcOAhLYqVNr MZ0Q==
X-Received: by 10.236.188.36 with SMTP id z24mr21313968yhm.96.1368712114132; Thu, 16 May 2013 06:48:34 -0700 (PDT)
Received: from che-vpn-cluster-1-51.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id f71sm9812799yha.8.2013.05.16.06.48.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 06:48:32 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <DE5873CF-043E-48D3-801D-7C900EF8B005@cdt.org>
Date: Thu, 16 May 2013 09:48:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <15350590-4B3A-45E4-9805-CB2949543C73@gmail.com>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <51922FFB.4070302@mnt.se> <DE5873CF-043E-48D3-801D-7C900EF8B005@cdt.org>
To: Alissa Cooper <acooper@cdt.org>
X-Mailer: Apple Mail (2.1503)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:48:35 -0000

On May 15, 2013, at 11:39 AM 5/15/13, Alissa Cooper <acooper@cdt.org> =
wrote:

>=20
> On May 14, 2013, at 8:37 AM, Leif Johansson <leifj@mnt.se> wrote:
>=20
>>>>=20
>>>> It probably makes sense to set a deadline by which mentors and =
prot=E9g=E9s need to sign up, after which you all can get to work doing =
the matchings. Suggestions for a deadline?=20
>>>>=20
>>> I'm not sure we would need the whole set before we started matching =
- maybe we have, and advertise, a date at which we would start
>>> (to drive early signup), but do matching up to and at the IETF =
meeting? I would suggest that start date be 1 or two weeks before the =
-00 deadline.
>>=20
>> sounds reasonable, how many mentorees are we expecting?
>=20
> No idea. We'll know better after this trial!
>=20
> So, let's say July 1 for start date?

Sounds fine. =20

>=20
>>=20
>>=20
>>>=20
>>>> The secretariat will be building a database to capture all of the =
info from the web forms. We're still working out how to make that a =
collaborative tool so that you all can work together on the matchings =
and see who has been matched already, etc. If you have thoughts about =
good tools for this, feel free to share.
>>> It's dangerous to build too much tool when you're still trying to =
figure out what you really want to be doing - it can cause you to =
accidentally get stuck with a behavior you don't really need. I would =
strongly suggest just starting with a wiki and more manual effort than =
you want in the long run until we know what a tool really needs to help =
with.
>>=20
>> agree fully.=20

Me, too...

>=20
> Alright, will let the secretariat know.
>=20
>>=20
>>>> Whether you want to stick to 1:1 matches or allow some =
1:more-than-1 is up to you and might depend on who you get signed up in =
both groups.
>>>>=20
>>>> Brian and I have also discussed opportunities to help mentors and =
prot=E9g=E9s meet at the beginning of IETF week, perhaps in designated =
areas at the newcomers' meet-and-greet. We're still mulling that over =
but would appreciate your thoughts about that.
>>>>=20
>>>> One last question is whether the fact that you all are coordinating =
the program should be made public. On one hand, it might be helpful for =
people to not know that you're doing the matching, so that no one tries =
to lobby you. Brian and I could certainly front all complaints/lobbying =
in that regard. On the other hand, you will be spending some time on =
this and so I can appreciate that you might want some recognition for =
it. Would be interested in your thoughts about that.
>>>>=20
>>> When in doubt, fail open.
>>>=20
>>=20
>> +1

I agree.

>=20
> Sounds good. In that case I think it would make sense to include your =
names in the mentor solicitation below.
>=20
> Alissa

- Ralph

>=20
>>>> Let us know if you have questions.
>>>>=20
>>>> Thanks,
>>>> Alissa
>>>>=20
>>>> -----------
>>>>=20
>>>> Subject: IETF Mentor Program
>>>>=20
>>>> Hi all,
>>>>    Based on discussions during IETF 86, we are trialing an IETF =
mentoring program.  During this trial period, we would like to pair =
those who are new to the IETF (people who have attended 3 or fewer =
meetings) with existing IETF participants.  The goal is to provide a =
resource for the new people who can assist them with integrating into =
the IETF community.  Mentors and prot=E9g=E9s (who express an interest =
in being mentored) will be paired prior to IETF 87. We cannot guarantee =
that every mentor or prot=E9g=E9 will be matched, but we'll do our best. =
If the trial goes well, there may be a variety of ways to expand the =
program in the future.
>>>>=20
>>>>    What we need is for people to volunteer to be mentors. As a =
mentor, we would ask that you be willing to assist your prot=E9g=E9 =
before, during, and (hopefully) after IETF 87.  The actual level of =
interaction will be driven by an agreement between the mentor and the =
mentee. Additionally, we would need a brief description of your areas of =
expertise, technical interests, and conversational languages.
>>>>=20
>>>>    People interested in acting as mentors can volunteer by filling =
at the form at ???.  An FAQ for this trial program is available here: =
???.
>>>>=20
>>>> Regards,
>>>> Alissa & Brian
>>>>=20
>>>=20
>>> On the signup forms - consider asking both mentors and protoges (I'm =
worried how the community will react to the term btw) are active in any =
other SDOs, and if they have any non-IETF activities they are passionate =
about.
>>>=20
>>> RjS
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> mentoring-coordinators mailing list
>>>>=20
>>>> mentoring-coordinators@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> mentoring-coordinators mailing list
>>>=20
>>> mentoring-coordinators@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>>=20
>> _______________________________________________
>> mentoring-coordinators mailing list
>> mentoring-coordinators@ietf.org
>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>=20
>=20
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators


From rbonica@juniper.net  Thu May 16 06:55:37 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21E9021F9354 for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kfd-Jy0unp4F for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:55:31 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE6521F9344 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:55:31 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUZTlUgS6rnnwpZMRlYNLScRxwwvXFieU@postini.com; Thu, 16 May 2013 06:55:31 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 16 May 2013 06:51:45 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Thu, 16 May 2013 06:51:44 -0700
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.14) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 16 May 2013 06:54:38 -0700
Received: from mail20-tx2-R.bigfish.com (10.9.14.230) by TX2EHSOBE012.bigfish.com (10.9.40.32) with Microsoft SMTP Server id 14.1.225.23; Thu, 16 May 2013 13:51:43 +0000
Received: from mail20-tx2 (localhost [127.0.0.1])	by mail20-tx2-R.bigfish.com (Postfix) with ESMTP id C8A673601BA	for <mentoring-coordinators@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 16 May 2013 13:51:43 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275bh8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1155h)
Received: from mail20-tx2 (localhost.localdomain [127.0.0.1]) by mail20-tx2 (MessageSwitch) id 1368712301418530_11077; Thu, 16 May 2013 13:51:41 +0000 (UTC)
Received: from TX2EHSMHS039.bigfish.com (unknown [10.9.14.238])	by mail20-tx2.bigfish.com (Postfix) with ESMTP id 55A5820004D; Thu, 16 May 2013 13:51:41 +0000 (UTC)
Received: from BY2PRD0512HT004.namprd05.prod.outlook.com (157.56.238.5) by TX2EHSMHS039.bigfish.com (10.9.99.139) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 16 May 2013 13:51:39 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.43]) by BY2PRD0512HT004.namprd05.prod.outlook.com ([10.255.243.37]) with mapi id 14.16.0311.000; Thu, 16 May 2013 13:51:38 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Eggert, Lars" <lars@netapp.com>, Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Mentoring-coordinators] Kicking off mentoring-coordinators
Thread-Index: AQHOT/opM5AaHwPByEiZq6HzV+gVbJkDauyAgAL6WICAACJAAIAA3wyAgAByN1A=
Date: Thu, 16 May 2013 13:51:37 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2509EEDB34@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <154FE74A-4986-4BD2-91DB-D8DFA43C08F8@cdt.org> <5193C94C.3070405@nostrum.com> <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com>
In-Reply-To: <5C9EB068-8CBF-4110-B2BF-DAB979D08E42@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%NETAPP.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%NOSTRUM.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%CDT.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "<mentoring-coordinators@ietf.org>" <mentoring-coordinators@ietf.org>, Alissa Cooper <acooper@cdt.org>
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:55:37 -0000

+1

Teachers and students are people who learn together!

                        Ron


> -----Original Message-----
> From: mentoring-coordinators-bounces@ietf.org [mailto:mentoring-
> coordinators-bounces@ietf.org] On Behalf Of Eggert, Lars
> Sent: Thursday, May 16, 2013 3:02 AM
> To: Robert Sparks
> Cc: <mentoring-coordinators@ietf.org>; Alissa Cooper
> Subject: Re: [Mentoring-coordinators] Kicking off mentoring-
> coordinators
>=20
> On May 15, 2013, at 19:43, Robert Sparks <rjsparks@nostrum.com> wrote:
> > rookie, tenderfoot, enthusiast, scholar, learner
>=20
> talent
> newbie
> hopeful
> fellow
> trainee
>=20
> Another thought: For new hires at NetApp, we assign a buddy. Both the
> mentor and the protege are simply called buddies. It's kinda nice,
> because it implies some sort of equivalence between the two rather than
> a hierarchy.
>=20
> Lars
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators



From rdroms.ietf@gmail.com  Thu May 16 06:55:56 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A77F21F8F61 for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level: 
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tA429+GrR1zD for <mentoring-coordinators@ietfa.amsl.com>; Thu, 16 May 2013 06:55:55 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 57F0121F9344 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:55:54 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s11so1064828qcw.1 for <mentoring-coordinators@ietf.org>; Thu, 16 May 2013 06:55:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=Y4qJlUFwLebsoR6iY5rQmIiB40NFAZVe4bodYmEwbTA=; b=g+a8UYGjslcUd5NVBWZu26bHqhtkIPbAyj2/ETSGOKE13oug3GN5tdLBlHivh3R0Dw xXjhlyQAPFZEFqjjT99GIJTXb8bb0rOekrGx55NApIVMAc8EeB42obLq18hr3dq9hLI8 bfMbt8nzumRvWDDN8ZXHG3pyNIPwZo8fZ29NQt5OuyG0VZnPAxVmO9e4uUmGEVlIpVa9 6YJEwmTGyK1nV0H9CvtkrtdjbFN+mmu7aHATs9urPMfU3+brygeCv4p+soCc5UZW/HVh uts9a8vPGkAcpFHE1u5GnmdCKEM77L7A4ubau/MD32w1KrIdOB46DQfI2WD8yimr3yj0 9jzg==
X-Received: by 10.49.12.35 with SMTP id v3mr5891212qeb.6.1368712553805; Thu, 16 May 2013 06:55:53 -0700 (PDT)
Received: from che-vpn-cluster-1-51.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id do6sm6911823qab.12.2013.05.16.06.55.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 06:55:51 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <8DD4EB91-1051-4BBC-BCF3-A881F7ADAC1B@netapp.com>
Date: Thu, 16 May 2013 09:55:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <98DF3141-4F0B-4BB4-9E78-B33B571AD603@gmail.com>
References: <C8DAD0FA-5B60-4782-A60C-90B57C2E40D2@cdt.org> <51912D11.8030904@nostrum.com> <8DD4EB91-1051-4BBC-BCF3-A881F7ADAC1B@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1503)
Cc: mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Kicking off mentoring-coordinators
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:55:56 -0000

On May 15, 2013, at 7:38 AM 5/15/13, "Eggert, Lars" <lars@netapp.com> =
wrote:

> Hi,
>=20
> On May 13, 2013, at 20:12, Robert Sparks <rjsparks@nostrum.com> wrote:
>> On 5/13/13 11:51 AM, Alissa Cooper wrote:
>>> The secretariat will be building an IETF Mentoring page linked from =
the main IETF site. The site will contain FAQs about the program and web =
forms that allow people to sign up to be mentors or to be prot=E9g=E9s. =
Our current thinking is to limit the prot=E9g=E9 pool to anyone who has =
attended three or fewer IETF meetings, and to limit the mentor pool to =
anyone who is nomcom eligible. We could change the prot=E9g=E9 limit in =
the future, but since this is an experiment we'd like to keep it =
somewhat limited for now and see how it works. Both the FAQs and the web =
form fields are attached for your review and comment.
>=20
> during the IAB retreat, the point was brought up that it would be =
helpful that mentors could recall their first exposure to the IETF =
clearly, i.e., maybe not the folks who have been coming for 20 years. =
But we don't need to have a hard rule here, we can just take this into =
account when we do the matching.

Interesting point.  I can clearly remember my first exposure to the IETF =
(which was more than 20 years ago), and it's either clearly irrelevant =
and OBE, or gives us a model for 1x1 introductions in the future...

At the time I first started in the IETF (1989), Phill Gross was IETF =
Chair.  He had been a grad student TA for me a decade earlier, and we =
stayed in touch.  When the DHCP problem came along, he suggested I might =
find it interesting, and we formed the dhc WG.

On the one hand, it's not likely anyone coming to the IETF now will have =
been a grad student with a current IETF chair.  On the other hand, it =
was that 1x1 relationship and introduction that drove my engagement at =
the WG chair level.

- Ralph

>=20
>>> [...]
>=20
> Lars



From amorris@amsl.com  Fri May 24 15:37:46 2013
Return-Path: <amorris@amsl.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 096E711E812D for <mentoring-coordinators@ietfa.amsl.com>; Fri, 24 May 2013 15:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OLir0QH+VMvk for <mentoring-coordinators@ietfa.amsl.com>; Fri, 24 May 2013 15:37:45 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 7B20711E812B for <mentoring-coordinators@ietf.org>; Fri, 24 May 2013 15:37:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 763DF12B51A; Fri, 24 May 2013 15:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AItYnzGKFWVV; Fri, 24 May 2013 15:37:45 -0700 (PDT)
Received: from [192.168.1.180] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c8a.amsl.com (Postfix) with ESMTPSA id 43EDB12B517; Fri, 24 May 2013 15:37:45 -0700 (PDT)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 24 May 2013 15:37:26 -0700
Message-Id: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com>
To: mentoring-coordinators@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: Brian Haberman <brian@innovationslab.net>, Alissa Cooper <acooper@cdt.org>
Subject: [Mentoring-coordinators] Online Mentorship Support
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 22:37:46 -0000

Hello Volunteer Coordinators,

We are getting ready to build some simple online tools to support the =
new mentorship program. What we have been envisioning to date is =
something along the following lines:

- An online form that allows mentors to sign up
- An online form that allows proteges to sign up to request mentoring
- A way for mentoring coordinators to match mentors with proteges. The =
system would then generate an email that would introduce them to each =
other and the match would be logged into the system.=20

I understand that some of you have thought that a simple wiki would be =
sufficient to perform the matching. That's fine if that's all you want, =
but we are happy to provide you with a bit more and will be able to do =
so in early June. Can you please provide feedback and/or direction on =
how we should proceed?

Thanks much,
Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From lars@netapp.com  Sat May 25 01:37:55 2013
Return-Path: <lars@netapp.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19DB721F93C4 for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 01:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.205
X-Spam-Level: 
X-Spam-Status: No, score=-12.205 tagged_above=-999 required=5 tests=[AWL=2.394, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CIQARXDIV8N9 for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 01:37:50 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1103621F9458 for <mentoring-coordinators@ietf.org>; Sat, 25 May 2013 01:37:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,739,1363158000"; d="scan'208";a="57671251"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 25 May 2013 01:37:48 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4P8blWc023871; Sat, 25 May 2013 01:37:47 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Sat, 25 May 2013 01:37:47 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Alexa Morris <amorris@amsl.com>
Thread-Topic: [Mentoring-coordinators] Online Mentorship Support
Thread-Index: AQHOWM9R9lWgsterhUGJ0niLkJduIZkWCfwA
Date: Sat, 25 May 2013 08:37:46 +0000
Message-ID: <94C2576D-EA67-4523-A52E-3BC62A94718C@netapp.com>
References: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com>
In-Reply-To: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31864B009F351245B3E49274A2035743@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mentoring-coordinators@ietf.org>" <mentoring-coordinators@ietf.org>, Alissa Cooper <acooper@cdt.org>, Brian Haberman <brian@innovationslab.net>
Subject: Re: [Mentoring-coordinators] Online Mentorship Support
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2013 08:37:55 -0000

Hi,

On May 25, 2013, at 0:37, Alexa Morris <amorris@amsl.com> wrote:
> We are getting ready to build some simple online tools to support the new=
 mentorship program.

I'm not sure we need tools quite yet. At least for this initial round, emai=
l should suffice?

> What we have been envisioning to date is something along the following li=
nes:
>=20
> - An online form that allows mentors to sign up

Why not just email to mentoring-coordinators@ietf.org?

> - An online form that allows proteges to sign up to request mentoring

Why not just email to mentoring-coordinators@ietf.org?

(More important IMO is that we word a prestigious-sounding invitation lette=
r in Jari's name to the potential proteges that really wants them to sign u=
p...)

> - A way for mentoring coordinators to match mentors with proteges. The sy=
stem would then generate an email that would introduce them to each other a=
nd the match would be logged into the system.=20

Why can't they just email each other once we match them up?

> I understand that some of you have thought that a simple wiki would be su=
fficient to perform the matching. That's fine if that's all you want, but w=
e are happy to provide you with a bit more and will be able to do so in ear=
ly June. Can you please provide feedback and/or direction on how we should =
proceed?

I think a wiki for us to coordinate, and email for everything else should b=
e enough for now. But if others want tools, that's fine with me too.

Lars=

From rbonica@juniper.net  Sat May 25 06:31:42 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1B421F8ADF for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 06:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QL5OiAWWp5Ye for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 06:31:37 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id D7D8821F8AD8 for <mentoring-coordinators@ietf.org>; Sat, 25 May 2013 06:31:36 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUaC9OLPkc0D8lp5I+BmQNuHawM5oRQbb@postini.com; Sat, 25 May 2013 06:31:36 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 25 May 2013 06:31:19 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Sat, 25 May 2013 06:31:18 -0700
Received: from va3outboundpool.messaging.microsoft.com (216.32.180.16) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sat, 25 May 2013 06:42:03 -0700
Received: from mail101-va3-R.bigfish.com (10.7.14.232) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Sat, 25 May 2013 13:31:17 +0000
Received: from mail101-va3 (localhost [127.0.0.1])	by mail101-va3-R.bigfish.com (Postfix) with ESMTP id 8DD2F2C022B	for <mentoring-coordinators@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Sat, 25 May 2013 13:31:17 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -24
X-BigFish: PS-24(zz9371I542I1432I62a3Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah18602eh8275bh8275dhz31h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1155h)
Received-SPF: softfail (mail101-va3: transitioning domain of juniper.net does not designate 157.56.238.5 as permitted sender) client-ip=157.56.238.5; envelope-from=rbonica@juniper.net; helo=BY2PRD0512HT004.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail101-va3 (localhost.localdomain [127.0.0.1]) by mail101-va3 (MessageSwitch) id 1369488675384788_26614; Sat, 25 May 2013 13:31:15 +0000 (UTC)
Received: from VA3EHSMHS015.bigfish.com (unknown [10.7.14.247])	by mail101-va3.bigfish.com (Postfix) with ESMTP id 4FCB8220071; Sat, 25 May 2013 13:31:15 +0000 (UTC)
Received: from BY2PRD0512HT004.namprd05.prod.outlook.com (157.56.238.5) by VA3EHSMHS015.bigfish.com (10.7.99.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 25 May 2013 13:31:11 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.27]) by BY2PRD0512HT004.namprd05.prod.outlook.com ([10.255.243.37]) with mapi id 14.16.0311.000; Sat, 25 May 2013 13:31:07 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Alexa Morris <amorris@amsl.com>, "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
Thread-Topic: [Mentoring-coordinators] Online Mentorship Support
Thread-Index: AQHOWM9XXHcZNBdzgEqOZeWW8vV/p5kV5nWw
Date: Sat, 25 May 2013 13:31:07 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2509F10388@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com>
In-Reply-To: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%AMSL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%INNOVATIONSLAB.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%CDT.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: Brian Haberman <brian@innovationslab.net>, Alissa Cooper <acooper@cdt.org>
Subject: Re: [Mentoring-coordinators] Online Mentorship Support
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2013 13:31:42 -0000

Alexa,

Until we really understand what we need, a Wiki will probably do.

                                    Ron


> -----Original Message-----
> From: mentoring-coordinators-bounces@ietf.org [mailto:mentoring-
> coordinators-bounces@ietf.org] On Behalf Of Alexa Morris
> Sent: Friday, May 24, 2013 6:37 PM
> To: mentoring-coordinators@ietf.org
> Cc: Brian Haberman; Alissa Cooper
> Subject: [Mentoring-coordinators] Online Mentorship Support
>=20
> Hello Volunteer Coordinators,
>=20
> We are getting ready to build some simple online tools to support the
> new mentorship program. What we have been envisioning to date is
> something along the following lines:
>=20
> - An online form that allows mentors to sign up
> - An online form that allows proteges to sign up to request mentoring
> - A way for mentoring coordinators to match mentors with proteges. The
> system would then generate an email that would introduce them to each
> other and the match would be logged into the system.
>=20
> I understand that some of you have thought that a simple wiki would be
> sufficient to perform the matching. That's fine if that's all you want,
> but we are happy to provide you with a bit more and will be able to do
> so in early June. Can you please provide feedback and/or direction on
> how we should proceed?
>=20
> Thanks much,
> Alexa
>=20
> ----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>=20
> Managed by Association Management Solutions (AMS) Forum Management,
> Meeting and Event Planning www.amsl.com <http://www.amsl.com/>
>=20
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators



From acooper@cdt.org  Sat May 25 07:36:08 2013
Return-Path: <acooper@cdt.org>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A525521F8A53 for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 07:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.369
X-Spam-Level: 
X-Spam-Status: No, score=-104.369 tagged_above=-999 required=5 tests=[AWL=2.230, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbAPvSt7zu8a for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 07:36:04 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 604ED21F89FD for <mentoring-coordinators@ietf.org>; Sat, 25 May 2013 07:36:04 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Sat, 25 May 2013 10:35:49 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <94C2576D-EA67-4523-A52E-3BC62A94718C@netapp.com>
Date: Sat, 25 May 2013 10:35:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC9B78CD-D117-4862-B4F5-3AD84E13D8E0@cdt.org>
References: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com> <94C2576D-EA67-4523-A52E-3BC62A94718C@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1499)
Cc: Alexa Morris <amorris@amsl.com>, mentoring-coordinators@ietf.org
Subject: Re: [Mentoring-coordinators] Online Mentorship Support
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2013 14:36:08 -0000

On May 25, 2013, at 4:37 AM, "Eggert, Lars" <lars@netapp.com> wrote:

> Hi,
>=20
> On May 25, 2013, at 0:37, Alexa Morris <amorris@amsl.com> wrote:
>> We are getting ready to build some simple online tools to support the =
new mentorship program.
>=20
> I'm not sure we need tools quite yet. At least for this initial round, =
email should suffice?
>=20
>> What we have been envisioning to date is something along the =
following lines:
>>=20
>> - An online form that allows mentors to sign up
>=20
> Why not just email to mentoring-coordinators@ietf.org?
>=20
>> - An online form that allows proteges to sign up to request mentoring
>=20
> Why not just email to mentoring-coordinators@ietf.org?

My thinking on the forms was that if we have forms then you'll have a =
better chance of getting all of the info from everyone who signs up, =
which might make a difference for the matching.

>=20
> (More important IMO is that we word a prestigious-sounding invitation =
letter in Jari's name to the potential proteges that really wants them =
to sign up...)
>=20
>> - A way for mentoring coordinators to match mentors with proteges. =
The system would then generate an email that would introduce them to =
each other and the match would be logged into the system.=20
>=20
> Why can't they just email each other once we match them up?

I think an automated nudge here could help encourage mentors to make the =
first contact.

Alissa

>=20
>> I understand that some of you have thought that a simple wiki would =
be sufficient to perform the matching. That's fine if that's all you =
want, but we are happy to provide you with a bit more and will be able =
to do so in early June. Can you please provide feedback and/or direction =
on how we should proceed?
>=20
> I think a wiki for us to coordinate, and email for everything else =
should be enough for now. But if others want tools, that's fine with me =
too.
>=20
> Lars
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>=20



From leifj@mnt.se  Sat May 25 13:01:47 2013
Return-Path: <leifj@mnt.se>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BED321F869F for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 13:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.151
X-Spam-Level: 
X-Spam-Status: No, score=-4.151 tagged_above=-999 required=5 tests=[AWL=1.052,  BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqWFGj+NLbXy for <mentoring-coordinators@ietfa.amsl.com>; Sat, 25 May 2013 13:01:46 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 5026121F8673 for <mentoring-coordinators@ietf.org>; Sat, 25 May 2013 13:01:45 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id ec20so5418393lab.4 for <mentoring-coordinators@ietf.org>; Sat, 25 May 2013 13:01:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=ujtEsTjLA81zJGw0Xv/w6mLBdo2PvBQp4BjQj65G8xM=; b=eXF4t6fT+irN3SXQNjGBtuOUik49yHiKYH+QQDE6ShFT4HnWoIYx5wVagZaLscorZG RGnl2HkecSSOUABGuMsBUbwGcthb0fmghkj4G/yH8Yc4gg3yAfPOM0tPKLkVmlwrYxMb RV//13BxY2iQibv0pTnONKnMU92lLs5JkCRaHmRGJRAeNvJB7lHgI6n56LFOteI7Wrxs DiL7IIsONws11mcmdCHtawKawXaLfPh6LqvFteab5BDI17czWmPcHewgcEgXOs4xy+D/ ntxnkOy/xYF5R+TEK0ci3j/f9l7Dc+2d3tegl2kf+4usDTq2fIsPdTCZcxxSeqaGw7eb NqoA==
X-Received: by 10.112.156.164 with SMTP id wf4mr11075825lbb.76.1369512104606;  Sat, 25 May 2013 13:01:44 -0700 (PDT)
Received: from [10.0.0.194] (tb62-102-145-131.cust.teknikbyran.com. [62.102.145.131]) by mx.google.com with ESMTPSA id f9sm8766995lbf.4.2013.05.25.13.01.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 May 2013 13:01:43 -0700 (PDT)
References: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com> <94C2576D-EA67-4523-A52E-3BC62A94718C@netapp.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <94C2576D-EA67-4523-A52E-3BC62A94718C@netapp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <5342075A-FAFF-42C1-97F0-962F37A5B2E5@mnt.se>
X-Mailer: iPhone Mail (10B350)
From: Leif Johansson <leifj@mnt.se>
Date: Sat, 25 May 2013 22:01:41 +0200
To: "Eggert, Lars" <lars@netapp.com>
X-Gm-Message-State: ALoCoQmo6RECOVnrtXNT0+OXexjdU9ZKkMXx2wIV/seQVLMqUbGcIWJFzsZqCWexSzagsf1HPKaw
Cc: Alexa Morris <amorris@amsl.com>, "<mentoring-coordinators@ietf.org>" <mentoring-coordinators@ietf.org>, Alissa Cooper <acooper@cdt.org>, Brian Haberman <brian@innovationslab.net>
Subject: Re: [Mentoring-coordinators] Online Mentorship Support
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2013 20:01:47 -0000

25 maj 2013 kl. 10:37 skrev "Eggert, Lars" <lars@netapp.com>:

> Hi,
>=20
> On May 25, 2013, at 0:37, Alexa Morris <amorris@amsl.com> wrote:
>> We are getting ready to build some simple online tools to support the new=
 mentorship program.
>=20
> I'm not sure we need tools quite yet. At least for this initial round, ema=
il should suffice?

I agree. Mostly I think we'll end up wrangling both mentors and mentorees in=
to this. Not sure that tools will help here.

>=20
>> What we have been envisioning to date is something along the following li=
nes:
>>=20
>> - An online form that allows mentors to sign up
>=20
> Why not just email to mentoring-coordinators@ietf.org?
>=20
>> - An online form that allows proteges to sign up to request mentoring
>=20
> Why not just email to mentoring-coordinators@ietf.org?
>=20
> (More important IMO is that we word a prestigious-sounding invitation lett=
er in Jari's name to the potential proteges that really wants them to sign u=
p...)
>=20
>> - A way for mentoring coordinators to match mentors with proteges. The sy=
stem would then generate an email that would introduce them to each other an=
d the match would be logged into the system.
>=20
> Why can't they just email each other once we match them up?
>=20
>> I understand that some of you have thought that a simple wiki would be su=
fficient to perform the matching. That's fine if that's all you want, but we=
 are happy to provide you with a bit more and will be able to do so in early=
 June. Can you please provide feedback and/or direction on how we should pro=
ceed?
>=20
> I think a wiki for us to coordinate, and email for everything else should b=
e enough for now. But if others want tools, that's fine with me too.
>=20
> Lars
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators

From rjsparks@nostrum.com  Sun May 26 21:13:45 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 257BF21F92F5 for <mentoring-coordinators@ietfa.amsl.com>; Sun, 26 May 2013 21:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.001
X-Spam-Level: 
X-Spam-Status: No, score=-104.001 tagged_above=-999 required=5 tests=[GB_I_INVITATION=-2, GB_I_LETTER=-2, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HOtTmNTnf9+o for <mentoring-coordinators@ietfa.amsl.com>; Sun, 26 May 2013 21:13:44 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5E121F92B2 for <mentoring-coordinators@ietf.org>; Sun, 26 May 2013 21:13:40 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4R4Db75067749 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <mentoring-coordinators@ietf.org>; Sun, 26 May 2013 23:13:40 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51A2DD6B.20704@nostrum.com>
Date: Sun, 26 May 2013 23:13:31 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mentoring-coordinators@ietf.org
References: <4FD7C772-9A83-40CA-806B-28E93E118EF1@amsl.com> <94C2576D-EA67-4523-A52E-3BC62A94718C@netapp.com> <CC9B78CD-D117-4862-B4F5-3AD84E13D8E0@cdt.org>
In-Reply-To: <CC9B78CD-D117-4862-B4F5-3AD84E13D8E0@cdt.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: Re: [Mentoring-coordinators] Online Mentorship Support
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 04:13:45 -0000

On 5/25/13 9:35 AM, Alissa Cooper wrote:
> On May 25, 2013, at 4:37 AM, "Eggert, Lars" <lars@netapp.com> wrote:
>
>> Hi,
>>
>> On May 25, 2013, at 0:37, Alexa Morris <amorris@amsl.com> wrote:
>>> We are getting ready to build some simple online tools to support the new mentorship program.
>> I'm not sure we need tools quite yet. At least for this initial round, email should suffice?
I'm also very reticent to invest in much tooling right now.
>>
>>> What we have been envisioning to date is something along the following lines:
>>>
>>> - An online form that allows mentors to sign up
>> Why not just email to mentoring-coordinators@ietf.org?
>>
>>> - An online form that allows proteges to sign up to request mentoring
>> Why not just email to mentoring-coordinators@ietf.org?
> My thinking on the forms was that if we have forms then you'll have a better chance of getting all of the info from everyone who signs up, which might make a difference for the matching.
That hasn't been my experience with signups for events. I get pretty 
much the same whether people have textboxes to fill in or a list of 
questions to answer in an email message. I don't object to a simple form 
for folks to fill out, but I don't see a big return on the effort
there either.
>
>> (More important IMO is that we word a prestigious-sounding invitation letter in Jari's name to the potential proteges that really wants them to sign up...)
>>
>>> - A way for mentoring coordinators to match mentors with proteges. The system would then generate an email that would introduce them to each other and the match would be logged into the system.
>> Why can't they just email each other once we match them up?
> I think an automated nudge here could help encourage mentors to make the first contact.
Why isn't this the coordinator sending a note to the mentor saying 
"here's a protoge - send them mail - here's a suggested letter for you 
to use"?  (btw - did we end up sticking with protoge?).

I can't imagine that there aren't going to be the need for customization 
of those messages. I'm not sure having a system do
something automatically is going to help.

>
> Alissa
>
>>> I understand that some of you have thought that a simple wiki would be sufficient to perform the matching. That's fine if that's all you want, but we are happy to provide you with a bit more and will be able to do so in early June. Can you please provide feedback and/or direction on how we should proceed?
>> I think a wiki for us to coordinate, and email for everything else should be enough for now. But if others want tools, that's fine with me too.
>>
>> Lars
>> _______________________________________________
>> mentoring-coordinators mailing list
>> mentoring-coordinators@ietf.org
>> https://www.ietf.org/mailman/listinfo/mentoring-coordinators
>>
>
> _______________________________________________
> mentoring-coordinators mailing list
> mentoring-coordinators@ietf.org
> https://www.ietf.org/mailman/listinfo/mentoring-coordinators


From brian@innovationslab.net  Tue May 28 10:48:29 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9306821F9690 for <mentoring-coordinators@ietfa.amsl.com>; Tue, 28 May 2013 10:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.549
X-Spam-Level: 
X-Spam-Status: No, score=-104.549 tagged_above=-999 required=5 tests=[AWL=2.050, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3lmx2wEmUq7u for <mentoring-coordinators@ietfa.amsl.com>; Tue, 28 May 2013 10:48:24 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2EDBD21F95F9 for <mentoring-coordinators@ietf.org>; Tue, 28 May 2013 10:48:24 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0A3898811D for <mentoring-coordinators@ietf.org>; Tue, 28 May 2013 10:48:24 -0700 (PDT)
Received: from 102523127.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id CE29F14000C for <mentoring-coordinators@ietf.org>; Tue, 28 May 2013 10:48:23 -0700 (PDT)
Message-ID: <51A4EDE6.30107@innovationslab.net>
Date: Tue, 28 May 2013 13:48:22 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mentoring-coordinators@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Mentoring-coordinators] Updated FAQ
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 17:48:29 -0000

Hi all,
      I have updated the FAQ based on feedback from various IESG members 
and the discussion on the coordinators list.  Please take a look and let 
me know what I missed.

http://www.innovationslab.net/~brian/mentoring/

I did have a chat with Jari and he is more than happy to allow us to 
send letters of invitation to potential mentoring participants with his 
signature (as IETF chair).  Any volunteers to draft such a letter?

Regards,
Brian

From lars@netapp.com  Wed May 29 00:32:51 2013
Return-Path: <lars@netapp.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F21D21F8EC2 for <mentoring-coordinators@ietfa.amsl.com>; Wed, 29 May 2013 00:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.982
X-Spam-Level: 
X-Spam-Status: No, score=-10.982 tagged_above=-999 required=5 tests=[AWL=1.117, BAYES_00=-2.599, GB_ABOUTYOU=0.5, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vy8325d-37CG for <mentoring-coordinators@ietfa.amsl.com>; Wed, 29 May 2013 00:32:46 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 42BCE21F8EBC for <mentoring-coordinators@ietf.org>; Wed, 29 May 2013 00:32:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,763,1363158000"; d="scan'208";a="59066910"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 29 May 2013 00:32:45 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4T7WjkL009367; Wed, 29 May 2013 00:32:45 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Wed, 29 May 2013 00:32:45 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Brian Haberman <brian@innovationslab.net>
Thread-Topic: [Mentoring-coordinators] Updated FAQ
Thread-Index: AQHOW8uRoCiK6e61DEeS5Y+1F2sYZZkcOy4A
Date: Wed, 29 May 2013 07:32:44 +0000
Message-ID: <22CFDD78-7F0F-4003-A580-C2A4541CCFD0@netapp.com>
References: <51A4EDE6.30107@innovationslab.net>
In-Reply-To: <51A4EDE6.30107@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DF05D6911FDB1C4A820E79BDAAA155FF@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mentoring-coordinators@ietf.org>" <mentoring-coordinators@ietf.org>
Subject: Re: [Mentoring-coordinators] Updated FAQ
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mentoring-coordinators>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>,  <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 07:32:51 -0000

Hi,

On May 28, 2013, at 19:48, Brian Haberman <brian@innovationslab.net> wrote:
>  Any volunteers to draft such a letter?

sure; here is a draft based on the FAQ. Since this is in Jari's name, we wa=
nt to make sure he is OK with the content/wording.

Lars

--

Hi,

my name is Jari Arkko and I chair the Internet Engineering Task Force (IETF=
). I'm delighted to see that you will be attending the Berlin meeting! As y=
ou have only recently begun attending the IETF, I would like to invite you =
to the IETF's Mentoring Program.=20

The goal of the IETF Mentoring Program is to match IETF "newcomers" (people=
 who have participated in three or fewer face-to-face meetings or anyone re=
gistering as a student) with experienced IETF mentors. Your mentor will per=
sonally introduce you to the IETF community, help you find your way around =
the IETF and the meeting, explain things, introduce you to other attendees =
you might like to meet. Basically, your mentor will be your personal buddy =
during the meeting week, and possibly afterwards.

The IETF Mentoring Program was created to help new IETF participants to get=
 up to speed rapidly and help them begin to contribute to the IETF quickly =
and easily. I hope you will decide to participate in the program!

After you decide to participate, we will ask you a few questions about your=
 technical interests, language preferences, etc. in order to match you up w=
ith the best qualified mentor. We will then introduce you to each other by =
email, and invite you to meet up in person at the IETF Meet & Greet event o=
n Sunday afternoon in Berlin. From there on, you and your mentor decide on =
when and where to meet during the rest of the week and afterwards.

You are of course free to withdraw from the program at any time and for any=
 reason, no questions asked, should a need arise. But I sincerely believe t=
he IETF Mentoring Program will be a great way for a new participant such as=
 yourself to get introduced to the IETF by an experienced participant with =
matching interest, and I hope you will participate.=20

Regards,
Jari Arkko
IETF Chair=
