Skip to content

Add "High Level Summary" to PAEP 1 #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
elena wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add "High Level Summary" to PAEP 1 #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion paep-1-purpose/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,15 @@ Each PAEP will be designated a positive integer number in consecutive order, per

Discussing the PAEP process at PyCon Australian 2025 made it clear that some level of consensus on
how to pronounce "PAEP" would be helpful. The suggested pronunciation is "pay-ep", but we're mostly
Australians, so it's inevitable it will frequently be shortened to the single syllable "pape".
Australians, so it's inevitable it will frequently be shortened to the single syllable "pape"/"payp".

# When is a formal process needed?

**High Level Summary**:

* PAEPs exist to allow both: things to get done AND having informed consensus
* only large/controversial efforts need to be PAEPs, smaller things can just be Issues

Many decisions relating to Python Australia may be made without needing a formal PAEP or approval
vote. For example, if someone wants to talk at their local user group about the efforts
that are being made to establish Python Australia and some of the hoped for benefits of getting
Expand Down