User Tools

Site Tools


webteam:webplan:2011:section6_recommendations

This is an old revision of the document!


1. People & Process

Creation of an Evergreen Advocate role

The Evergreen community has historically been composed largely of Evergreen developers (and other highly-technical people) and understandably led by those developers. As the software becomes used in libraries across the world, it's natural for the number of non-developers in the community to grow substantially. We're recommending the creation - either formally or informally - of an Evergreen Advocate role in the community. The objectives of Evergreen Advocates would be:

  • Provide leadership for, and representation of, non-developers in the Evergreen community
  • Promote the adoption of Evergreen in various library and consortia contexts (e.g., K-12)
  • Teach librarians and related personnel, both inside and outside the Evergreen community, about Evergreen via formal and informal documentation, webinars, in-person gatherings, and other venues as appropriate
  • Share resources, expertise, and opinions about Evergreen on the Evergreen website, the mailing list, and other venues as appropriate
  • Foster a strong sense of community spirit in the Evergreen community by using community building tools and skills, providing volunteer recognition, etc.
  • Encourage widespread participation in the Evergreen community by members, on the website, mailing lists, etc.

Creation of formal Evergreen Website Team

A community website platform that supports the needs of a diverse community and fosters the growth of that community is not something that can be built and then left to run on its own. We're recommending the formation of a formal Website Team, to be composed of self-selected community members, and reporting to the Governance Committee until a formal Evergreen organizational structure can be put in place. The twin primary goals of this Team would be to make short-term improvements to the website as well as plan long-term architecture improvement and maintenance operations. This Team would actively and regularly seek out feedback and suggestions for direction from Evergreen community constituencies, including the Communications Committee, the developer community, DIG, new users and potential users, etc. In addition, this team would be tasked with lowering any barriers to participation in the website and encouraging contributions from as many community members as possible.

Creation of Website Policies

Until the Evergreen Foundation is formalized and intellectual property concerns are subsequently addressed, it would be wise to institute website-related policies as semi-formal community guidelines or terms of service. Specifically, the Website Planning Committee has recognized the need for:

  • A "netiquette policy" to promote civility and community spirit on the website and mailing lists
  • A "privacy policy" to advise community participants about electronic privacy, collection of personally-identifying data, retention of data, distribution of data, etc.
  • An "intellectual property policy" governing the licensing of information contributed to the website, mailing lists, etc.

Active Publication of New Content

The new Website Team, working in conjunction with the Communications Committee and any interested Evergreen Advocates, should create and implement a schedule for regular publication of new Evergreen-related content on the website. For instance, once each week a blog entry about a specific Evergreen feature or case study could be published to the front page of the website.

Accessibility Advocate

In order to form an inclusive and diverse community welcoming all, we are recommending the creation of a formal Accessibility Advocate role, possibly as an adjunct to or within the Website Team. This role would strive to ensure that no groups of people are inadvertently barred from participating in the Evergreen community due to any reason such as visual, auditory, or motor skill impairment, language barriers, etc. We also recommend the creation of a similar role to actively participate in Evergreen software development features related to user experience.

2. Technical

webteam/webplan/2011/section6_recommendations.1303323582.txt.gz · Last modified: 2011/04/20 14:19 by jimcraner

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.