Skip to content

group-charter_TEMPLATE.md

Latest commit

 

History

History
65 lines (53 loc) · 3.94 KB

group-charter_TEMPLATE.md

File metadata and controls

65 lines (53 loc) · 3.94 KB
Raw

title: (Group name goes here) description: > (Description text goes here, indented two spaces; will display in header; e.g., see https://www.tdwg.org/community/cd/expeditions/ ) background: img: (Put a URL to an image here, e.g., https://images.unsplash.com/photo-1580407196238-dac33f57c410 ) by: (Put the credit for the image here, e.g., Wolfgang Hasselman just the string without quotes) href: (Put the URL to the source of the image, if there is one, here, e.g., https://unsplash.com/photos/6JZJyHXQ-p0 ) github: (URL to GitHub repo; add the name of the group's GitHub repository to the end of this URL: https://github.com/tdwg/[repo-name] ) toc: true

Convener

An interest/task group convener is responsible for:

  • managing the group’s structure and processes
  • reporting to TDWG and the TDWG Executive Committee on the group’s activities; i.e., the primary point of contact for the group.

Co-conveners may be designated, but having more than two is discouraged unless they maintain excellent communication and clear responsibility for tasks.

Core members

  • Members who supported the formation of the group and who have been or expect to be active in the group’s work.
  • Core members should be cognizant of the group’s organization and plans, and should be able to explain to an outsider the purpose, justification and current state of work.
  • Indicate their role within the group wherever appropriate
  • Any core member could substitute for the Convener when required.
  • Core members are not necessarily people who contributed in the past. This is not a credits list. Active participants can and should be identified through contributions to discussion, as well as a separate list of contributors on any produced documents.

Motivation and scope

  • Why is this group needed?
  • Describe the scope of the problems/solutions.
  • Be sure to address how the group is distinct from or interfaces with other TDWG groups, as well as groups in other standards organizations.
  • Any historical background (e.g., previous standards or standards efforts) should be placed in the 'History' section.

Goals, outputs, and outcomes

  • Interest groups should have a few annual goals.
  • Task groups should have specific deliverables and a schedule.
  • A maintenance group may have goals or simply respond to requests for modifications of a standard o Deliverables are outputs that can be used by people outside the group. o Meetings and discussions are not deliverables. Resources (documents, software, diagrams, databases) and standards are deliverables. o Deliverables should be placed in a timeline depicting any prerequisites or dependencies.

Strategy and/or Framework

  • Articulate the steps or methods the group expects to use in describing the problem and developing solutions.
  • Indicate whether the group’s plan will follow an existing framework, such as developing a “RESTful Service" or a “semantic specification in RDF”.

Becoming Involved

  • Required for Interest Groups and recommended for Task Groups.
  • Describe how the group conducts its work. What collaboration tools/platforms do you (expect to) use? (See “Resources” below.)
  • Where can the group’s progress be monitored?
  • How could the reader help the group?
  • Are any skills currently needed within the group?
  • Who should be contacted?

Resources

  • List and link the resources used and promoted by the group - wiki, mailing list, repository.
  • List any references cited or reading that should be considered background for the group’s work.

History/Context

  • Optional.
  • For general interest, clarification, and to give credit for previous work.