Barriers to Evergreen adoption

Hardware:
- two servers recommended
- offline mode for staff, but not for catalogue
Software skills:
- Linux system administration
- PostgreSQL
- Apache
- ejabberd
Installation & configuration is not "turn key"
Community currently concentrated in North America
IRC support may be limited in your timezone
Internationalization is hit or miss
Javascript-heavy catalogue*

Evergreen growth: community

Increased use of community bug database
- For merge requests as well as bugs
- Any non-trivial code changes are supposed to go through a merge request / review process
Weekly developer meetings via IRC
- One meeting to discuss issues and processes
- One meeting to review merge requests
Automated testing for build / compile / unit testing errors after every commit
- More unit tests needed!

Evergreen IRC

Joined the Software Freedom Conservancy (SFC) American non-profit organization
- SFC, as a legal entity, can hold project assets such as trademarks, copyright, domain names, and funds
- Transparent, neutral third party
Evergreen Oversight Board represents the project
- Board membership was "bootstrapped" in 2011 but will hold elections in 2012

2.1.0 release should be available any day now
Improved since 2.0:
- Serials with predictions and check-in
- Acquisitions with EDI support
New since 2.0:
- Bibliographic parts
- Conjoined items
- Authority control sets
- SRU/Z39.50 server access to authority records
- Hold-driven recalls
- Automated staff client updates
- … and much more
Serials and acquisitions were introduced in 2.0; as sites went through the process of using these features, they found a number of issues that have been resolved in 2.1

2.2 beta targeted for late November 2011
TPAC: low-bandwidth, full-featured catalogue
- Easy customization
- On-the-fly lists
OpenLibrary integration for cover art, added content, e-books (includes lending)
Revamped configuration interface, courtesy of Google Summer of Code student Joseph Lewis:
- Categorized configuration settings
- Settings history; import; export
- Searchable interface
Staff client: saved searches

Have a test server - and use it
- Learn how to administer the Evergreen stack - safely
- Test your migration strategy
- Test and document new features on new releases before learning "the hard way"
- Train staff on new features on new releases
Speak up!
- Share your troubles and triumphs on the mailing lists, IRC, and bug reporting database
Stay current!
- Point releases contain bug fixes that can save time
- Major releases can change how internal processes work significantly, making it hard for the community to help users on previous releases