Submission

Only organization (non-user) accounts have access to the grant application form.

Applications for paid organizations receive priority in the reviewing queue. This is both to offer a meaningful benefit to paid organizations and to ensure that funding is available for PyPI’s operational costs, including more reviewers.

Approval Criteria

1. The namespace must not be something common like tool or apps.
2. The namespace should be greater than three characters.
3. The namespace should properly and clearly identify the reservation owner.
4. The organization should be actively using the namespace.
5. There should be evidence that not reserving the namespace may cause ambiguity, confusion, or other harm to the community.

Organizations that are not paid organizations will represent one of the following:

• Large, popular open-source projects with many packages
• Universities that actively publish packages
• Government organizations that actively publish packages
• NPOs/NGOs that actively publish packages like Our World in Data

Generally speaking, reviewers should be more tolerant of paid organizations that apply for grants for which they are not yet using.

For example, while it’s reasonable to grant a namespace to a startup or an existing company with a new product line, it’s not as reasonable to grant a namespace to a community project that doesn’t have many users.

Rejections

Rejected applications will receive clear rationale for the decision based on the approval criteria. Applications rejected due to the namespace being too common will be persisted internally for future reviewers to reference and new applications attempting to reserve a namespace that was previously rejected for that reason will display a warning.

Acceptance

When an application is accepted for a namespace that is used by projects outside of the organization, an email will be sent to the owners of the projects notifying them of the new grant. The email will contain a link to the namespace’s page.

Root Grant

An organization gets a root grant for every approved application. This grant may produce any number of child grants.

Child Grant

A child grant may be created by the owner of a root grant at any time without approval. The namespace associated with such grants must be a child namespace of the root grant’s namespace.

Child grants cannot have their own child grants.

Namespace Page

The namespace of every active grant will have its own page that has information such as its open status, the current owners, the time at which ownership was granted and the total number of projects that match the namespace.

Project Page

Every project’s page (example) that matches an active namespace grant will indicate what the prefix is (NuGet currently does not do this) and will stand out as a pill or label. This value will match the prefix key in the namespace detail API.

Clicking on the namespace will take the user to its page.

Visual Indicators

For projects that match an active namespace grant, users will be able to quickly ascertain which of the following scenarios apply:

1. Projects that are tied to a grant owner will not have a visual indicator and users should solely rely on the always-present prefix.
2. Projects that are not tied to a grant owner and the matching grant is open will have a unique indicator that does not convey mistrust or danger. A good choice might be the users icon from Font Awesome or the groups icon from Google Fonts.
3. Projects that are not tied to a grant owner and the matching grant is restricted will have a unique visual indicator. This situation arises when the project existed before the grant was created. The indicator will convey inauthenticity or lack of trust. A good choice might be a warning sign (⚠).