February 2, 2010 - Revision history

Mtesauro: /* OLD BUSINESS */ Added Conflict resolution process and Wiki outsourcing to old business

2010-02-02T15:44:24Z

‎OLD BUSINESS: Added Conflict resolution process and Wiki outsourcing to old business

KateHartmann: /* NEW BUSINESS */

2010-02-02T01:00:26Z

‎NEW BUSINESS

Alison.McNamee: /* NEW BUSINESS */

2010-02-01T21:46:10Z

‎NEW BUSINESS

Jeff Williams at 19:41, 1 February 2010

2010-02-01T19:41:01Z

Jeff Williams at 19:40, 1 February 2010

2010-02-01T19:40:50Z

Jeff Williams at 19:39, 1 February 2010

2010-02-01T19:39:25Z

Jeff Williams at 19:38, 1 February 2010

2010-02-01T19:38:05Z

Jeff Williams at 15:45, 1 February 2010

2010-02-01T15:45:31Z

Alison.McNamee: /* Financials */

2010-01-29T14:33:43Z

‎Financials

Alison.McNamee: Created page with '==Financials== To see the final numbers for 2009, click [http://www.owasp.org/index.php/File:2009_Numbers.xlsx Here]'

2010-01-27T18:18:45Z

Created page with '==Financials== To see the final numbers for 2009, click [http://www.owasp.org/index.php/File:2009_Numbers.xlsx Here]'

New page

==Financials==

To see the final numbers for 2009, click [http://www.owasp.org/index.php/File:2009_Numbers.xlsx Here]

@@ Line 22: / Line 22: @@
 ==OLD BUSINESS==
 ;TBD Title
 :TBD Description
 ==NEW BUSINESS==

← Older revision		Revision as of 01:00, 2 February 2010
Line 40:		Line 40:
	;Proposal - OWASP should move off of mailman and onto groups.owasp.org		;Proposal - OWASP should move off of mailman and onto groups.owasp.org
	:This brings the full power and ease of administration of Google Groups to an OWASP domain. The existing archives have been uploaded to Google docs where anyone can [https://docs.google.com/leaf?id=0ByUwHYYmOdvrNTBiZGJlNzMtZWY3NC00YjZhLTgyOWUtNGFkZDE2ZGYwZTMx&hl=en search them]. The only real hiccup is that people must have a google account to use this (or an owasp.org account). We can force add all existing members and their transition to the new list should be seamless - this will get them email list functionality. If they want the full forum, they'll need to have a google account. One other hiccup is that OWASP-ALL will generate one email per list. We can manage a list of lists, but any message will get multiplexed across all of them. Ideas?		:This brings the full power and ease of administration of Google Groups to an OWASP domain. The existing archives have been uploaded to Google docs where anyone can [https://docs.google.com/leaf?id=0ByUwHYYmOdvrNTBiZGJlNzMtZWY3NC00YjZhLTgyOWUtNGFkZDE2ZGYwZTMx&hl=en search them]. The only real hiccup is that people must have a google account to use this (or an owasp.org account). We can force add all existing members and their transition to the new list should be seamless - this will get them email list functionality. If they want the full forum, they'll need to have a google account. One other hiccup is that OWASP-ALL will generate one email per list. We can manage a list of lists, but any message will get multiplexed across all of them. Ideas?
		+
		+	;Proposal - OWASP replace "cafe press" with an EBay Store to make OWASP branded gear available.

@@ Line 33: / Line 33: @@
 ;2009 Financial Results
 :The [http://www.owasp.org/index.php/File:2009_Final_Numbers.xlsx final numbers for 2009] have been prepared.
 ;Proposal - OWASP should create a global OWASP-Alerts mailing list

@@ Line 15: / Line 15: @@
 ;Minutes
-:Kate Hartman
+:Kate Hartmann
 ;Participants

@@ Line 11: / Line 11: @@
 :1-866-534-4754 Code: 7452912855
-;MEETING LEADER
+;Leader
 :Jeff Williams
-;IDEA CATCHER
+;Minutes
 :Kate Hartman

@@ Line 34: / Line 34: @@
 :The [http://www.owasp.org/index.php/File:2009_Final_Numbers.xlsx final numbers for 2009] have been prepared.
-;Proposal: OWASP should create a global OWASP-Alerts mailing list
+;Proposal - OWASP should create a global OWASP-Alerts mailing list
 :There has been a request for the creation of a single OWASP-wide vulnerability reporting mailing list, OWASP-alerts, so that corporations can monitor for vulnerabilities in our software.  This is a PCI requirement. The items posted here would be security vulnerabilities in our libraries (ESAPI, AntiSamy, Encoding, and maybe our tools). Assuming we support the idea, we need to decide who would moderate the list.
-;Proposal: OWASP should move off of mailman and onto groups.owasp.org
+;Proposal - OWASP should move off of mailman and onto groups.owasp.org
 :This brings the full power and ease of administration of Google Groups to an OWASP domain. The existing archives have been uploaded to Google docs where anyone can [https://docs.google.com/leaf?id=0ByUwHYYmOdvrNTBiZGJlNzMtZWY3NC00YjZhLTgyOWUtNGFkZDE2ZGYwZTMx&hl=en search them]. The only real hiccup is that people must have a google account to use this (or an owasp.org account). We can force add all existing members and their transition to the new list should be seamless - this will get them email list functionality. If they want the full forum, they'll need to have a google account. One other hiccup is that OWASP-ALL will generate one email per list. We can manage a list of lists, but any message will get multiplexed across all of them.  Ideas?

@@ Line 1: / Line 1: @@
-[[NOTOC]]
+__NOTOC__
 ==AGENDA==
@@ Line 30: / Line 31: @@
 Committees (and projects) should post items (in the form of a proposal) here for consideration by the Board
-;Finance Committee
+;2009 Financial Results
 :The [http://www.owasp.org/index.php/File:2009_Final_Numbers.xlsx final numbers for 2009] have been prepared.
-;ESAPI Project
+;Proposal: OWASP should create a global OWASP-Alerts mailing list
-:There has been a request for the creation of a single OWASP-wide vulnerability reporting mailing list, OWASP-alerts. The items posted here would be security vulnerabilities in our libraries (ESAPI, AntiSamy, Encoding, and maybe our tools). Assuming we support the idea, we need to decide who would moderate the list.
+:There has been a request for the creation of a single OWASP-wide vulnerability reporting mailing list, OWASP-alerts, so that corporations can monitor for vulnerabilities in our software.  This is a PCI requirement. The items posted here would be security vulnerabilities in our libraries (ESAPI, AntiSamy, Encoding, and maybe our tools). Assuming we support the idea, we need to decide who would moderate the list.

← Older revision		Revision as of 15:45, 1 February 2010
Line 1:		Line 1:
−	==~~Financials~~==	+	[[NOTOC]]
		+	==AGENDA==

−	~~To see~~ the ~~final numbers~~ for ~~2009, click~~ [http://www.owasp.org/index.php/File:2009_Final_Numbers.xlsx ~~Here~~]	+	http://www.owasp.org/index.php/OWASP_Board_Meetings
		+
		+	;When
		+	:Tue February 2, 2010 5pm – 6pm GMT (no daylight saving)
		+
		+	;Where
		+	:1-866-534-4754 Code: 7452912855
		+
		+	;MEETING LEADER
		+	:Jeff Williams
		+
		+	;IDEA CATCHER
		+	:Kate Hartman
		+
		+	;Participants
		+	:Please review the progress of the Global Committee http://www.owasp.org/index.php/Global_Committee_Pages and prepare your report to status on old business and new business.
		+
		+
		+	==OLD BUSINESS==
		+
		+	;TBD Title
		+	:TBD Description
		+
		+
		+	==NEW BUSINESS==
		+
		+	Committees (and projects) should post items (in the form of a proposal) here for consideration by the Board
		+
		+	;Finance Committee
		+	:The [http://www.owasp.org/index.php/File:2009_Final_Numbers.xlsx final numbers for 2009] have been prepared.
		+
		+	;ESAPI Project
		+	:There has been a request for the creation of a single OWASP-wide vulnerability reporting mailing list, OWASP-alerts. The items posted here would be security vulnerabilities in our libraries (ESAPI, AntiSamy, Encoding, and maybe our tools). Assuming we support the idea, we need to decide who would moderate the list.

← Older revision		Revision as of 14:33, 29 January 2010
Line 1:		Line 1:
	==Financials==		==Financials==

−	To see the final numbers for 2009, click [http://www.owasp.org/index.php/File:~~2009_Numbers~~.xlsx Here]	+	To see the final numbers for 2009, click [http://www.owasp.org/index.php/File:2009_Final_Numbers.xlsx Here]