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-05"

From OWASP
Jump to: navigation, search
(Added 1 item to the agenda)
 
(4 intermediate revisions by 2 users not shown)
Line 20: Line 20:
  
 
*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.  
 
*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|"OWASP Projects Dashboard"]] with all the OWASP Projects
+
** See the [[OWASP Projects Dashboard|"OWASP Projects Dashboard"]] with all the OWASP Projects,
** Working to finishing up the email to be sent to all OWASP leaders. Happily it will be done until the begining of this meeting.
+
** [https://docs.google.com/a/owasp.org/Doc?id=dcn8962c_51ftpmj2g7 Email/draft to be sent to all OWASP leaders].
  
 
----
 
----
Line 29: Line 29:
 
*** Methodology to fill in the referred tab?
 
*** Methodology to fill in the referred tab?
 
*** Methodology to link the tab to each project?
 
*** Methodology to link the tab to each project?
 +
 +
----
 +
 +
* 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.
  
 
----
 
----
Line 43: Line 50:
  
 
* Update on the conversation between Sebastien and Matt.
 
* Update on the conversation between Sebastien and Matt.
 +
* Start discussion on changing current Wikimedia to a more professional solution:
 +
** http://www.wikimatrix.org/compare/Swirrl+Confluence+PBwiki+CentralDesktop
 +
** http://www.atlassian.com/software/confluence/pricing.jsp?type=nonprofit
  
 
= Issues for next Meeting  =
 
= Issues for next Meeting  =

Latest revision as of 20:12, 5 October 2009

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)



  • 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?

  • 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

Issues for next Meeting

  • Add here

Minutes

  • Meeting started 10PM/GMT+1
  • Add here