User Tools

Site Tools


faqs:feedback_questions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
faqs:feedback_questions [2011/08/23 18:42] – [I was wondering what kind of programming skills are needed to develop the Evergreen ILS. What languages do you have to know and/or what software or other applications do people use to customize this ILS?] phasefxfaqs:feedback_questions [2013/07/19 09:10] – remove references to old virtual images bshum
Line 8: Line 8:
   - Items in Evergreen are typically barcoded, though you could just enter their titles if you don't need to track them physically.   - Items in Evergreen are typically barcoded, though you could just enter their titles if you don't need to track them physically.
  
-Disclaimers aside, probably the first thing you should do is download the staff client and connect to one of the [[community_servers|demo servers]].  There is [[http://docs.evergreen-ils.org/|documentation]] and [[community_tutorials|tutorials]].  Play around and see if it might work for you.  For running your own server, perhaps the simplest step would be to install [[http://www.virtualbox.org/|Virtualbox]] and run an Evergreen [[http://evergreen-ils.org/downloads.php#evergreen_vm|virtual image]] with it.  Otherwise, check out the [[http://evergreen-ils.org/downloads.php#evergreen|download and installation instructions]].+Disclaimers aside, probably the first thing you should do is download the staff client and connect to one of the [[:community_servers|demo servers]].  There is [[http://docs.evergreen-ils.org/|documentation]] and [[:community_tutorials|tutorials]].  Play around and see if it might work for you.  For running your own server, check out the [[http://evergreen-ils.org/downloads.php#evergreen|download and installation instructions]].
  
  
Line 19: Line 19:
  
 See the page for [[dev:contributing_code|developing code]]. See the page for [[dev:contributing_code|developing code]].
 +
 +
 +==== Wow--that's a lot to know...I'm guessing that some people focus on certain aspects of development then, or do most people know how to use most if not all of the tools/languages/programs you listed? ====
 +
 +The former.  There are just a handful of [[contributing:contributors|"core" developers]] that have
 +deep and wide understanding of Evergreen, and they funnel
 +contributions from others in the development community into what
 +becomes the "official" Evergreen.  People with different skillsets are
 +found in that dev community; some are expert programmers just learning
 +Evergreen, others are novice programmers helping out with bite-sized
 +problems, and yet others help out in ways not involving "coding" at
 +all, whether with IT expertise, library domain knowledge, testing,
 +documentation, leadership or advocacy (for whatever goal).
 +
 +> Would you be able to recommend a path to start learning more?
 +
 +A disclaimer: you don't have to be a programmer or have programming
 +staff to use Evergreen, and there are other avenues for getting
 +customization done (such as hiring folks, or an [[faqs:evergreen_companies|Evergreen company]],
 +within the community to do work for you, or [[:contributing|contributing]] in other ways
 +such that folks want to help you in kind--even simply opening bug
 +reports can instigate change).  In general, we like to encourage adoption of useful features into stock Evergreen as opposed to encouraging local customizations that never leave their original libraries (and for changes that don't or won't make it into Evergreen proper, it's still useful to sharethem with others).
 +
 +That said, probably the best thing to do is to start by installing
 +Evergreen (a useful learning experience in and of itself). That can be
 +found here: http://evergreen-ils.org/downloads.php
 +
 +Play with the software in the roles of admin, staff, and patrons, and
 +find something that gives you an itch to fix or improve.  Create a
 +Launchpad ticket describing the problem and mention that you plan on
 +working on it (assign it to yourself).  Then ask folks on the
 +OPEN-ILS-DEV mailing list, or on the #evergreen IRC channel, how you
 +might do that.  Folks may point you to the exact file that you'd want
 +to tinker with, and give you pointers on how to test changes.  You
 +don't have to be a master of Perl or Javascript before you dip your
 +toes in the water, but some familiarity with programming in general
 +won't hurt.
 +
 +If you need to remain anonymous (maybe for fear of retaliation from
 +your current library vendor), there are ways to do that and still
 +participate in the community.  You can ask at
 +feedback@evergreen-ils.org for advice in that regard.  In general
 +though, it'd be nice if you just said Hi and introduced yourself on
 +the dev mailing list and/or in IRC.
 +
 +Launchpad is our public bug tracker; you'll want to create an account for it:
 +http://launchpad.net/evergreen
 +
 +Our mailing lists can be found here:
 +http://evergreen-ils.org/listserv.php
 +
 +Information on the IRC chat here:
 +http://evergreen-ils.org/irc.php
 +
faqs/feedback_questions.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.