That's definitely a good idea - I have just subscribed to the dev list
and shall surely have a look at the chat :-)...
Linda
On 17.3.2016 15:20, Yamil Suarez wrote:
Linda,
Another suggestion is to look at logs of previous developer meetings
that happen on IRC [1]. So you can see part of how new features end up
being accepted into EG. For example, you will see how the "wishlist"
Launchpad bug will be shared, and folks will give constructive
criticism on IRC or in the comments of the Launchpad bug. Eventually
as the code gets improved with the developer feedback it will be
(hopefully) accepted by the core committers into EG. Of course some of
this communication also happens in the developer mailing list, so I
recommend you subscribe to it too.
Good luck,
Yamil
[1]
http://wiki.evergreen-ils.org/doku.php?id=dev:meetings&s[]=developer&s[]=meetings
--------------------------------
Yamil Suarez, MCS
Library Systems Administrator/Developer
Stan Getz Library
Berklee College of Music
1140 Boylston St
Boston, MA 02215
ysua...@berklee.edu
617-747-2617
On Thu, Mar 17, 2016 at 10:13 AM, Linda Jansova <skolk...@chello.cz> wrote:
Thank you, Yamil! We will surely come up with some questions in the process
:-)...
Linda
On 17.3.2016 15:07, Yamil Suarez wrote:
Hello,
First of all, Galen that was a great summary. Linda, feel free to ask
more question about the process of contributing code on this list
(general list) or on the developer list. Also you can chat with
members of the community, including developers, on the Evergreen IRC
channel.
Good luck,
Yamil
--------------------------------
Yamil Suarez, MCS
Library Systems Administrator/Developer
Stan Getz Library
Berklee College of Music
1140 Boylston St
Boston, MA 02215
ysua...@berklee.edu
617-747-2617
On Thu, Mar 17, 2016 at 10:01 AM, Galen Charlton <g...@esilibrary.com>
wrote:
Hi,
On Thu, Mar 17, 2016 at 3:41 AM, Linda Jansova <skolk...@chello.cz>
wrote:
We have been awarded a grant to create a module which would add book
covers
from Czech provider http://obalkyknih.cz/ to Evergreen.
Congratulations!
However, as we have not submitted code yet, we are a bit unsure about
which
steps should we take to have it included in the master. Could you please
let
us know how it works or how we should proceed once our module is ready?
A guide to contributing to the Evergreen project can be found here:
http://wiki.evergreen-ils.org/doku.php?id=contributing
That's a lot to digest, of course; some initial steps I recommend you
take to get started are:
[1] File a bug on Launchpad (https://bugs.launchpad.net/evergreen)
with details about the proposed book cover integration. Set the bug's
importance to "Wishlist", as it will be a new feature.
[2] Read the instructions at
http://wiki.evergreen-ils.org/doku.php?id=dev:git and have whoever
will be writing the code submit their SSH public keys so that they can
push code to the Evergreen working Git repository.
[3] Have a look at the existing added content modules
(Open-ILS/src/perlmods/lib/OpenILS/WWW/AddedContent.pm and
Open-ILS/src/perlmods/lib/OpenILS/WWW/AddedContent/* in the source).
Regards,
Galen
--
Galen Charlton
Infrastructure and Added Services Manager
Equinox Software, Inc. / Open Your Library
email: g...@esilibrary.com
direct: +1 770-709-5581
cell: +1 404-984-4366
skype: gmcharlt
web: http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org
