You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
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:
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.
Identify who in the CTWG will curate the initial terms.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
The Bounty Effort should not be considered complete until these WG reps sign-off on validation of usage.
The text was updated successfully, but these errors were encountered: