Evergreen has applied for, but has not been accepted yet as a Google Summer of Code 2015 Mentoring organizations. Updates will be posted here as they develop.
If you've found this page, you might be interested in making a valuable contribution of your development time to the Evergreen project. The primary goal for our mentors this summer is to enable students to successfully contribute working code to our project and gain experience with the tools and social norms of open source development. We'll expect you to use the same communication channels, code repositories, and bug tracking systems as the rest of the developers, while we help you commit code early and often in your efforts - and we, in turn, will learn from your insight as a newcomer to our community. We want the experience to be positive for each student, each mentor, and for the project as a whole.
In solidarity with the Software Freedom Conservancy's participation in the GNOME Foundation's Outreach Program for Women, we particularly invite and encourage eligible women to apply.
The Evergreen Project develops an open source ILS (integrated library system) used by more than 1000 libraries around the world. The software, also called Evergreen, is used by libraries to provide their public catalog interface as well as to manage back-of-house operations such as circulation (checkouts and checkins), acquisition of library materials, and sharing resources among groups of libraries.
To become more familiar with the project:
We expect students to communicate their progress publicly with the project, either via blog posts or posts to the mailing list, on a regular basis: weekly, at a minimum. We also expect the intern to meet weekly with the project mentors in the #evergreen IRC channel. Much more communication should also occur between the student and the development team on a daily basis through the normal modes of IRC, bug tracker, and mailing list.
As part of their application for the Google Summer of Code, we expect any student applicants to submit an SSH key to the git administrators and gain working access to the Evergreen git repository. One can follow instructions on the dev:git page, which contains other useful information on use of git for the project. Additionally, students are required 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. We also ask that all applicants introduce themselves to the developer community through a post to the technical discussion mailing list.
To increase your chances of being selected and having a successful summer of code, please read the GSoC Student Guide, including the section on Writing a Proposal. A good application will have the following properties:
We strongly encourage all applicants to publicly discuss their proposals on the development mailing list for Evergreen.
Here are examples of what we would consider to be a good application:
REMEMBER: Applicants must submit a patch or pull request that makes a small improvement to Evergreen
The following project ideas are the result of brainstorming within the Evergreen development community. They are not the only project ideas that would be valuable to the Evergreen project - hopefully they serve as a starting point for your own initiative.
While documents have their place, there's generally no substitute for talking to existing community members - whether you're working through a tough piece of code, or putting together a patch, or just getting your development environment up and running - and you'll find that our development community tries to support newcomers like you. If you have questions, the #evergreen IRC channel on Freenode is the best place to start. You can also use the Evergreen development mailing list (open-ils-dev) if you prefer.
If you have questions about the following project ideas or want to kick around some new ideas that you have, you can contact the project mentors as follows:
kmlussier, email: firstname.lastname@example.org
bshum, email: email@example.com
bshum, email: firstname.lastname@example.org
dbs, email: email@example.com
Dyrcona, email: firstname.lastname@example.org