This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "GPC Agenda 2009-10-19"
From OWASP
(13 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
= Agenda = | = Agenda = | ||
− | == | + | == Current Meeting == |
+ | *New Assessment Criteria | ||
+ | ** Release Assessment | ||
+ | ***[[:File:OWASP-ReleasesDiag Chandras-Version.png|Pravir's diagram - First stab]], [[:File:OWASP-ReleasesDiag v3.png|Pravir's diagram - Second stab]], | ||
+ | ***[[:File:Release-Assessement Matts-Drawing.jpg|Matt's illustration]]. | ||
− | + | == From Previous Meeting/Follow up == | |
− | |||
*[[:Summit 2009|"OWASP Mini-Summit 2009"]]/[[:OWASP AppSec DC 2009]]: | *[[:Summit 2009|"OWASP Mini-Summit 2009"]]/[[:OWASP AppSec DC 2009]]: | ||
− | ** [https://docs.google.com/a/owasp.org/present/edit?id=0Ae9M2vJFBkqfZGZjOGJoY3dfMmM3cHI0OGN6&hl=en Brad's PPT]. | + | **[https://docs.google.com/a/owasp.org/present/edit?id=0Ae9M2vJFBkqfZGZjOGJoY3dfMmM3cHI0OGN6&hl=en Brad's PPT]. |
− | + | **[[:File:AppSec DC 2009 OWASP GPC.ppt|Brad's PPT - Second version]] | |
− | + | ***Issues (revision)we decided last meeting to add to the PPT: | |
− | + | ****One slide about review process, | |
− | * | + | ****A reviewers' drive, |
− | ** | + | ****What we ask to all projects |
− | ** | + | ****Maybe a PDF with all diagrams and processes/everything we have, |
+ | ****What we want from our community, | ||
+ | ****SoC, | ||
+ | ****We should use a methodology similar to [[OWASP Working Session Top 10 2009|the one we used in the former Summit]], | ||
+ | ****Projects committee should involve the community in determining which projects/project leaders are supported financially. Travel, evangelism, publication, training, etc..... | ||
---- | ---- | ||
− | * | + | *Honorary memberships to be given to "active" OWASP participants (chapter leader, project participants, etc.). Chapter and projects committees to submit proposal for persons to be given membership: |
− | ** | + | **Community's adhesion has been very limited if any - See the [[OWASP Projects Dashboard|"OWASP Projects Dashboard"]], |
− | ** | + | **It seems we haven't been clear and confused project leaders with the distinction between "contributors" and ""past_leaders_special_contributions" - Action must be taken. |
− | ** | + | ** We need to add a column in the [[OWASP Projects Dashboard|"OWASP Projects Dashboard"]] to show "current" contributors. |
---- | ---- | ||
− | * Consider having a single release roadmap page that is not attached to a single version but instead is the summation of the various release roadmaps. | + | *Spreading [[:Template:OWASP Project Identification Tab|OWASP Project Details Tab]] through [[OWASP Projects Dashboard|ALL OWASP Projects]]. |
− | ** The single page is easier for project leaders to find/edit | + | *Waiting until we (Jason's task?) come up with revised&improved wiki code to either link project with release and to consider the below referred, |
− | ** The single page would show the progression of the project to external audiences | + | **Consider having a single release roadmap page that is not attached to a single version but instead is the summation of the various release roadmaps. |
− | ** Makes the release roadmap very similar to a changelog - which is more useful if its in one place rather then in bits attached to releases | + | ***The single page is easier for project leaders to find/edit |
− | + | ***The single page would show the progression of the project to external audiences | |
− | + | ***Makes the release roadmap very similar to a changelog - which is more useful if its in one place rather then in bits attached to releases. | |
− | |||
− | |||
− | |||
---- | ---- | ||
Line 42: | Line 46: | ||
*Committee members' evaluation process. | *Committee members' evaluation process. | ||
**"GPC - Send 'Individual Committee Member' [https://spreadsheets.google.com/viewform?formkey=ckdDbXE0bkxPM3dkbDZvSmFNWVBGcnc6MA online form]". | **"GPC - Send 'Individual Committee Member' [https://spreadsheets.google.com/viewform?formkey=ckdDbXE0bkxPM3dkbDZvSmFNWVBGcnc6MA online form]". | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Issues for next Meeting = | = Issues for next Meeting = |
Latest revision as of 14:56, 21 October 2009
Previous meetings and Dial-in details
see GPC Meetings for previous GPC Meetings Agenda and the Dial-In details
Agenda
Current Meeting
- New Assessment Criteria
- Release Assessment
From Previous Meeting/Follow up
- "OWASP Mini-Summit 2009"/OWASP AppSec DC 2009:
- Brad's PPT.
- Brad's PPT - Second version
- Issues (revision)we decided last meeting to add to the PPT:
- One slide about review process,
- A reviewers' drive,
- What we ask to all projects
- Maybe a PDF with all diagrams and processes/everything we have,
- What we want from our community,
- SoC,
- We should use a methodology similar to the one we used in the former Summit,
- Projects committee should involve the community in determining which projects/project leaders are supported financially. Travel, evangelism, publication, training, etc.....
- Issues (revision)we decided last meeting to add to the PPT:
- Honorary memberships to be given to "active" OWASP participants (chapter leader, project participants, etc.). Chapter and projects committees to submit proposal for persons to be given membership:
- Community's adhesion has been very limited if any - See the "OWASP Projects Dashboard",
- It seems we haven't been clear and confused project leaders with the distinction between "contributors" and ""past_leaders_special_contributions" - Action must be taken.
- We need to add a column in the "OWASP Projects Dashboard" to show "current" contributors.
- Spreading OWASP Project Details Tab through ALL OWASP Projects.
- Waiting until we (Jason's task?) come up with revised&improved wiki code to either link project with release and to consider the below referred,
- Consider having a single release roadmap page that is not attached to a single version but instead is the summation of the various release roadmaps.
- The single page is easier for project leaders to find/edit
- The single page would show the progression of the project to external audiences
- Makes the release roadmap very similar to a changelog - which is more useful if its in one place rather then in bits attached to releases.
- Consider having a single release roadmap page that is not attached to a single version but instead is the summation of the various release roadmaps.
- Committee members' evaluation process.
- "GPC - Send 'Individual Committee Member' online form".
Issues for next Meeting
- Add here
Minutes
- Meeting started 10PM/GMT+1
- Add here