At the conference, one highly attended break-out session was dedicated to a
"Code4Lib Mentorship Program". Each attendee there voiced a desire to
improve the process of finding and/or sharing expertise within the C4L
community. Some people wanted to form groups to learn new technology
together (ex. that recent Py/PyMARC thread); others needed help right away
with some new task that just landed on their desk.
This community is full of knowledge, so let's share it. On behalf of the
attendees of this breakout, I'm officially reigniting the Code4Lib
Mentorship Program today.
- - - -
As a first step, as we work to build up the program, please indicate your
desire to participate following the links below.
== Call for Mentors ==
If you are willing to be a mentor, please follow the examples and add your
name, contact information and areas of specialization to the wiki here:
At a minimum, mentors should be willing to coordinate an hour-long online
hangout monthly. You could do much more than that, but you shouldn't do
less. Basically, it's a commitment to check in and offer your expertise
once a month.
== Call for Partners ==
If you want to find a mentor or learn something new, please add your name,
contact information and area of interest to the wiki here:
I want to especially welcome people who feel uncomfortable with their level
of technical foo/bar/baz to participate. Everyone of all levels is invited
and encouraged to join up.
- - - -
Lastly, if you have time to assist in building the C4L mentorship program
into all that it should be, please send me your name and contact
I will arrange a conference all or Google hangout in March for all the
people interested in building the mentorship program itself.
Web Architect and User Experience Analyst
University of Minnesota Libraries