Skip to content
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

PEP 752: Add terminology section #3918

Merged
merged 2 commits into from
Aug 21, 2024
Merged

PEP 752: Add terminology section #3918

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a3789e7
PEP 752: Add terminology section
ofek Aug 21, 2024
adb0a66
fix
ofek Aug 21, 2024
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
20 changes: 20 additions & 0 deletions peps/pep-0752.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,26 @@ specific scenarios) provides the following benefits:
feedback would be required because the process to approve a paid organization
already bestows a certain amount of trust.

Terminology
===========

The keywords "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as
described in :rfc:`2119`.

Organization
`Organizations <orgs_>` are entities that own projects and have various
users associated with them. Only organizations have access to the namespace
application form.
Corporate Organization
`Corporate organizations <corp-orgs_>` are organizations that have paid for
special functionality on PyPI.
Public Namespace
A `public <public-namespaces_>`_ namespace allows for uploads from any
project owner.
Private Namespace
A private namespace only allows uploads from an owner of the namespace.

Specification
=============

Expand Down