These are the individual and collective responsibilities of core committers.

Individual responsibilities

To actively review and merge patches submitted by other developers.
To provide feedback and constructive criticism on submitted patches.
To take part in discussions regarding future developments and design directions.
To take part in discussions regarding policies and procedures for Evergreen development.
To, when it comes to it, say "no" to a code contribution, but in such a way as to avoid alienating potential contributors.
To model good participation as a developer in the Evergreen community
To advocate for:
- The quality of Evergreen's architecture and its continual improvement
- A holistic view of Evergreen's features and userbase. In other words, a committer should not only represent the needs of the institution that employs them
To provide encouragement to other committers who are taking on group responsibilities.
To assist in directing people to other committers who are working on a group responsibility, even when not personally engaged in it.

Group responsibilities

To act as coders of last resort as needed for the sake of successfully releasing Evergreen and dealing with security issues
To assist new and "mid-career" developers by
- writing technical documentation
- engaging in mentorship, formally or informally
To identify and foster new core committers