Skip to content
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.

Commit

Permalink
Initial draft per request form from Iain Robertson
Browse files Browse the repository at this point in the history
  • Loading branch information
riscv-tech-admin committed Jun 1, 2023
1 parent 17e127e commit 74679f1
Showing 1 changed file with 6 additions and 32 deletions.
38 changes: 6 additions & 32 deletions CHARTER.md
Original file line number Diff line number Diff line change
@@ -1,37 +1,11 @@
# {{ New Group Name }} {{ New Group Type }} Charter
# RISC-V E-Trace Encapsulation TG Charter

## Directions for creating a charter
The information in this file should be created as part of the group formation and approved by your sponsoring group. See the [Chairs Best Practices policy](https://docs.google.com/document/d/1rtXskVd7YyFq74tQ2OrInyM_-OQa228R5UZs5Pm3Vz0/) for more details.
The E-Trace Encapsulation TG will define how trace packet payloads shall be encapsulated.

A good Task Group (TG) charter describes how it achieves filling in a gap defined by the Special Interest Group (SIG) or Committee that spawned it (directly or dotted line). It lists the specific small set of deliverables it will deliver.
In line with the original charter, the ratified Enhanced Trace for RISC-V standard defines packet payloads for instruction and data trace but does not fully define how this should be encapsulated. Chapter 7 gives some illustrative examples but this is insufficiently detailed and informative only.

A SIG is an extension of a Committee, in that its only deliverables are strategy, gaps, and prioritizations, and helping spawn other SIGs or TGs to fill the gaps. A good SIG charter spells out the small set of topic areas their strategy will address along with its responsibilities as laid out in this bullet.
The E-Trace Encapsulation TG will deliver a normative trace encapsulation specification that:

In the next section is a raw template. Delete the section header and substitute appropriate text in for [ALL CAPS ITEMS AS DESCRIBED].
- Applies to Enhanced Trace for RISC-V packets but which is not restricted to that standard

**Delete this whole section when done.**

## Raw template

The {{ New Group Name }} {{ New Group Type }} will [OVERALL MISSION STATEMENT in 2-3
SENTENCES]

[THIS PARAGRAPH IS OPTIONAL]
The [TERM 1] IS [DEFINITION 1]. [EXPLANATION OF IMPORTANCE OF TERM 1]. [MORE TERMS AND DEFINITIONS AS NEEDED]

[BACKGROUND INFORMATION ABOUT RELEVANCE OF GROUP/TECHNOLOGY]

The {{ New Group Name }} {{ New Group Type }} will [DELIVER SOMETHING] [WITH THESE ATTRIBUTES]:

- [ATTRIBUTE 1]
- [ATTRIBUTE 2]
- [... AS NEEDED]

[THIS PARAGRAPH AND LIST ARE OPTIONAL, ESPECIALLY IF THE LIST IS EMPTY]
The following items are presently not planned to be delivered as part of this work, but may be considered in future versions:

1. [FEATURE 1]
1. [FEATURE 2]
1. [... AS NEEDED]

To achieve its goals, the {{ New Group Name }} {{ New Group Type }}, will interact with the following groups: [GROUP NAME 1] [GROUP TYPE 1], [GROUP NAME 2] [GROUP TYPE 2], [...] and [GROUP NAME N] [GROUP TYPE N].
To achieve its goals, the E-Trace Encapsulation TG, will interact with the following groups: SoC HC, DTPM SIG.

0 comments on commit 74679f1

Please sign in to comment.