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

[PROCESS] Bounty Testcase #48

Open
vinomaster opened this issue Mar 29, 2021 · 0 comments
Open

[PROCESS] Bounty Testcase #48

vinomaster opened this issue Mar 29, 2021 · 0 comments

Comments

@vinomaster
Copy link
Contributor

Need

As we plan for a Bounty for the implementation of PR #45, we need to have a mechanism for the validation of the TT tool.

Proposed Solution

Using the "Big 4" release form ToIP, we SHOULD:

  1. Use the TSWG and GSWG as submitters of scoped terms. This work can and SHOULD commence ASAP. Minimally we should get at least a dozen terms from each WG.
  2. Identify who in the CTWG will curate the initial terms.
  3. Identify a WG rep each from TSWG and GSWG that will work with the Bounty developers to test the command-line option scenarios framed in the spec.

The Bounty Effort should not be considered complete until these WG reps sign-off on validation of usage.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant