LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  March 2012

CODE4LIB March 2012

Subject:

Job: Google Summer of Code intern at Evergreen

From:

[log in to unmask]

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 29 Mar 2012 20:38:28 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

The Evergreen Project has been accepted by the Google
Summer of Code 2012 program. This is the second year we've
been accepted, and we look forward to working with GSoC students to build some
cool new stuff into Evergreen.

  
If you're a student looking for a GSoC project to apply to, why choose
Evergreen? There are many reasons, both technical and
community. Evergreen qua software is a resource discovery
and sharing system for libraries. It can be used to run a
library's catalog, including checking out and checking in books and other
materials, managing library patrons' requests for materials, and helping the
library acquire new stuff. But it's not just a specialized
inventory tool; Evergreen is designed to handle very large groups of libraries
that share both their materials and metadata about those items, while at the
same time giving library patrons a way to find the books they want, even if
sometimes a patron may not have a clear idea of what they want until they find
it in the catalog.

  
Evergreen is a large, multi-layer application. Are you a
budding PostgresSQL DBA and developer? There are lots of
things you could do to enhance Evergreen. Is your personal
motto TMTOWTDI? Ditto. Are you a
JavaScript guru? Ditto. Are you a C
programmer who likes making fast network protocols even faster but couldn't
care less about the middle layer? Ditto.
Are you focused on making interfaces more usable? Do you like to break things, then figure out how to
fix them? Ditto.

  
But Evergreen is about more than just the code. Our
community is very active, and it's not just made up of developers -- both
librarians who run Evergreen systems and patrons who use them are also to be
found on the IRC channel (#evergreen on FreeNode) and mailing
lists. Some of the librarians are also coders, and some of
the coders are also librarians. If you ask a question about
some odd thing that Evergreen does, you'll find out not just how, but why.

  
So let's say you're ready to apply to be a GSoC student for the Evergreen
project. You've first got a bit of reading ahead of you:

  
Register an account at the GSoC 2012 home page, then read carefully,
particularly the timeline and FAQ.

All done? Great. Please read the FAQ
again. If you have questions about the mechanics of
applying, please feel free to email the GSoC org admins for the Evergreen
project (Galen Charlton and Dan Scott) at , but please respect our time by
checking the FAQ first.

Next, check out our ideas page, which has suggestions for some projects as
well as our expectations of students during the application and coding
processes.

Next, please read our (very brief) getting started with Evergreen development,
our (longer) procedures for contributing, and our page about how we use Git.

"That's a lot of reading!", you might say… and you'd be
right. On the other hand, Evergreen is used by libraries,
after all.

  
Ready to move on to the next step? Get to know us a bit:
join the general and development mailing lists and the IRC channel, hang out,
listen, and ask good questions. While you're doing that,
also keep in mind one of our application requirements:

  
As part of their application for the Google Summer of Code, we expect any
student applicants to submit a patch or point to a branch that addresses some
problem or adds some small enhancement. Bite-size bugs and new unit tests are
good candidates to tackle. To help you get started, the community has put
together a quick-start introduction and virtual image.

  
Please take that requirement seriously -- Evergreen is not a trivial project;
if you start trying to put a patch together an hour before the application
deadline… you're almost certainly too late to submit a good application.

  
So after you've read a bit, talked with us a bit, and patched Evergreen a bit…
go ahead and fill out the GSoC application form and hit submit.

  
We look forward to working with you!



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/873/

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager