Merge pull request #156 from activus-d/policies

Documentation: Align the policies docs with the style guide

Author: activus-d

policies/discord/where-to-talk.md

@@ -1,54 +1,53 @@
-# The Best Place to Chat in the Discord...
+# The best place to chat in Discord
 
-We get asked often "Where is the best place to talk about..."
+People often ask: “Where’s the best place to talk about…?”
 
-We've been trying to figure this out ourselves and currently our policy is _the community will figure it out and we will do our best to support it_.
+We’ve been asking the same thing. Right now, our answer is simple: _the community figures it out, and we support what works_.
 
-Okay but what does that mean...
+So what does that mean? It means there’s no perfect answer. Is GitHub a good place? The answer to this depends on what you want to do. GitHub is where issues and PR updates show up. It helps reduce noise and keeps people informed.
 
-This means that there isn't really a wrong answer. Is `#github` the best place to have that discussion, kinda yes and no.  The `#github` channel was actually where issues and PR updates are relayed to the community. This is in part to reduce the number of places to check but also so people can see new issues. 
+That said, we also have a `#contributors-wanted` channel in Discord. The channel is for sharing projects that need help.
 
-That said we also have `#contributors-wanted` where maintainers can share open source projects that are looking for maintainers. But until writing this I totally forgot that it existed and I've been putting things in `#general`. 
+## Start in `#general` when in doubt
 
-## When in doubt start in `#general`
+The `#general` channel in Discord is the home for all kinds of conversation. You can share your excitement, ask a question, bring up a community topic—it all fits.
 
-General is meant to be the home for all kinds of conversation. Whether you're excited about a new event or meetup or something in the community is happening and you want our opinion about it.
+Not sure where something belongs? Start in `#general`. Our rule is that you _won't be yelled at for putting something in `#general`_.
 
-If you don't know where something should go, our rule is you _usually won't be yelled at for putting something in `#general`_.
+This means that a lot of the conversation happens in `#general`. So, we encourage you to have conversations in the channel.
 
-Obviously, this means that a lot of conversation should be happening in `#general` (we encourage you to have conversations.)
+## When is `#general` not okay?
 
-This is where discords technology should be used.
+Two things don’t belong in #general:
 
-- If you want to have a conversation on a message start a thread.
-- If you want something to have a longer discussion on it, use the `community-discussion`
-- If it's related to a conversation happening in a channel or to a specific group, then link and continue the conversation in the channel. 
-- If you think a channel should be created for it, simply ask `@mods` or `@BPDLeaders`. The worst they will say is either "No" or "That exists already". In many cases they'll just make the channel.
+- direct solicitation
+- aggressive self-promotion
 
-## When is `#general` not okay
+### No direct soliciting
 
-The only thing that is generally not okay is solicitation or **aggresive** self-promotion.
+We care about a lot of projects. Black Python Devs is a US non-profit. This means that a part of what we do is raise money. So we do our best to keep fundraising efforts internal to the community at an absolute minimum. This is because we don't want the community to feel like a place where you are constantly being asked for money. We will only share campaigns we're doing once they launch and **how folks can share the campaign**. There is no expectation for anyone to pay for being in _Black Python Devs_ or taking part in Black Python Devs events on the Discord.
 
-### No Direct Soliciting
+That message gets skewed when members come and ask for money. Not everyone is in a position where being asked for money is something they can easily say "Yes" or "No". That kind of pressure can make people uncomfortable in the community.
 
-There are a lot of projects that we all care about. Black Python Devs is a US Non-Profit. This means that a part of what we do is raise money. That being, said we do our best to keep fundraising efforts internally to the community at an absolute minimum. This is because we truly don't want the community to feel like a place where you are constantly being asked for money. In fact, we will only share campaigns we're doing once they launch and **how folks can share the campaign**. There is no expectation that anyone pay for being in _Black Python Devs_ or taking part of Black Python Devs events in the Discord.
+### Aggressive self promotion
 
-That message gets skewed when members come and ask for money. Not everyone is in a position where being asked for money is something they can easily say "Yes" or "No". Whether the reasons are financial or cultural that pressure can cause people to not feel comfortable in the community.
+If you wrote something that you're excited about or you've hit an amazing milestone in your career, we want you to share that excitement with us. `#general` can be a great place for it.
 
-### Aggressive Self Promotion
+If you're on a content grind, this is not your a place for you. 
 
-If you wrote something that you're excited about or you've hit an amazing milestone in your career, we want you to share that excitement with us. `#general` can be a great place for it. 
+We understand that people join the community for different reasons, but **_it's not our job to make anyone famous_**. Our goal is to make the Python community a place where all  Black Pythonistas of all skill levels don't simply belong, but lead and thrive. This means that everyone should feel welcome to chat. So the BPD community is not the place to build your clout.
 
-If you're on your #content-grind. This is not your channel. 
+## Posting of unpaid Jobs
 
-We understand that people join the community for different reasons. I've said this before and I'll stand on it. 
+Please don't post unpaid positions in any of our Discord channels. While internships are welcome, we prohibit posting positions offering equity-only compensation.
 
-> Our job is to not make anyone _famous_. 
- 
-Our goal here is to make the Python Community a place where all  Black Pythonistas of all skill-levels don't simply belong, but lead and thrive. This means that everyone should feel welcome to chat and be encouraged that we are not only for celebrities. So if you came here to build your clout, it's not going to be the best place for that.
+This is because equity-based compensation can be problematic. While it has the potential for significant rewards if the startup succeeds, it often involves working without guaranteed future pay. The arrangement may suit certain stages of life, but it's generally inappropriate for most people in our community, who seek paid opportunities.
 
-## Posting of Unpaid Jobs
+## Using our Discord channels
 
-Please do not post unpaid positions in any of our Discord channels. While internships are welcome, we prohibit posting positions offering equity-only compensation.
+You can use our Discord in the following manner:
 
-This is because equity-based compensation can be problematic. While it has the potential for significant rewards if the startup succeeds, it often involves working without guaranteed future pay. The arrangement may suit certain stages of life, but it's generally inappropriate for most people in our community, who seek paid opportunities.
+- If you want to have a message-like conversation, start a thread.
+- If you want to have a longer discussion, use the `community-discussion` channel.
+- If it's related to a conversation happening in a channel or to a specific group, then link and continue the conversation in the channel. 
+- If you think a channel should be created for it, ask `@mods` or `@BPDLeaders`. The worst they will say is either "No" or "That exists already". In most cases, they'll just make the channel.

policies/event-grants.md

@@ -1,5 +1,5 @@
 ---
-title: Grants Policy Document
+title: Grants policy document
 author: Jay Miller
 date-created: 19 Jan 2025
 last-updated: 21 Apr 2025
@@ -8,50 +8,49 @@ last-updated: 21 Apr 2025
 ## 1. Purpose
 The purpose of this grants policy is to provide a structured approach to sponsoring events while maintaining financial sustainability for our organization.
 
-## 2. Grant Budget Allocation
+## 2. Grant budget allocation
 
-### 2.1 Annual Budget Cap
+### 2.1 Annual budget cap
 
-- Current Grant Budget (2025): $2,000
-- Rationale: Designed to support event sponsorships for up to three years at the same level.
+- Current grant budget (2025): $2,000
+- Rationale: Designed to support event sponsorships for up to three years at the same level
 
-### 2.2 Budget Considerations
+### 2.2 Budget considerations
 
-- Derived from analysis of donation patterns
-- Subject to annual review and potential mid-year adjustment
+- derived from analysis of donation patterns
+- subject to annual review and potential mid-year adjustment
 
-## 3. Future Outlook
+## 3. Future outlook
 
-- Commitment to increasing grant support as donation base grows
-- Ongoing evaluation of financial capacity
+- commitment to increasing grant support as donation base grows
+- ongoing evaluation of financial capacity
 
-## 4. Financial Principles
+## 4. Financial principles
 
-- Maintain organizational financial stability
-- Prevent overcommitment of resources
-- Ensure ability to support events consistently
+- maintain organizational financial stability
+- prevent overcommitment of resources
+- ensure ability to support events consistently
 
-## 5. Review and Adjustment
+## 5. Review and adjustment
 
-- Annual review of grant allocation
-- Reassessment based on Donation income
+- annual review of grant allocation
+- reassessment based on donation income
 
-## 6. Application Process
-  
-  Apply for an BPD Event grant by emailing [email protected] **at least 6 weeks prior** to the event.
-  
-  Include in your request:
+## 6. Application process
+
+Apply for a BPD Event grant by emailing `[email protected]` **at least 6 weeks prior** to the event.
 
-    - Event Prospectus (if available)
-    - Requested amount
-    - Expected number of participants
-    - What the grant would go towards
-    
+Include the following in your request:
+
+- event Prospectus (if available)
+- requested amount
+- expected number of participants
+- purpose of the grant
+
 ## 7. Disclaimer
 
-  The grant budget is subject to change based on the organization's financial capabilities and donation levels.
+The grant budget is subject to change based on the organization's financial capabilities and donation levels.
 
 ## 8. Changelog
 
 21 Apr 2025 - Updated syntax and added a 6 week prior notification deadline - Jay Miller
-

policies/onboarding.md

@@ -1,7 +1,7 @@
-# Onboarding New Black Python Dev Leadership
+# Onboarding new Black Python Dev leadership
 
-### Things to Do
+### Things to do
 
-- Assign the BPD Leaders Role
-- Ensure they are added to the `#leadership` channel
-- Add GitHub account to the organization leadership channel
+- assign the BPD leaders Role
+- ensure they are added to the `#leadership` channel
+- add GitHub account to the organization leadership channel

policies/paying-for-things-and-getting-reimbursed.md

@@ -1,18 +1,18 @@
-# Paying for Things and Seeking Reimbursement
+# Paying for things and seeking reimbursement
 
 When spending money on behalf of Black Python Devs, ensure that all expenses are approved in writing and properly documented.
 
-Also, you should send a quote for the expenses to the email address _[email protected]_, _[email protected]_, or the organizing team's email address.
+Also, send a quote for the expenses to the email address _[email protected]_, _[email protected]_, or the organizing team's email address.
 
-## Authorized Purchase Approvers
+## Authorized purchase approvers
 
 The following roles have the authority to approve purchases:
 
-* Global Executor (Chairman)
-* Regional-Executor
+* Global Executor
+* Regional executor
 * Treasurer
 
-## Authorized Request Types
+## Authorized request types
 
 All purchases must be for the official business of Black Python Devs. Approved purchase examples include the following:
 
@@ -21,11 +21,11 @@ All purchases must be for the official business of Black Python Devs. Approved p
 * paying for a meal for everyone in a Black Python Devs Event (requires pre-approval) **Meetup pizza, Thai, Ice cream**
 * swag, booth Materials
 
-## How Payment is Handled
+## How payment is handled
 
-### Black Python Devs Pays Directly
+### Direct payment
 
-This is the preferred method. You can request an invoice to be paid by Black Python Devs. This is great when payment can be handled via wire transfer.
+Direct payment is the preferred method. You can request an invoice to be paid by Black Python Devs. This is great when payment can be handled via wire transfer.
 
 All wire transfers require the following information:
 
@@ -35,8 +35,8 @@ All wire transfers require the following information:
 * SWIFT code of their bank (if applicable)
 * currency of their account
 
-### Member Pays and is Reimbursed
+### Member pays and is reimbursed
 
 Ensure you get approval before paying out of pocket.
 
-If you've been approved for an out-of-pocket purchase, you need to request a copy of the reimbursement form from _treasury@blackpythondevs.com_. Fill out the form and send it to _accounting@gnome.org_ and cc _leadership@blackpythondevs.com_. 
+If you've been approved for an out-of-pocket purchase, you need to request a copy of the reimbursement form from `treasury@blackpythondevs.com`. Fill out the form and send it to `accounting@gnome.org` and cc `leadership@blackpythondevs.com`. 

policies/standards_of_content.md

@@ -1,4 +1,4 @@
-# Standards of Content
+# Standards of content
 
 ## Making changes to this document
 
@@ -12,11 +12,11 @@ This document is meant to be a guideline for content that is created on behalf o
 
 This pertains to written as well as audio and video content.
 
-## Content is not mean to be hateful, but not afraid to address difficult topics
+## Content is not meant to be hateful, but not afraid to address difficult topics
 
-It is a reality that the lives of Black people around the world is in many cases elevated based on current events.
+It is a reality that the lives of Black people around the world are, in many cases, elevated based on current events.
 
-Black, Colored/Coloured developers are not able to minimize their blackness in the eyes of the world and therefore we invite our platform to share those experiences from time-to-time.
+Black, colored developers are unable to minimize their blackness in the eyes of the world, therefore, we invite our platform to share those experiences from time-to-time.
 
 Our content is held to the same Code of Conduct and is subject to review by our leadership. 
 
@@ -26,10 +26,10 @@ We want to ensure that our content is readable, but doesn't take away from the m
 
 We ask that cultural references be documented so that others can learn and enjoy with the same context.
 
-## _Own your masters_ approach to signal amplification
+## Own your masters approach to signal amplification
 
 One of our core foundations is to _own your masters_. This references the ability to control how your content is distributed.
 
 Black Python Devs wants to be an amplifier, but not an owner of your content. We'll only ask that you contribute content if it directly relates to Black Python Devs. Any time that we promote your content, it should always link to your original source.
 
-Lastly, any content that you do create on behalf of Black Python Devs, we will give you the rights to have removed at your request.
+Lastly, for all content you create on behalf of Black Python Devs, you have the right to request its removal.

policies/supporters_reporting.md

@@ -1,28 +1,28 @@
 ---
-name: Supporters Reporting
+name: Supporters reporting
 created: 1 Jan 2025
 updated: 1 Jan 2025
 created_by: Jay Miller
 last_updated_by: Jay Miller
 ---
 
-# Record of Supporters
+# Record of supporters
 
 We keep an annual record of our supporters to track their contributions over time. To protect their privacy, we only share their names in public.
 
-## Updating or Removing Supporter Information
+## Updating or removing supporter information
 
-You can request updates or removal of your name from our public records by sending a written request via email to **[email protected]**.
+You can request updates or removal of your name from our public records by sending a written request via email to `[email protected]`.
 
 However, since we manage these records using version control, we cannot completely delete all information. So if you prefer not to have your name appear in our public records, please mark it as `anonymous` at the time of your donation.
 
 We use [CommitChange](https://commitchange.com) for record-keeping. While we can update information in `CommitChange`, we cannot remove it entirely.
 
-## Adding a Name to the List of Supporters
+## Adding a name to the list of supporters
 
 The supporters’ list is annually updated using the end-of-year export feature in `CommitChange`.
 
-## Foundational Supporters
+## Foundational supporters
 
 Donors who contribute over $200 in a calendar year will be recognized as Foundational Supporters, and their names will be featured on our website. This information is updated monthly through our payment processor, `CommitChange`.