Extended Description
As a FedRAMP ASAP stakeholder, I would like to have active communication between users, developers, and the FedRAMP PMO, so OSCAL validations and tooling will continue to improve.
Context: users need a clear way to communicate with developers and the FedRAMP PMO. Github issues in the GSA repository is serving that purpose. Some users are not confident of where to document their problems and feature requests, and would be served by clarity on how and where to create issues.
Acceptance Criteria
[ ] Links to Github issues and/or discussions prominently documented
Definition of Done
[ ] Acceptance criteria met
[ ] Unit test coverage of our code > 95%
[ ] Automated code quality checks passed
[ ] Security reviewed and reported
[ ] Reviewed against plain language guidelines
[ ] Code must be self-documenting
[ ] No local tech debt
[ ] Load/performance tests passed – needs to be created/automated
[ ] Documentation updated
[ ] Architectural Decision Record completed as necessary for significant design choices
Extended Description As a FedRAMP ASAP stakeholder, I would like to have active communication between users, developers, and the FedRAMP PMO, so OSCAL validations and tooling will continue to improve.
Context: users need a clear way to communicate with developers and the FedRAMP PMO. Github issues in the GSA repository is serving that purpose. Some users are not confident of where to document their problems and feature requests, and would be served by clarity on how and where to create issues.
Acceptance Criteria
Definition of Done