Talk:Chairs: March 14, 2011

From OWASP
Revision as of 09:27, 14 March 2011 by Sarah Baso (Talk | contribs)

Jump to: navigation, search

Contents

Talk Page Guidelines

  • Sign your name after a comment by using four tildas (~~~~). Mediawiki automatically replaces this with the right thing
  • Add a new discussion point with the level 2 heading (==Example==) or the '+' sign
  • Add inline replies using increasing number of colons (:)
  • See MediaWiki Talk Page Conventions

From Kate:

  1. Be constructive. An idea is a seed and needs to be nurtured. If you do not agree with the idea, come up with an alternative, don’t just shoot it down.
  2. Be flexible. We can’t all get our way all the time.
  3. Follow through and be honest. If you say you are going to do something, please do it. if you don’t’ have time to do something, say that too.
  4. Encourage your committee members to follow the discussions and to channel their ideas up to you. Let’s keep this the leadership board.
  5. Be creative! Come up with new ways of thinking and opportunities to make things happen!
  6. Hold everything against the Core Values and Core Principles. http://www.owasp.org/index.php/About_OWASP These are in the process of being updated.
  7. Be considerate of other’s time. I am the only one who doesn’t really have anything else to do than talk about OWASP. Let’s use this time to make decisions and move forward, not to debate.

Base Committee Governance Rules

My thought is that we can have a common "base rules" for how committees conduct business, membership, voting, minimum meeting frequency, removing members, chair elections ....... and then extend these rules as applicable to each committee. To get started, we can look at the relevant sections of the document the Conferences Committee passed late last year (http://www.owasp.org/index.php/Global_Conferences_Committee_Governance). With some minimal tweaking I think we can update the relevant sections to apply across committees. I've taken a stab below (note some of this language was stolen from current by-laws)

Mark.bristow

Committee Missions

  • What is a committee?
  • What is the mission of each Committee?

Jason Li 01:02, 11 March 2011 (EST)

  • Industry Committee would like to change mission statement (as drafted by Joe Bernik) to:

To expand the engagement of OWASP and its mission amongst the public and private sector verticals, through outreach; including presentations, development of position papers and collaborative efforts. The Industry committee serves as the voice of OWASP within the public and private sector and the channel through which OWASP aligns its efforts to the demands of the market.

Thoughts?

Sarah Baso 10:27, 14 March 2011 (EDT)

OWASP Points Program

Mark.bristow

Shared Budget Items

  • Administrative Support?
  • Marketing/Promotion?
  • Committee Summit?

Jason Li 01:02, 11 March 2011 (EST)

Raising Revenue

  • Individual Membership Dues
    • Increase
    • Tiered
  • Corporate Membership Dues
    • Increase
    • Tiered
  • Conference Tickets
    • Increase
    • Tiered
  • Other Revenue Streams?
    • Markup on Lulu printing?
    • Hardcopy software distribution?

Jason Li 01:02, 11 March 2011 (EST)

Cross-Committee Concerns

  • OWASP Conferences Track (Conferences, Projects, Education)
  • OWASP Academies (Chapters, Education)
  • Industry + Connections merger?
  • OWASP Student Chapter (Membership, Chapters, Education)

Jason Li 01:02, 11 March 2011 (EST)

  • Speaker's Sub Committee (education/chapters/conferences)

Kate thinks that before we can consider merging/ending a committee we need to understand what the mission and goal of the committees are. Initial purpose of connections was along the lines of PR and outreach (newsletters, etc) and this is outside the Industry committee. From what I've seen, the Industry committee is actually more in line with Membership as it serves as outreach to corporations to involve them in OWASP. KateHartmann 10:26, 14 March 2011 (EDT)