Talk:Chapter Handbook/Chapter 4: Chapter Administration
Suggested edits are located on the Talk/Discussion pages of each chapter of the Chapter Leader Handbook. For each comment or suggested edit that you would like to add, please create a bullet point under my signature, add your comment, then sign your name by adding four tildes (~) in a row and then click save. The four tildes will automatically be replaced with your name and time stamp when you save.
- 1 4.1 OWASP Email Addresses
- 2 4.2: OWASP Wiki
- 3 4.3 Local Domain Names
- 4 4.4: Mailing Lists
- 5 4.4.5: New Section OWASP Event Calendar
- 6 4.5: Social Media
- 7 4.6: Organizing Your Contacts
- 8 4.7: Handling Money
- 9 4.7.1: Spending Guidelines
- 10 4.7.2: Additional Expense Policies
- 11 4.7.3: Reimbursement Process
- 12 4.7.4: Chapter Budget
- 13 4.7.5: Money Not Tracked by the Foundation
- 14 4.8: Charging for Events
- 15 4.10 Signing Contracts
4.1 OWASP Email Addresses
Add "and project leaders"
The rest is specific to chapter leaders. Project leader handbook needs to expand info on OWASP.org emails.
4.2: OWASP Wiki
Last bullet: Other promotional services such as LinkedIn, Facebook, Twitter, Ning, Meetup, etc. are fine to inform people about your local chapter and its activities; however, the OWASP Chapter Wiki Page should be the authoritative information at all times.
This bullet should be a separate paragraph, not a sub bullet under what to post on the wiki. Include Ning and other platforms mentioned above.
4.3 Local Domain Names
Should we add a note about contacting Foundation staff to approve external websites? CJK and right to left languages could be a problem for our wiki that is resolved by using a different CMS, rather than just pointing the domain to the global website. This is an exception that requires approval. China and Korea are examples of external websites.
I also suggest adding if an exception is permitted that every effort be made to inform the Foundation about changes to leadership and upcoming meetings so that the global site information is up to date.
Resolution: Add the following text to the paragraph about China and Korean websites:
"If an exception is permitted, every effort must be made to announce changes to leadership and upcoming meetings on the chapter wiki page so that the global site information is up to date."
We still have an outstanding question about chapters such as that are using external websites with noncompliant branding. This needs to be addressed.
4.4: Mailing Lists
Job Board On wiki has been removed and replaced functionally with the LinkedIn job discussion board. The jobs link is no longer available on the home page.
Edit suggestion: reference LinkedIn job board. Possibly add a link to home page.
4.4.5: New Section OWASP Event Calendar
Add a section 4.5 on the event calendar and renumber the sections.
Posting to the calendar is simple. Log into http://calendar.google.com with your OWASP.org account. Confirm that you can view the OWASP Event Calendar. It will show up in the left column. When you create the event, be sure to select "OWASP Event Calendar" as the calendar to post it on. Then save.
4.5: Social Media
Suggested addition: "Conversely, since the chapter page on the OWASP wiki is the official representation of the chapter, communication on social media platforms should complement, not replace the wiki page. Do keep any new event or activity announcements up to date on the wiki page, per section 4.2."
The Governance/Social Media Policy states:
"Administration and Ownership of OWASP Social Media Accounts: Any person with access to an OWASP social media account must sign a document agreeing to the terms of this policy, acknowledging that OWASP owns the account and may at any time transition usage and control of the account. This will allow the Foundation to quickly establish ownership in the case of a dispute or other circumstance."
According to this, we can reclaim any OWASP branded social media site, but it says that leaders need to sign an agreement before they can set one up. I don't believe anyone actually does this, and it would be extremely hard to enforce. In fact the only requirement we have asked so far has been for prospective leaders to acknowledge that they read and understood the chapter leader handbook. There is a section in the handbook on social media but it does not mention an agreement. I suggest adding a link to the policy and changing the policy to read that it is understood, not that they have to sign an agreement every time they open a new social media account.
4.6: Organizing Your Contacts
Add a reminder to abide by confidentiality rules. Member lists may not be distributed outside of chapter leadership.
Should we also state that member lists can be distributed to chapter members for networking purposes as long as individual members opt in?
4.7: Handling Money
Remove reference to Global Chapter Committee. Who should be the contact for the treasurer information? Community Manager? ED? Accountant? or Community 2.0 leadership?
Add information about the new funding rules and edit text accordingly.
4.7.1: Spending Guidelines
Add link to the Donation Scorecard so leaders can look up their current allocation. Replace Global Chapters Committee with Community Manager.
4.7.2: Additional Expense Policies
Does anyone actually publish exceptions to their expense policies to the wiki?
4.7.3: Reimbursement Process
Change "Get advise from the Global Chapter Committee" to "get advice from the Community Manager."
4.7.4: Chapter Budget
We need a description of the purpose and process for chapter budgets. This is just a link to the template.
4.7.5: Money Not Tracked by the Foundation
Suggested: To avoid appearance of impropriety, forward all potential donors to the Donate button on your chapter wiki page or to approved third party processors.
4.8: Charging for Events
Change reference to Global Conferences Committee to Global Foundation.
Remove: Should you feel that your event should be managed by the Global Chapter Committee instead of the Global Conferences Committee please submit an email to the chairs of both the Chapters and Conferences Committees with your rationale for consideration of an exception.
4.10 Signing Contracts
Add: All contracts must be submitted for approval and signature by authorized OWASP Foundation staff.