|
|
(30 intermediate revisions by one other user not shown) |
Line 1: |
Line 1: |
| =Main= | | =Main= |
| | | |
− | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | + | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] </div> |
| | | |
| {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- |
Line 24: |
Line 24: |
| | | |
| == Project Resources == | | == Project Resources == |
− | <span style="color:#ff0000">
| |
− | This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
| |
− | </span>
| |
− |
| |
| | | |
| + | * key files are being translated and will be available soon. |
| | | |
| == Project Leader == | | == Project Leader == |
| | | |
| | | |
− | [mailto:cicerogadelha@gmail.com Cicero Gadelha] | + | [mailto:cicero.gadelha@owasp.org Cicero Gadelha] |
| | | |
| == Related Projects == | | == Related Projects == |
− | <span style="color:#ff0000">
| |
− | This is where you can link to other OWASP Projects that are similar to yours.
| |
− | </span>
| |
| | | |
| + | * [[:Category:OWASP_Top_Ten_Project|OWASP Top Ten Project]] |
| | | |
| ==Classifications== | | ==Classifications== |
Line 58: |
Line 53: |
| | | |
| == News and Events == | | == News and Events == |
− | <span style="color:#ff0000">
| + | |
− | This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.
| + | * First meeting, Chapter Fortaleza |
− | </span>
| + | |
| | | |
| | | |
Line 67: |
Line 62: |
| =FAQs= | | =FAQs= |
| | | |
− | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
| |
− | <span style="color:#ff0000">
| |
− | Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
| |
− | </span>
| |
| | | |
| ==How can I participate in your project?== | | ==How can I participate in your project?== |
| | | |
| + | The project is at the very beginning and there are many possibilities, please get in contact with: |
| + | |
| + | * [mailto:cicerogadelha@gmail.com Cicero Gadelha] |
| | | |
| ==If I am not a programmer can I participate in your project?== | | ==If I am not a programmer can I participate in your project?== |
| | | |
| + | Absolutely yes. |
| | | |
| = Acknowledgements = | | = Acknowledgements = |
− | ==Contributors== | + | ==Team== |
− | | |
− | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
| |
− | <span style="color:#ff0000">
| |
− | The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
| |
− | Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
| |
− | Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
| |
− | </span>
| |
| | | |
| + | * Felipe Albuquerque |
| | | |
| + | The OWASP Knowledge Graph is selecting members for the team. |
| | | |
− | The first contributors to the project were:
| + | If you would like to contribute please contact: |
| | | |
| * [mailto:cicerogadelha@gmail.com Cicero Gadelha] | | * [mailto:cicerogadelha@gmail.com Cicero Gadelha] |
Line 97: |
Line 87: |
| | | |
| <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> |
− | <span style="color:#ff0000">
| + | |
− | A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
| |
− | Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
| |
− | </span>
| |
| | | |
| ==Roadmap== | | ==Roadmap== |
| | | |
− | <strong>
| + | |
− | 1. Define the graph structure to store data in a efficient way.
| + | # Define the graph structure to store data in a efficient way. |
− | 2. Represent in graphs the top 10 vulnerabilities.
| + | # Represent in graphs the top 10 vulnerabilities. |
− | 3. Create a tool to use the knowledge graph to detect vulnerabilities and explore theirs caracteristics.
| + | # Create a tool to use the knowledge graph to detect vulnerabilities and explore theirs caracteristics. |
− | 4. Conduct an evaluation of results.
| + | # Conduct an evaluation of results. |
− | 5. Expand the knwoledge graph storing more vulnerabilities.
| + | # Expand the knwoledge graph storing more vulnerabilities. |
− | </strong>
| |
| | | |
| Subsequent Releases will add | | Subsequent Releases will add |
− |
| |
| | | |
| ==Getting Involved== | | ==Getting Involved== |
| | | |
| + | =Minimum Viable Product= |
| | | |
| + | Creation of a model that provides: |
| + | # Creation of Graphs using triples. |
| + | # Representation of vulnerabilities. |
| + | # Study, detect and explore vulnerabilities. |
| | | |
− | =Minimum Viable Product=
| |
− | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
| |
− | <span style="color:#ff0000">
| |
− | This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.
| |
− | Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.
| |
− | </span>
| |
| | | |
| | | |