ArchivesSpace Product Management Group

 

Proposal to Establish an ArchivesSpace Product Management Group

 

Purpose

The ArchivesSpace Product Management Group is a group representing the ArchivesSpace and collaborating  with the ArchivesSpace Product Manager and Governance Board to set the policies for developing the ArchivesSpace application, including establishing criteria for guiding substantial changes to the application (e.g., adding a new module) or integration with other products,   for evaluating and planning modifications to the application interfaces and technical stack, and for defining a process for vetting code contributions.

 

Membership, including Liaisons from other groups (11 members)

An elected representative for each ArchivesSpace membership level (5).  [Terms shall be for two years.  In the first year, 2-3 terms should be for one or three years, in order to introduce a stagger and ensure some continuity over time.]

Chairs of the Technical and User Advisory Councils (2)

Governance Board liaisons to the Technical and User Advisory Councils (2)

ArchivesSpace Technical Lead (1)

ArchivesSpace Program Manager (1)

The Product Management Group will determine internally how best to organize itself to address and document its work. 

 

Reporting

The Product Management Group will report its activities to the Governance Board. 

 

Meetings

The Product Management Group will meet monthly at a fixed time. 

 

 

 

Questions:  

 

1:  Can the envisioned purpose of this new group be addressed by groups already in place, and thereby avoid revision of bylaws and increasing the election workload?

 

2:  Should this group subsume the TAC / UAC Coordinating Committee, and, thus, take on as part of its charge, advisory oversight of the councils?  This would certainly ensure that the group would have enough work month-to-month. 

 

3:  What would be the relationship of this group to the prioritization team?  Certainly it would set policy for integrations and large-scale additions to the application.  But should it be involved in setting priorities for releases?