Hi all,
I just wanted to let everyone know that I added three potential coding
projects to the OPW wiki page
http://wiki.evergreen-ils.org/doku.php?id=opw. The first two came from
discussions with a few other people: 1) Improvements to the self-check
interface, including moving the interface to AngularJS and 2) a
continuation of our responsive design work. The third, Awesome Box
integration, was something I added today as I was remembering the great
keynote we had at the last Evergreen conference.
I think these projects should be doable for a developer new to Evergreen
to accomplish in the time allotted (December 9 to March 9). However, I'm
not a developer, so if anyone with more expertise thinks these are
unreasonable, please let me know.
There are two people who have volunteered to be mentors for the
responsive design project, but we would need mentors for the other
projects to include them on the final list. My preference is to have two
co-mentors for a project to help minimize the per-mentor time
commitment. If you are interested in mentoring either of these projects,
feel free to add your name to the wiki. We need to let the OPW folks
know our final decision by the end of the week, so I'm hoping volunteers
can put their names forward by Friday morning.
If there are other coding projects that you think might be good for this
program, feel free to add them to the wiki. As far as criteria for what
might make a good project, OPW made the following recommendations in the
'Defining a Project" section of the mentors page:
The project should consist of manageable and relevant tasks that can
be incorporated into the project throughout the internship period.
Stand-alone projects proposed by an applicant are not suitable at all
for people who are not established contributors. Please try to avoid
situations when participants work on features that are not yet
designed or agreed-upon, have too many moving parts, and would only
land in the main code-base after the internship is over as a best-case
scenario. This rarely works out. Instead, look for agreed-upon
manageable bugs and small features that have a shared theme and would
allow the participant to feel the satisfaction of landing her changes
throughout the internship.
Feel free to let me know if you have any questions!
Kathy
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier
#evergreen IRC: kmlussier
On 8/25/2014 12:49 AM, Kathy Lussier wrote:
Hi all,
Please excuse the cross-postings.
At its meeting last week, the Executive Oversight Board discussed the
possibility of participating in the GNOME Outreach Project for Women -
http://gnome.org/opw/. The goal of OPW is to increase the
participation of women in FOSS projects by connecting interns with
communities that need help for specific projects.
It is similar to the Google Summer of Code program in which Evergreen
has previously participated, but the internships provided through this
program can extend beyond coding. Interns could also work on user
experience design, graphic design, documentation, web development,
marketing, translation, or any other task that would help sustain the
project. The EOB agreed to put forth the funds to cover the intern's
stipend if, as a community, we could come up with some strong project
ideas that will help the community and mentors willing to commit their
time to the project
I have started a page at http://wiki.evergreen-ils.org/doku.php?id=opw
where we can start collecting potential project ideas. I had a couple
of doc ideas that I have already added to the list. If you can think
of anything that you think would be a worthwhile project, feel free to
add it to the page.
Please remember, though, that the projects need to be something that
serve as an entry point for somebody who is entirely new to Evergreen.
In talking about how to define a project, OPW suggests starting with
smaller tasks (i.e. bugs) with a shared them and progressing over time
to more complex tasks (i.e. features). They also ask that we select
projects where the intern is likely to see their contributions
incorporated in the project before the internship is over.
Also, we need to make sure we have committed mentors on any project
that is ultimately posted. The next OPW round starts September 8 when
the names of participating organizations are released. The application
deadline is October 22. During that application period, mentors may
need to commit as much as 10 hours per week on the program since
you'll be working with multiple potential applicants. I expect that it
wouldn't be 10 hours per week for the entire application period, but
that it will become more demanding as the application deadline
approaches.
The internship dates then run from December 9 to March 9, during which
time you may need to spend up to five hours per week working with the
intern. Due to the time commitment, I think we should shoot for two
mentors on each project so that the commitment does not fall on just
one person.
There is more information for potential mentors at
https://wiki.gnome.org/OutreachProgramForWomen/Admin/InfoForMentors.
We need to let OPW know by September 8 if we plan on participating, so
we have about two weeks to see if we can pull together some strong
projects. However, I think this is doable if we have some willing
volunteers and good project ideas.
Feel free to let me know if you have any questions!
Kathy
