Skip to content

Track drafts/ and add the "Role of TASC in the PDAP" directive (draft) - #101

Open
mamanambiya wants to merge 4 commits into
ga4gh:mainfrom
mamanambiya:docs/pdap-review-directive
Open

mamanambiya wants to merge 4 commits into
ga4gh:mainfrom
mamanambiya:docs/pdap-review-directive

Conversation

@mamanambiya

Copy link
Copy Markdown
Collaborator

Summary

Two changes, staged together:

  1. Stop ignoring drafts/. The folder was gitignored (only a .stub kept it in the tree), so in-progress TASC outputs could not be version-controlled or reviewed before approval. This removes the drafts/ ignore rule and the now-redundant .stub, so drafts can be tracked and reviewed while still in draft.
  2. Add the draft directive "What TASC Does in the PDAP, and What to Expect." It sets out TASC's role in PDAP v2 — what it reviews and decides, the risk tiers, engagement across the lifecycle, accountability, and cross-product conflict resolution. Reconciled against the PDAP v2 draft, the 2026 TASC Interoperability framework, the Technical Product Dossier, and TASC-GOV-01.

Draft workflow

The directive sits under drafts/recommendations/, mirroring its destination (recommendations/) so that approval is a one-level move and its relative links stay valid across it. This introduces a small drafts/<type>/ sub-structure for in-progress work — a deliberate workflow addition, called out here for visibility.

Status and scope

  • Status: Draft — for review and version control, not approval.
  • The directive forward-references TASC-ADR-012 (../adr/TASC-ADR-012.md) and the PDAP Review Operating Procedure, which are separate in-progress drafts not included in this PR; those links resolve once those drafts land.

Notes

Drafting assistance is disclosed in the directive's own Notes section, consistent with existing TASC outputs.

Stop ignoring drafts/ so in-progress TASC outputs can be version
controlled and reviewed before approval, and remove the now-redundant
drafts/.stub placeholder.

Add the draft directive "What TASC Does in the PDAP, and What to Expect"
under drafts/recommendations/, mirroring where it moves on approval
(recommendations/). It forward-references TASC-ADR-012 and the PDAP
Review Operating Procedure, which are separate in-progress drafts not
included in this change.
List the 16 workshop participants with institution and GA4GH work
stream / role, sourced from the GA4GH Individual Contributors page and
the TASC README.
Align the H1 and metadata Title with the filename, issue ga4gh#93, and how
the document is referenced elsewhere. The descriptive framing remains in
the Abstract.
Promote the "TASC reviews, judges sufficiency, and arbitrates" ADR into
drafts/adr/ (mirroring adr/), keeping number 012 — 006-011 are reserved
and 013/014 are the sibling workshop ADRs. Point the directive and ADR
at each other via the stable ../adr/ and ../recommendations/ links.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant