This repository was archived by the owner on Jun 17, 2019. It is now read-only.
-
Couldn't load subscription status.
- Fork 4
Community
Fraser Scott edited this page May 15, 2017
·
3 revisions
This page describes how to participate in the community, how to make code contributions and includes developer-centric documentation.
It is being written with the help of the following two books:
- Identify how we can divide our community into teams.
- Ensure that teams can communicate clearly and effectively.
- Attract a diverse range of contributors to our community to get involved and contribute to our goals.
- Build an environment conductive to our wider goals.
- Define the scope of each team, and help team members understand that scope.
- Understand the extent and range of collaboration between our teams.
- Encourage diversity and opportunity in the community.
- Produce a Code of Conduct.
Our mission is to make secure-by-design a practical reality for all developers and engineers. Using continuous threat modelling through code, we aim to do for security what unit testing and TDD has done for software development.
- Build developer-focused tools that fit into their workflows in order to lower the barrier to entry for threat modelling
- Build a community that shares knowledge, skills and best practices on the subjects of threat modelling
- Build a community that is open and accessible, centred around transparency and open source software
- Software development, including ThreatSpec parsers for different languages as well as reporting and visualisation tools
- Threat specification design to grow the capability of the ThreatSpec "language"
- Threat modelling open source software to test the capabilities of ThreatSpec in the real world
- Design and user experience of the website
- Documentation writing and translations
- Software development
- Web design
- Threat modelling, security review
- Documentation writing