governance:software_freedom_conservancy_membership_application
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
governance:software_freedom_conservancy_membership_application [2010/09/06 11:44] – Provide wiki links instead of http links to the committers/patchers/DIG links dbs | governance:software_freedom_conservancy_membership_application [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Software Freedom Conservancy membership application ====== | ====== Software Freedom Conservancy membership application ====== | ||
+ | Hello: | ||
+ | My name is Dan Scott, and I am one of the core developers and long-time contributors to the Evergreen open source library system. On behalf of the Evergreen community, I would like to submit the following application for membership in the Software Freedom Conservancy. | ||
- | To apply to the Conservancy, | + | * Detailed description of the project. |
- | following (links to online documents where the information is already | + | |
- | published is fine): | + | |
- | * Detailed description of the project. | + | To quote from the project |
- | * (dbs) http:// | + | |
- | * FLOSS License(s) used by the project | + | |
- | * (dbs) Any original work produced by the project | + | |
- | * Roadmap | + | |
- | * (dbs) http:// | + | |
- | * link to the website. | + | |
- | * (dbs) http:// | + | |
- | * Link to the code repository. | + | |
- | * Evergreen code: http:// | + | |
- | * (dbs) Do we consider OpenSRF a separate project, or should we also link to http:// | + | |
- | * Have you ever had funds held by the project, or by any individual on behalf of the projects? | + | |
- | * Brief history of the project, including past governance decisions. | + | |
- | * (dbs) Question 8 on http:// | + | |
- | * Existing for-profit | + | |
- | * (aft) Partnering with the Galecia Group (Petaluma, CA) and the King County Library System (Issaquah, WA) in developing resources for the Evergreen community. | + | |
- | * Names, email addresses, and affiliations of key developers, past and present. | + | |
- | * [[committers|Committers]] was a start - we could add email addresses and affiliations. We should also add Karen Schneider. | + | |
- | * (gmc) [[patchers|Patchers]] has a few more people who would count as significant developers but who are not committers | + | |
- | * (dbs) I've brought these two documents together in a single document under the "contributing" | + | |
- | * Information about any past for-profit or non-profit organizational affiliations the project has had. | + | |
- | Please note that this information will be shared with Conservancy' | + | The project began in 2004 when the Georgia Public Library Service found all of the existing library systems, open source and proprietary, |
- | of Directors, its Evaluation Committee (which is currently just a subset | + | |
- | of the Directors, but that may change | + | |
- | Conservancy' | + | |
- | input as possible from Conservancy' | + | |
- | new projects | + | |
- | Also, please be advised that we currently have a backlog | + | In 2006, the first version |
- | and it is currently taking about 3-6 months for projects to be considered | + | |
- | by our evaluation committee. | + | |
- | with a list of questions, and then if you answer quickly, it is one month | + | * the original developers of Evergreen formed a for-profit company |
- | later that the project | + | |
- | more projects, but we do so carefully to be sure that the influx | + | * the Georgia Public Library Service won the Mellon Award for Technology Collaboration (MATC) for its work on the Evergreen ILS (http:// |
- | projects doesn' | + | |
- | There has been overwhelming interest in the Conservancy, and we are | + | Since then, the community |
- | evaluating projects on a first-come, first-evaluated basis. | + | |
- | prioritizing our work to make sure the needs of already accepted projects | + | |
- | are met before we proceed on the evaluation | + | |
- | projects. | + | |
- | projects already in the Conservancy get what they need, and should your | + | |
- | project ultimately join the Conservancy, | + | |
- | beneficiary | + | |
- | very scarce resources with a growing demand from the community that we | + | |
- | serve. | + | |
- | Conservancy. | + | |
- | Feel free to submit | + | * FLOSS License(s) used by the project |
- | like us to review in considering an application, | + | |
- | the queue. | + | |
- | Finally, we ask that applying projects consider donating a percentage of | + | Any new code that the project creates is licensed under the GNU General Public License, version 2, with the "or later" clause. |
- | their funding to the general operating costs of the Conservancy. | + | |
- | a way to assure we can continue providing a high level of service to all | + | |
- | Conservancy projects. | + | |
+ | In some cases we have bundled code that is provided under a more permissive license, such as the New BSD License. If we modify any 3rd party code, such as the DP_DateExtensions.js, | ||
+ | |||
+ | * Roadmap for future development. | ||
+ | |||
+ | Our roadmap is currently very much focused on the next release, 2.0, with a beta due at the end of September 2010: http:// | ||
+ | |||
+ | The roadmap is a living document, and after our IRC community meeting on September 7th, I expect that there will be further development plans fleshed out for the subsequent release(s). | ||
+ | |||
+ | * Link to the website. | ||
+ | |||
+ | Both http:// | ||
+ | |||
+ | * Link to the code repository. | ||
+ | |||
+ | The Evergreen source code is available from svn:// | ||
+ | |||
+ | The OpenSRF source code (OpenSRF provides the communication infrastructure on which Evergreen is built) is available from svn:// | ||
+ | |||
+ | A Trac instance links to both repositories from http:// | ||
+ | |||
+ | * Have you ever had funds held by the project, or by any individual on behalf of the projects? | ||
+ | |||
+ | As was noted above, the Georgia Public Library Service (GPLS) was awarded the Mellon Award for Technology Collaboration (MATC), worth $50,000. GPLS invested the funds in hiring technical writers to create documentation for the project. | ||
+ | |||
+ | There have been two Evergreen conferences, | ||
+ | |||
+ | * Brief history of the project, including past governance decisions. | ||
+ | |||
+ | The Evergreen project was created by the Georgia Public Library Service (GPLS) in 2004 and employed all of the initial developers and systems personnel. GPLS currently holds legal collateral such as the Evergreen trademark and logo and still holds a significant proportion of the copyright over the Evergreen code base. Shortly after the Evergreen International Conference in 2009, Elizabeth McKinney of GPLS announced their intention to form a non-profit legal entity to hold these assets on behalf of the broader Evergreen community ( http:// | ||
+ | |||
+ | In practice, since the project began focusing on being applicable to libraries outside of GPLS, most project decisions have been made by gaining the informal consensus of interested parties via the mailing lists and/or the IRC channel. This is, for example, how the decision to switch from CVS to Subversion occurred; how bug and enhancement tracking went from a Bugzilla instance to a read-only Trac instance to an open Launchpad instance; and how we have set up conference site selection committees. People who define a problem in the project and offer to provide a solution are generally given whatever power we can give them to achieve their goal. | ||
+ | |||
+ | At the Evergreen International Conference in 2010, Elizabeth McKinney of GPLS solicited participation from a broad set of representatives to go forward with forming that Evergreen Software Foundation. Many discussions of potential governance models and membership structures have been held since then, and there is overwhelming support to seek a membership within the Software Freedom Conservancy while continuing these discussions. We understand that the Software Freedom Conservancy has experience in setting up governance structures with open source projects, and if the Conservancy accepts our application we would welcome your insight and suggestions. | ||
+ | |||
+ | * Existing for-profit or non-profit affiliations, | ||
+ | |||
+ | Most of the committers to the Evergreen and OpenSRF repositories are or have been employees of Equinox Software, Inc (http:// | ||
+ | |||
+ | Dan Scott, one of the committers to Evergreen and OpenSRF, holds a full-time position as a systems librarian with Laurentian University, although as of September 2010 he will be seconded to a full-time Evergreen development position within the " | ||
+ | |||
+ | The King County Library system (Issaquah, WA), in partnership with the Galecia Group (Petaluma, CA), won a $1 million IMLS grant in September 2009, entitled “Powered by Open Source.” King County has partnered with six other library systems to provide a peer-to-peer support model for open source libraries. The grant-funded website for their open source project, RSCEL (Resource & Sharing Cooperative of Evergreen Libraries) is at http:// | ||
+ | |||
+ | * Names, email addresses, and affiliations of key developers, past and present. | ||
+ | |||
+ | http:// | ||
+ | |||
+ | * Information about any past for-profit or non-profit organizational affiliations the project has had. | ||
+ | |||
+ | In 2006, GPLS contracted the development of the initial SIP 2.0 support (realized in http:// | ||
+ | |||
+ | Evergreen was one of two free software library systems that participated in the Electronic Information For Libraries Free and Open Source Software (eIFL-FOSS) ILS project: http:// | ||
+ | |||
+ | Lyrasis (formerly Solinet) helped organize the 2009 Evergreen International Conference and offered Evergreen training and other services at http:// | ||
+ | |||
+ | Finally, on the subject of contributing a percentage of our funds to the Conservancy, | ||
+ | |||
+ | If you have any questions, of course, please feel free to address them to me at dan@coffeecode.net. | ||
+ | |||
+ | Many thanks, | ||
+ | Dan Scott |
governance/software_freedom_conservancy_membership_application.1283787847.txt.gz · Last modified: 2022/02/10 13:34 (external edit)