Changes to Technical Specifcation Group formation due to TRC

[glenrobson]

With the formation of the TRC the TSG formation process has been updated in the following pull request to reflect the bare minimum of changes required to keep the two documents in sync:

#139

and is available at:

https://preview.iiif.io/root/tsg_process/community/groups/framework/#technical-specification-group-formation-and-approval

This gives an opportunity to review the formation process to see if it could be improved. Here are my suggestions:

Order of formation:

1. Community raise need and ideally but not mandatory to contact Technical coordinator to facilitate the next steps
2. Document outline scope, deliverables timescale
   2a. Coco and TRC encouraged to participate in the document creation process
3. Document sent out to the community to gauge interest and commitment of resources
4. If sufficient interest is gathered document is submitted to TRC
5. If the TRC approves the group they will assign two members of the group to support the group to ensure any specifications are consistent with other specifications. (Should one be chair?)
6. Final review from the Coordinating Committee

Changes to and proposed standards from the TSGs will be approved by the TRC before publication.

Inactivity
If the group fails to meet regularly and work does not progress the MD will discuss with the Chairs and the TRC representatives whether the group should continue or dissolve. A motion to dissolve will be approved by Coco and TRC.

This proposal would replace the requirement to have two editors and replace this with two TRC representatives allowing a wider and more diverse pool to assist in the work of TSGs. Note the TRC representatives should not be IIIF Staff and maybe not other TSG chairs to avoid conflicts of interest so would come from Editors, IIIF-C members and from the 5 community slots.