commoncriteria / commoncriteria/transforms
TD Validation Report guidance
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The "TDValidationReport.txt" was introduced although I'm not currently aware of its maturity or intended use. Guidance is sought on the appropriate way to handle application of TDs.
Note the current use case is that the editor manually applies all TDs as needed when an updated pass of a PP or module is done (e.g. if tasked to update to version 1.1, all TDs from 1.0 are reviewed and either applied or determined to be OBE) so it's not clear if a different process needs to be followed in the future (e.g. separate commits to apply separate TDs so that the deltas can be shown programmatically).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with TDValidationReport.txt and the manual TD application process described in the issue. Clarify the report's maturity and intended use, then determine what workflow guidance is needed for applying TDs and recording deltas. Done means the repository has an agreed, documented process.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100