Code of Conduct

Content & IP Rights · Permission or license

Repository owners may remove or edit contributions, edit or hide comments, and tag content NFAA

Under the heading 'Enforcement Responsibilities', the Code says repository owners have the right to remove, edit or reject commits and pull requests; edit discussion titles and community comments; hide community comments; and tag content as 'Not For All Audiences' (NFAA). So if you contribute to or comment on someone else's repository, its owner can change, hide or reject what you posted. The Code frames these as owners' rights; it does not say owners must use them or set rules for how they decide.

Supporting quotations

Enforcement Responsibilities

Repository owners have the right to:

Remove, edit, or reject commits and pull requests;

Edit discussion titles and community comments;

Hide community comments;

Tag content as "Not For All Audiences" (NFAA);

Qualifications & exceptions

• These are rights of repository owners over their own repositories.
• The Code does not require owners to use these tools or give contributors notice.

Not stated here

• The document does not say whether contributors can challenge an owner's removal, edit or hiding of their contribution.
• Actions Hugging Face itself may take against violators are not described in this document.

Content & IP Rights · Permission or license

Repository owners may gate access for manual approval or make repositories private

Repository owners also have the right to gate access to their repositories, which lets them manually review and approve or reject requests for access to their ML artifacts, and to make repositories private so only the owner or members of their organization can access them. For other users, this means access to a gated repository depends on the owner's approval, and a repository can become private.

Supporting quotations

Repository owners have the right to:

Gate access to repositories, allowing owners to manually review and approve/reject access to their ML artifacts;

Make repositories private, restricting access to only the owner or members of their organization.

Qualifications & exceptions

• Gating means the owner manually reviews and approves or rejects access.
• A private repository is limited to the owner or members of their organization.

Not stated here

• The document does not say what information an owner sees when reviewing an access request.