[Eg-oversight-board] Fwd: Evergreen participating in Outreachy again?

Tue Feb 16 11:48:30 EST 2016

Ruth (and everyone),
I think it's worth having a discussion about at the conference but I don't
necessarily think the EOB meeting is a good place for it.  Happy to hear
contradicting opinions though!

Maybe it would be beneficial to get some input from the people we keep
failing - people who are new or unfamiliar with the project/code/product.
Do you think we could solicit some feedback at the conference by getting
some people to hand out a quick anonymous survey at their presentations?
Or making one available online and pushing it at the beginning or end of a
talk?

Things I think we could learn from a survey of first-timers/newbies:
-- How easy is it to find information you want about Evergreen?
-- What did you wish someone had explained to you about Evergreen?
-- How confident do you feel asking questions of the community?  Do you
think the community is accepting/encouraging?
-- When you ask for help, how helpful is the assistance you receive from
the community?  How could it be improved?
-- Would you say you get too many opinions or not enough?
etc. etc.

So, maybe we start by asking people how the community can do better with
supporting/explaining our product/process/needs... and that will lead us to
some concrete improvements we can make to structure things better for a
future mentoring program?

Just an idea...
Grace

On Tue, Feb 16, 2016 at 11:26 AM, Kathy Lussier <klussier at masslnc.org>
wrote:

> Hi all,
>
> I'm going to chime in as the coordinator from our previous participation
> in the Outreachy program. I concur with everything Grace said in her email.
>
> I love the idea of inviting students into our community to work on a
> project, but I do think we need to work together ahead of time to establish
> clear guidelines of the time that is expected from the mentor, what type of
> guidance the mentor is expected to give a student, and how the student
> should be interacting with the community.  I don't think this is something
> we can quickly throw together, but is something that will take time to
> develop.
>
> Going beyond the mentorship requirements, in terms of selecting projects
> for interns to work on, I'll say one problem we've consistently come across
> with coding projects is that there is a high bar for entry for contributing
> code to the Evergreen project. We heard from interns who had trouble
> getting an Evergreen installation up and running. When we last participated
> in Outreachy, we didn't have any candidates who successfully completed the
> requirement to fix a bitesize bug before submitting an application, even
> though I know at least one candidate had an Evergreen install going early
> in the application period. Maybe Grace is correct when she says it will
> become easier once the web client is finished, but, even so, we do need to
> work in the meantime on learning how to mentor.
>
> Kathy
>
>
> On 02/16/2016 11:01 AM, Grace Dunbar wrote:
>
> Having participated as a mentor in the first round, I'd say that our
> participation suffered from the same issue we've always had in these
> situations (GSOC, etc.) - mainly, lack of time on behalf of the mentors.  I
> would not qualify our mentorship of our Outreach participant as a success
> because I don't feel like we met the stated goals of the program which were
> to guide the participant through a small project wherein at the conclusion
> they could see their code accepted and implemented in the project before
> the end of the term.  Until we address our own issues with mentoring,
> transparency, and the ability to successfully create small projects that
> are achievable for the participants I don't think we should be
> participating.
> That said... I think that there will be many, many more opportunities for
> participation in these programs once the web client is finished as the
> platform will be much friendlier for a wider range of participants.
> So, while I'm a big fan of the idea, I'm not a believer in our ability to
> successfully mentor participants.  And I think it's unfair of us use these
> participants as our learning curve.
>
> Grace
>
> On Tue, Feb 16, 2016 at 10:48 AM, Ruth Frasur <rfrasur at gmail.com> wrote:
>
>> While I know that this happened, I wasn't part of any of the logistical
>> stuff.  On the one hand, I'm for anything that empowers women, encourages
>> any participation in open source communities, and promotes Evergreen ILS
>> beyond its community and users.  On the other hand, I don't really know
>> enough about what this would entail to make an informed recommendation.
>>
>> On Tue, Feb 16, 2016 at 8:11 AM, Chris Sharp <
>> <csharp at georgialibraries.org>csharp at georgialibraries.org> wrote:
>>
>>> For your consideration.  "Outreachy" was formerly known as the "Outreach
>>> Project for Women", which Evergreen participated in a couple of years ago.
>>> See details below.
>>>
>>> ----- Forwarded Message -----
>>> > From: "Karen Sandler" < <karen at sfconservancy.org>
>>> karen at sfconservancy.org>
>>> > To: csharp at georgialibraries.org, "Kathy Lussier" <klussier at masslnc.org
>>> >
>>> > Sent: Tuesday, February 16, 2016 12:14:28 AM
>>> > Subject: Evergreen participating in Outreachy again?
>>> >
>>> > Hi Kathy and Chris,
>>> >
>>> > The Outreachy program is looking for organizations to participate in
>>> > round 12.  Do you think Evergreen would want to participate again?
>>> > The round will open this week.
>>> >
>>> > Please let us know if Evergreen can participate again!
>>> >
>>> > karen
>>> >
>>> > On Mon, Jan 25, 2016 at 7:51 AM, Sarah A Sharp <sarah at thesharps.us>
>>> > wrote:
>>> >
>>> >
>>> > Dear coordinators and mentors,
>>> >
>>> > Thank you for being a part of our outreach program! The next round for
>>> > Outreachy is scheduled to open on February 16, with an application
>>> > deadline of March 22. Internships will run from May 23 to August 23.
>>> >
>>> > If your organization is interested in participating in the next round,
>>> > please update your landing page, and let us know by February 16 if you
>>> > will participate. Organization coordinators and mentors, please
>>> > coordinate on the following:
>>> >
>>> > * Review set up information at
>>> > https://wiki.gnome.org/Outreachy/Admin/GettingStarted
>>> > * Secure funding for your org to sponsor at least one intern ($6,500)
>>> > * Update your org's landing page
>>> > * List your project ideas and recruit other mentors
>>> > * Let us know at outreachy-admins at gnome.org that your org is
>>> > participating
>>> > * Start spreading the word about your org's internships - no need to
>>> > wait for February 16
>>> >
>>> > We plan on having a twitter chat about Outreachy on Feb 16, to
>>> > spotlight the organizations that are participating, and allow orgs to
>>> > answer any questions people have. Participation in the chat is
>>> > optional, but if you do want to participate, being able to link to a
>>> > blog post that describes why you're passionate about your project
>>> > would help us promote your project.
>>> >
>>> > The updated resources for the upcoming round are:
>>> >
>>> > * https://wiki.gnome.org/Outreachy/2016/MayAugust
>>> >
>>> > A page with a timeline and participating organizations listing; if
>>> > you have funds secured you can add your organization there.
>>> >
>>> > * https://wiki.gnome.org/Outreachy/Admin/InfoForOrgs and
>>> > https://wiki.gnome.org/Outreachy/Admin/InfoForOrgs/Proposal
>>> >
>>> > These pages have motivation and information for sponsorship; you
>>> > can use and customize the text from the Proposal page to approach
>>> > companies about sponsorship (please do a quick check with Karen,
>>> > Sarah, and myself at <outreachy-admins at gnome.org>
>>> outreachy-admins at gnome.org alias first to make
>>> > sure we coordinate any efforts to approach the same company)
>>> >
>>> > * https://wiki.gnome.org/Outreachy/Admin/GettingStarted
>>> >
>>> > Please review this page when you are updating the landing page for
>>> > your organization and if your organization plans to participate in
>>> > Google Summer of Code
>>> >
>>> > * https://wiki.gnome.org/Outreachy#Contracts
>>> >
>>> > Please make all people who volunteer as mentors in your
>>> > organization aware that they will need to sign a contract similar
>>> > to this to be a mentor in the program. Interns cannot be paid until
>>> > their mentors sign the contract, so it is important that mentors
>>> > sign the contract as soon as the application system opens on Feb
>>> > 16.
>>> >
>>> > * https://wiki.gnome.org/Outreachy#Eligibility
>>> >
>>> > As we announced last round, we have expanded the Outreachy program
>>> > to include underrepresented people of color underrepresented in
>>> > tech in the U.S.  Outreachy continues to be open internationally to
>>> > women (cis and trans), trans men, and genderqueer people.
>>> >
>>> > Google Summer of Code (GSoC)
>>> > https://developers.google.com/open-source/gsoc
>>> >
>>> > The applications for organizations to participate in GSoC will open
>>> > February 8 and will close at 7pm UTC on Friday, February 19. I highly
>>> > encourage organizations to apply for this program as it's a great
>>> > opportunity to engage students with your project and is generously
>>> > sponsored by Google.  Please note that GSoC deadlines are set in stone
>>> > and be sure to work with participants and mentors to get things done
>>> > by these deadlines as your organization participates in GSoC.
>>> >
>>> > Outreachy was created in response to low participation of women in
>>> > GSoC, and we encourage women who are students and coders to apply for
>>> > both programs if the organization they are interested in is
>>> > participating in both. The dates for this round of Outreachy are
>>> > intentionally set to be similar to GSoC dates. Outreachy application
>>> > deadline is a couple days earlier to make sure that applicants
>>> > eligible for GSoC don't miss the GSoC deadline.
>>> >
>>> > Please contact Karen, Marina, and myself at
>>> <outreachy-admins at gnome.org>outreachy-admins at gnome.org
>>> > alias if you have any questions. We hope you can join in for this
>>> > round!
>>> >
>>> > Thanks,
>>> > Sarah Sharp
>>> >
>>> >
>>>
>>> --
>>> Chris Sharp
>>> PINES System Administrator
>>> Georgia Public Library Service
>>> 1800 Century Place, Suite 150
>>> Atlanta, Georgia 30345
>>> (404) 235-7147 <%28404%29%20235-7147>
>>> csharp at georgialibraries.org
>>> http://pines.georgialibraries.org/
>>> _______________________________________________
>>> eg-oversight-board mailing list
>>> eg-oversight-board at list.evergreen-ils.org
>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>>>
>>
>>
>> _______________________________________________
>> eg-oversight-board mailing list
>> eg-oversight-board at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>>
>>
>
>
> --
> Grace Dunbar, Vice President
> Equinox Software, Inc.  -  The Open Source Experts
> gdunbar at esilibrary.com
> 1-877-OPEN-ILS    www.esilibrary.com
>
>
> _______________________________________________
> eg-oversight-board mailing listeg-oversight-board at list.evergreen-ils.orghttp://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative(508) 343-0128klussier at masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>
> _______________________________________________
> eg-oversight-board mailing list
> eg-oversight-board at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>
>

-- 
Grace Dunbar, Vice President
Equinox Software, Inc.  -  The Open Source Experts
gdunbar at esilibrary.com
1-877-OPEN-ILS    www.esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/eg-oversight-board/attachments/20160216/177d29fb/attachment-0001.html>