Regional chapter policy #118
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kingthorin
reviewed
Oct 24, 2022
kingthorin
reviewed
Oct 24, 2022
kingthorin
reviewed
Oct 24, 2022
kingthorin
reviewed
Oct 24, 2022
kingthorin
reviewed
Oct 24, 2022
|
I only got part way through reading it earlier. The title caps thing probably applies throughout, and I think the reason I mentioned the periods was that there were earlier occurrences where they were missing. I'll try to get through the rest of the doc this evening. |
kingthorin
reviewed
Oct 25, 2022
| - Requests from OWASP staff, such as expense claims, should be responded to by one or more of the chapter leaders within 9 business days. | ||
| - Leaders are encouraged, but not required, to monitor and participate in the [OWASP Leaders List](https://groups.google.com/u/1/a/owasp.org/g/leaders), other Google groups, and the Slack platform. | ||
| - OWASP chapters can create and manage their own social media presence and other reasonable communication channels. Access to these accounts must be shared with all leaders of the chapter. Administration of the account should be handed over to a remaining chapter leader when stepping down. | ||
| ### Regional chapters |
|
|
||
| OWASP Foundation will provide chapters with the following shared services at no cost. Chapters are encouraged to make use of these. Access to these services can be obtained by submitting a ticket via [Contact Us](https://contact.owasp.org/). If, after 9 business days have passed, and reasonable efforts have been made to attempt to utilize shared services, no response is received, the chapter may, with due care, seek a reasonable alternative, filling out a [Chapter Funding Pre-Approval](https://owasporg.atlassian.net/servicedesk/customer/portal/8/group/20/create/107) ticket. | ||
| Regional chapter names MUST NOT conflict or likely to create confusion with other OWASP entities, events, committees, chapters, and so on. |
There was a problem hiding this comment.
Suggested change
| Regional chapter names MUST NOT conflict or likely to create confusion with other OWASP entities, events, committees, chapters, and so on. | |
| Regional chapter names MUST NOT conflict or be likely to create confusion with other OWASP entities, events, committees, chapters, and so on. |
|
|
||
| Services identical or like those provided by the foundation cannot be expensed without [prior approval](https://owasporg.atlassian.net/servicedesk/customer/portal/8/group/20/create/107). Where possible, all chapters are encouraged to use a service that respects user privacy. | ||
| ### Naming precedence |
|
|
||
| ### Starting a Student Chapter | ||
| If an academic institution has membership, campus access, or leadership restrictions or additional requirements that contravenes open access, Student chapters MAY apply in writing to the Chapters Committee for an exemption by explaining the restrictions in full. |
There was a problem hiding this comment.
Suggested change
| If an academic institution has membership, campus access, or leadership restrictions or additional requirements that contravenes open access, Student chapters MAY apply in writing to the Chapters Committee for an exemption by explaining the restrictions in full. | |
| If an academic institution has membership, campus access, leadership restrictions, or additional requirements that contravene open access, Student chapters MAY apply in writing to the Chapters Committee for an exemption by explaining the restrictions in full. |
|
|
||
| ### Regional Chapters | ||
| Chapter leaders SHOULD be present in the country of their chapter. Regional chapters leaders MUST reside within the region. |
There was a problem hiding this comment.
Suggested change
| Chapter leaders SHOULD be present in the country of their chapter. Regional chapters leaders MUST reside within the region. | |
| Chapter leaders SHOULD be present in the country of their chapter. Regional chapter leaders MUST reside within the region. |
|
|
||
| ### Deactivation or Dissolution of New or Re-activating Chapters | ||
|
|
||
| Chapters that fail to meet Chapter startup or reactivation requirements will be: |
There was a problem hiding this comment.
This lead-in doesn't really jive with the bullets. It could be dropped or re-worded.
| - New chapters will be dissolved after 90 days if no activity is held | ||
| - Reactivating chapters will be deactivated after 30 days if the chapter page is not updated and an initial activity scheduled. If the reactivation plan is not completed after the first 90 days, the chapter will be deactivated. | ||
|
|
||
| As a first step, the OWASP Foundation MAY deactivate chapters where the chapter has failed to meet chapter policy, including chapter startup and activity requirements. |
There was a problem hiding this comment.
Suggested change
| As a first step, the OWASP Foundation MAY deactivate chapters where the chapter has failed to meet chapter policy, including chapter startup and activity requirements. | |
| As a first step, the OWASP Foundation MAY deactivate chapters where the chapter has failed to meet chapter policy, including chapter startup, and activity requirements. |
|
|
||
| ## Governance | ||
|
|
||
| The OWASP Foundation is a US-based 501 (c)(3) non-profit membership organization. OWASP MUST follow specific financial and legal guidelines or IRS compliance requirements that can change from time to time, which governs how chapters and chapters MUST operate. |
There was a problem hiding this comment.
Suggested change
| The OWASP Foundation is a US-based 501 (c)(3) non-profit membership organization. OWASP MUST follow specific financial and legal guidelines or IRS compliance requirements that can change from time to time, which governs how chapters and chapters MUST operate. | |
| The OWASP Foundation is a US-based 501 (c)(3) non-profit membership organization. OWASP MUST follow specific financial and legal guidelines or IRS compliance requirements that can change from time to time, which governs how chapters MUST operate. |
|
|
||
| Leaders MUST abide by the latest approved [Code of Conduct](https://owasp.org/www-policy/operational/code-of-conduct). | ||
|
|
||
| During activities, the latest approved [Conference and Event Anti Harassment Policy]( https://owasp.org/www-policy/operational/conferences-events#conference-and-event-anti-harassment-policy) applies. |
There was a problem hiding this comment.
Suggested change
| During activities, the latest approved [Conference and Event Anti Harassment Policy]( https://owasp.org/www-policy/operational/conferences-events#conference-and-event-anti-harassment-policy) applies. | |
| During activities, the latest approved [Conference and Event Anti-Harassment Policy]( https://owasp.org/www-policy/operational/conferences-events#conference-and-event-anti-harassment-policy) apply. |
|
|
||
| OWASP must comply with international laws and regulations, including international sanctions. Sanctions take many forms and are often limited in scope to access to specific intellectual property, organizations, governments, and/or individuals. | ||
| If the issue is remains unresolved, or is escalated by the OWASP Foundation, the Chapter Committee SHALL ask to meet all concerned at a future Chapter Committee activities, and a final decision reached. |
There was a problem hiding this comment.
Suggested change
| If the issue is remains unresolved, or is escalated by the OWASP Foundation, the Chapter Committee SHALL ask to meet all concerned at a future Chapter Committee activities, and a final decision reached. | |
| If the issue is remains unresolved, or is escalated by the OWASP Foundation, the Chapter Committee SHALL ask to meet all concerned at a future Chapter Committee activity, and a final decision reached. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.