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
GPC Agenda 2009-10-19
From OWASP
Revision as of 14:51, 12 October 2009 by Paulo Coimbra (talk | contribs) (Created page with '== Previous meetings and Dial-in details == see GPC Meetings for previous GPC Meetings Agenda '''and the Dial-In details''' = Agenda = == From Pre…')
Previous meetings and Dial-in details
see GPC Meetings for previous GPC Meetings Agenda and the Dial-In details
Agenda
From Previous Meeting/Follow up
- New Assessment Criteria
- Pravir's assessment diagram - Note that this is not related to 'Project Releases' but to 'Project Health'
- We need to create a separate diagram to help our project leaders to understand the desired workflow for Releases (which go from Alpha, to Beta, to Stable)
- Modification of Assessment Criteria v2 (ACv2)
- Review of email templates to reflect any changes from above.
- Pravir's assessment diagram - Note that this is not related to 'Project Releases' but to 'Project Health'
- 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.
- See the "OWASP Projects Dashboard" with all the OWASP Projects,
- Email/draft to be sent to all OWASP leaders.
- Spreading OWASP Project Details Tab through ALL OWASP Projects.
- ALL the projects with defined leadership already HAVE the GPC Project Details Tab - Check out "OWASP Projects Dashboard",
- Methodology to fill in the referred tab?
- Methodology to link the tab to each project?
- ALL the projects with defined leadership already HAVE the GPC Project Details Tab - Check out "OWASP Projects Dashboard",
- 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.
- Projects committee should determine which projects/project leaders are supported financially. Travel, evangelism, publication, training, etc.....
- Matt Tesauro's draft to deal with this kind of issues.
- Committee members' evaluation process.
- "GPC - Send 'Individual Committee Member' online form".
Current Meeting
- Update on the conversation between Sebastien and Matt.
- Start discussion on changing current Wikimedia to a more professional solution:
Issues for next Meeting
- Add here
Minutes
- Meeting started 10PM/GMT+1
- Add here