The Evergreen development team has put together another 2.0 alpha release in the relentless march towards stability. The release, cleverly named alpha 4, incorporates a much smaller number of bug fixes and performance improvements than alpha 3, suggesting that we are indeed getting close to the level of stability needed for a good beta release. Please download the beta (source tarball or virtual image), join the testing effort, and report your findings to the Evergreen development mailing list; the earlier we find bugs, the better the 2.0 release will be!
Draft rules of governance for Evergreen Software Foundation – for discussion
After a great deal of effort through the summer, the Governance Committee struck at the 2010 Evergreen Conference is pleased to provide for your review and feedback the proposed rules of governance for the Evergreen Software Foundation. These rules can be found at the top of the “governance structure” space of the Evergreen wiki in wiki format, OpenDocument format, and Word format.
The proposed rules of governance describe the purpose of the Evergreen Software Foundation as having the mission to:
(i) promote, support, and advance the Evergreen software;
(ii) support and facilitate the growth of the international community of Evergreen users;
(ii) foster and protect the Evergreen assets;
(iii) serve as a resource and communication device for Evergreen users; and
(iv) serve as a funding and grant seeking source for cooperative
development projects.
Hopefully these goals are self-explanatory, but some explanation of (ii) (the second ii – heh – some editing still required): the “Evergreen assets” are the trademarks, logos, domain names, and some hardware currently held by GPLS PINES and Equinox, as well as copyright over portions of the code, should institutions or individuals for some reason opt to contribute their copyright to the foundation. The assets would also include funds that result from donations to the project, revenues from conferences, etc.
The Governance Committee has chosen to submit a membership application to the Software Freedom Conservancy (http://sfconservancy.org) as the most expedient route to functioning within a 501(c)(3) non-profit structure that offers tax benefits for donations made by residents of the United States. The membership application is also visible at the top of the “governance structure” space of the Evergreen wiki.
These are significant steps for the Evergreen community, and your feedback on the proposed rules of governance for the foundation is genuinely desired. For the foundation to be successful, we need to be sure that we have the confidence and trust of the community to move forward with the proposal. If, after reading the documents, there are aspects of the plans or documents that you find confusing, or that you find worrisome, please raise your concern on the Evergreen General mailing list – you probably won’t be alone! If you have suggestions for amendments, please post those suggestions to this mailing list as well.
Evergreen 2.0, alpha 3 release ready and waiting
Yesterday we (the Evergreen development team) finished wrapping up the Evergreen 2.0 alpha 3 release and made it available for your consumption, inspection, testing, development – what have you.
The released ??files, including the source tarball, staff clients for Windows and Linux, and a virtual image built on Debian Squeeze, are available from the Evergreen downloads page, along with installation instructions.
This alpha release reflects a ton of bug fixes, usability enhancements, and performance imporovements since the alpha 2 release, undoubtedly aided by the concentration of a significant portion of the development teams’ focus on a migration of a large production environment to this code base.
Thanks for contributions to this release are owed to many in the community, but let’s call out special praise for Thomas Berezansky from MVLC for providing us with the Linux staff client packaging target, and to Chris Sharp of Georgia PINES, Anoop Atre of Minnesota PALS, and Benjamin Shum of Bibliomation Inc. for going through the install process in prior alpha releases and providing us with the feedback we needed to correct problems in install process and accompanying documentation.