Page History

...

• Advise on technical implementation options based on prioritized use cases (from DCAT) and/or the proposed product plan (from Product Planning Group).
• For larger scale project, research and prototype specific technical implementation options, or lead implementation subgroups to perform those investigations
• Create / refresh the Implementation Plan (Release Plan) / Technical Roadmap on a yearly basis

Membership:

• Chair: DSpace Technical Lead
• Members are selected from the Committers group by the Technical Lead and the Committers. Members must should have some time dedicated to Technology Planning from their workplace (amount TBD).
• Community Contributors (non-Committers) may be selected to this group by a vote of the Committers.

...

• Maintain the codebase. They are the only individuals who can actively change/commit to the codebase
• Resolve bugs or security issues within codebase
• Review all code contributions/changes to ensure stability, etc (see Code Contribution Guidelines).  They are the only individuals who can merge/accept community code contributions.
• Help to resolve bugs or security issues within codebase
• Help to provide ongoing support to community developers and users (via IRC, mailing lists, etc.)
• Perform and manage new releases based on the Implementation Plan / Technical Roadmap (from the Technology Planning Group).

Membership:

• Chair: DSpace Technical Lead
• The Committers group is a meritocracy. Any community member or Committer can nominate someone for Committership. However, an individual only becomes a Committer after they have been voted in by the existing Committers. For more information see Committer Nominations.

...