Chapter Handbook/Chapter 5: Governance - Revision history

Dawnaitken: /* Chapter Bylaws */

2019-07-07T01:17:21Z

‎Chapter Bylaws

Dawnaitken: /* Chapter Elections */

2019-07-07T01:15:16Z

‎Chapter Elections

Dawnaitken: /* Transferring Leadership. */

2019-07-07T01:13:49Z

‎Transferring Leadership.

Dawnaitken: /* Chapter Leadership */

2019-07-07T01:10:34Z

‎Chapter Leadership

Dawnaitken: /* Chapter Leadership */

2019-07-07T01:09:14Z

‎Chapter Leadership

Dawnaitken: /* Chapter Leadership */

2019-07-07T01:07:36Z

‎Chapter Leadership

Tiffany.Long: 2017 update

2017-04-14T23:32:04Z

2017 update

Show changes

Nwhysel: /* Chapter Elections */ grammatical correction

2015-10-19T15:42:49Z

‎Chapter Elections: grammatical correction

Nwhysel: /* Chapter Leadership */ Added definition of an Active Chapter Leader

2015-10-19T15:38:32Z

‎Chapter Leadership: Added definition of an Active Chapter Leader

Nwhysel: /* Disputes */ Removed reference to Global Chapter Committee and added reference to whistleblower policy for suspected ethics violations.

2015-04-21T21:24:03Z

‎Disputes: Removed reference to Global Chapter Committee and added reference to whistleblower policy for suspected ethics violations.

@@ Line 43: / Line 43: @@
 While there is no requirement for Chapters to have their own bylaws or recommended template, if you do create bylaws, you should incorporate the following information as it applies in your country or region:
 ** The Open Web Application Security Project (OWASP) is a not-for-profit worldwide charitable organization focused on improving the security of application software. Our mission is to make application security visible, so that people and organizations can make informed decisions about true application security risks. Everyone is free to participate in OWASP and all of our materials are available under a free and open software license.
-** Reference to the OWASP Foundation Bylaws, the primary governing document for the OWASP, as well as this Handbook. Where there is conflict between chapter bylaws and the Foundation's bylaws or handbook the Foundation’s Bylaws and Handbooks take precedence. Should any Handbook conflict with the Foundation’s Bylaws, the Bylaws take precedence.
+** Reference to the OWASP Foundation Bylaws, the primary governing document for the OWASP, as well as this Handbook. When there is conflict between chapter bylaws and the Foundation's bylaws or handbook the Foundation’s Bylaws and Handbooks take precedence. Should any Handbook conflict with the Foundation’s Bylaws, the Bylaws take precedence.

@@ Line 22: / Line 22: @@
 ==Chapter Elections==
-It is always advisable to avoid elections. Running a chapter is a hard, volunteer job and sharing the load is always advisable. Since the chapter leader role structure is flexible, choosing the a defined  chapter structure (such as a board of leaders who work by consensus) may help to avoid elections. However, if there is a lack of agreement between chapter members on structure, roles or any other issues an election for a role or a poll on any other subject may be required:
+It is always advisable to avoid elections. Running a chapter is a hard, volunteer job and sharing the load is always advisable. Since the chapter leader role structure is flexible, choosing the defined  chapter structure (such as a board of leaders who work by consensus) may help to avoid elections. However, if there is a lack of agreement between chapter members on structure, roles or any other issues an election for a role or a poll on any other subject may be required:
 *A poll on a subject will be held if 10% of the chapter members request it.
 *Elections for a role will be held if there are multiple candidates for a role at the end of the term for the role.

@@ Line 15: / Line 15: @@
 ==Transferring Leadership.==
-In the course of time, a leader may want to move on and leave his/her role. While this chapter provides guidelines to the technical process to follow, we found in the past that the actual challenge is find the new leader, especially in chapters that lack a board. We strongly suggest that a chapter leader who wants to stop would try to find a successor among the active members of the chapter. Such a process has the best chance of ensuring the continuous success of the chapter.
+In the course of time, a leader may want to move on and leave his/her role. While this chapter provides guidelines to the technical process to follow, we found in the past that the actual challenge is finding the new leader, especially in chapters that lack a board. We strongly suggest that a chapter leader who wants to stop would try to find a successor among the active members of the chapter. Such a process has the best chance of ensuring the continuous success of the chapter.
 Please let us know of your wish to leave the job and let us help you in finding a successor.
 When a new leader is to be added to your team or a current leader is leaving you must fill out the change of leadership form to complete the activity.  Chapter leadership is an agreement with the OWASP Foundation to take on responsibilities as well as privileges; records of who is in what role need to be up to date.
 ==Chapter Elections==
 It is always advisable to avoid elections. Running a chapter is a hard, volunteer job and sharing the load is always advisable. Since the chapter leader role structure is flexible, choosing the a defined  chapter structure (such as a board of leaders who work by consensus) may help to avoid elections. However, if there is a lack of agreement between chapter members on structure, roles or any other issues an election for a role or a poll on any other subject may be required:

@@ Line 4: / Line 4: @@
 * Preferably, a chapter should have as many organizers as possible.  Running a successful chapter requires concerted effort all year long, and these duties should be split between whoever is willing to volunteer to take the load. A single chapter leader has proven to be an anti-pattern for successful chapters and high performing chapters often have three or more co-organizers that meet regularly to plan.  In order to promote checks and balances, there are some benefits given explicitly to chapters with multiple leaders.  The most important of these is that every chapter with at least 2 leaders is given access to a minimum starting annual budget of $500.  You can read more about budgets in [[Chapter Handbook/Chapter 4: Chapter Administration|section four]].
-* Chapter Leader (or Coordinator): Every chapter must nominate a Chapter Leader, who is the central point of contact for the chapter and responsible to the OWASP Board.  We suggest (but do not require) that leaders rotate every 24 months to allow for new ideas and to spread the workload. Leadership can be in the form a few people who work by consensus, a leader with an advisory board, or, if you must, a single leader.   In case of dispute over the leader role, your leadership board may rotate over the 24 month term. If there are multiple candidates and no rotation agreement, elections should be held for a 24 months term (see elections below).
+* Chapter Leader (or Coordinator): Every chapter must nominate a Chapter Leader, who is the central point of contact for the chapter and responsible to the OWASP Board.  We suggest (but do not require) that leaders rotate every 24 months to allow for new ideas and to spread the workload. Leadership can be in the form of a few people who work by consensus, a leader with an advisory board, or, if you must, a single leader.   In case of dispute over the leader role, your leadership board may rotate over the 24 month term. If there are multiple candidates and no rotation agreement, elections should be held for a 24 months term (see elections below).
 * Board: Chapters are free to decide on the number of role holders, their titles, how they are selected and for how long. In case there are multiple candidates for a specific role, and no restructuring, rotation or teaming works, elections for the role should be held for a 24 months term.

@@ Line 4: / Line 4: @@
 * Preferably, a chapter should have as many organizers as possible.  Running a successful chapter requires concerted effort all year long, and these duties should be split between whoever is willing to volunteer to take the load. A single chapter leader has proven to be an anti-pattern for successful chapters and high performing chapters often have three or more co-organizers that meet regularly to plan.  In order to promote checks and balances, there are some benefits given explicitly to chapters with multiple leaders.  The most important of these is that every chapter with at least 2 leaders is given access to a minimum starting annual budget of $500.  You can read more about budgets in [[Chapter Handbook/Chapter 4: Chapter Administration|section four]].
-* Chapter Leader (or Coordinator): Every chapter must nominate a Chapter Leader, who is the central point of contact for the chapter and responsible to the OWASP Board.  We suggest (but do not require) that leaders rotate every 24 months to allow for new ideas and to spread the workload. Leadership can be in the form a a few people who work by consensus, a leader with an advisory board, or, if you must, a single leader.   In case of dispute over the leader role, your leadership board may rotate over the 24 month term. If there are multiple candidates and no rotation agreement, elections should be held for a 24 months term (see elections below).
+* Chapter Leader (or Coordinator): Every chapter must nominate a Chapter Leader, who is the central point of contact for the chapter and responsible to the OWASP Board.  We suggest (but do not require) that leaders rotate every 24 months to allow for new ideas and to spread the workload. Leadership can be in the form a few people who work by consensus, a leader with an advisory board, or, if you must, a single leader.   In case of dispute over the leader role, your leadership board may rotate over the 24 month term. If there are multiple candidates and no rotation agreement, elections should be held for a 24 months term (see elections below).
 * Board: Chapters are free to decide on the number of role holders, their titles, how they are selected and for how long. In case there are multiple candidates for a specific role, and no restructuring, rotation or teaming works, elections for the role should be held for a 24 months term.

@@ Line 8: / Line 8: @@
 Chapter leaders serve as the main point of contact for the local chapter, and are responsible for ensuring that the local chapter fulfills its requirements, including planning at least two meetings per year.
-*Preferably, a chapter should have as many organizers as possible. A single chapter leader has proven to be an anti-pattern for successful chapters. Running a successful chapter requires concerted effort all year long, and these duties should be split between whoever is willing to volunteer to take the load. High performing chapters often have three or more co-organizers that meet regularly to plan.
+* An Active Chapter Leader is a leader who is responsive to all requests within a reasonable amount of time, generally within 5-7 business days. Active chapter leaders must have their name and contact information clearly available on the Chapter wiki page.
 *Chapter Leader (or Coordinator): The only governance requirement for every chapter is to nominate a Chapter Leader, who is the central point of contact for the chapter and responsible to the OWASP Board. In case of dispute over the leader role, we suggest rotation over the 24 month term, if there are multiple candidates and no rotation agreement, elections should be held for a 24 months term (see elections below).
 *Board: Chapters are free to decide on the number of role holders, their titles, how they are selected and for how long. We recommend that a chapter would have also a board with at least 3 members, each one having a specific role. Common roles:

@@ Line 57: / Line 57: @@
 If you feel that a chapter leader is not acting in accordance with the chapter handbook, please follow the following hierarchy in escalating your concern:
 # Bring your concern to the attention of the chapter leader or chapter board. If possible, make an attempt to handle the issue locally.
-# If you are unable to resolve at the local level, please contact the [[Global Chapter Committee]] (or through the [http://sl.owasp.org/contactus contact us form]).
+# If you are unable to resolve at the local level, please contact the Community Manager (through the [http://sl.owasp.org/contactus contact us form]).
-#If the Global Chapter Committee is not able to handle your concern or you would like to challenge the feedback/decision of the Committee, the concern can be raised with the Global OWASP Board.
+#If the Community Manager is not able to handle your concern or you would like to challenge the feedback/decision of the Community Manager, the concern can be raised with the Global OWASP Board.
 [[Category:Chapter_Handbook]]