Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Permanent Working Groups / Teams

DSpace Product Planning

...

Group

The DSpace Product Planning Team Group develops and maintains the DSpace Product Plan in conjunction with the DSpace Community Advisory Team (DCAT) and the DSpace Technology TeamPlanning Group.

Primary Responsibilities:

  • Create / Refresh the DSpace Product Plan / Product Roadmap and present to Steering Group for approval (Yearly activity)
  • Refresh High Level Vision (in conjunction with DCAT and Technology TeamPlanning Group) once every three years

Membership:

  • Members are selected from the DSpace Community Advisory Team and DSpace Technology TeamPlanning Group.  More details forthcoming.

...

DCAT is made up of community repository managers. DCAT plays a user advisory role with Committers, Steering Group and Technology Planning Group.  They also help to gather and maintain a list of common use cases from the members (and wider community). These use cases help to inform the Product Plan.

...

More detailed and official charge/role coming soon.  Also see: DSpace Community Advisory Team

DSpace Technology

...

Planning Group

The DSpace Technology Team advises Planning Group advises all groups on anything related to technology. They advise  

Primary Responsibilities:

  • Advise on technical implementation options based on prioritized use cases (from DCAT) and/or the proposed product plan

...

  • (from Product Planning Group).
  • As necessary, research and prototype specific technical implementation options (for larger scale projects), perhaps in conjunction with other Committers
  • Maintain DSpace Technical Roadmap (along with Committers) based on Product Plan

Membership:

  • Chair: DSpace Technical Lead
  • Members are selected from the Committers group by the Technical Lead and the Committers. Members must 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.

...

DSpace Committers have primary control over the code. They are a meritocracy (members are added from the community based on merit)

Primary Responsibilities:

  • Maintain the codebase
  • Review all code changes to ensure stability, etc.
  • Help to provide support to community developers and users (via IRC, mailing lists, etc.)

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.

 

More detailed and official charge/role coming soon. Also see: DSpaceContributors