Clarify Transparency and Well Communicated architecture.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The RFC need to expand and organize the different transparency aspects: process, documentation, code and people. This needs to play into well communicated architecture planning. Since much of the OWASP Top 10 and general CWEs are issues with consistently applying architecture, there may need to be a stand-alone tenant that expresses the need for Well Communicated and Applied Architecture, perhaps with a succinct title.
Contributor guide
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 by reading the RFC and reviewing how it currently presents transparency and architecture planning. Done means organizing the process, documentation, code, and people aspects, clarifying how well-communicated architecture fits, and deciding whether a standalone tenet with a succinct title is needed.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100