Problem description
The volume of whitepapers in CAMARA is growing, and there is no consistent process. The Wiki-based approach used for earlier whitepapers (SIM Swap, Tenure, etc.) caused edit conflicts and lacked contributor traceability. The CQM model (Markdown via PRs in a dedicated repo) works better technically, but it is not formally adopted as the standard. Upcoming whitepapers for Device Location, Device Status, Population Density Data, and Region Device Count span multiple repositories, so there is no natural home for the content. The Marketing WG repository cannot host API-related technical documentation (Project Charter, CC BY 4.0 constraint). No formal handoff process exists between technical authors and the Marketing WG designer team.
Possible evolution
Establish a reusable process covering three things: (1) a canonical location for whitepapers that span multiple Sub Projects; (2) Markdown as the normative authoring format, with a defined conversion step to the final format required by Marketing; (3) a formal handoff interface with the Marketing WG, including content requirements, review checkpoints, and publication timelines.
Alternative solution
Use the Sub Project repository when the whitepaper covers only APIs within that scope (consistent with the CQM model). For cross-Sub Project whitepapers, create a dedicated shared repository under the camaraproject organization with explicit CODEOWNERS. Confirm that the Marketing WG repository is out of scope as a hosting location at any stage of the technical authoring process.
Additional context
The CQM Sub Project repository is the reference model. The Marketing WG's role should be limited to final format, design assets, and external publication — not hosting of technical drafts. Governance of any shared repository (ownership, PR approval) must be resolved before creation, to avoid an orphaned repo.
Problem description
The volume of whitepapers in CAMARA is growing, and there is no consistent process. The Wiki-based approach used for earlier whitepapers (SIM Swap, Tenure, etc.) caused edit conflicts and lacked contributor traceability. The CQM model (Markdown via PRs in a dedicated repo) works better technically, but it is not formally adopted as the standard. Upcoming whitepapers for Device Location, Device Status, Population Density Data, and Region Device Count span multiple repositories, so there is no natural home for the content. The Marketing WG repository cannot host API-related technical documentation (Project Charter, CC BY 4.0 constraint). No formal handoff process exists between technical authors and the Marketing WG designer team.
Possible evolution
Establish a reusable process covering three things: (1) a canonical location for whitepapers that span multiple Sub Projects; (2) Markdown as the normative authoring format, with a defined conversion step to the final format required by Marketing; (3) a formal handoff interface with the Marketing WG, including content requirements, review checkpoints, and publication timelines.
Alternative solution
Use the Sub Project repository when the whitepaper covers only APIs within that scope (consistent with the CQM model). For cross-Sub Project whitepapers, create a dedicated shared repository under the
camaraprojectorganization with explicit CODEOWNERS. Confirm that the Marketing WG repository is out of scope as a hosting location at any stage of the technical authoring process.Additional context
The CQM Sub Project repository is the reference model. The Marketing WG's role should be limited to final format, design assets, and external publication — not hosting of technical drafts. Governance of any shared repository (ownership, PR approval) must be resolved before creation, to avoid an orphaned repo.