Please also review the Outpost Code of Conduct for a general overview of our community standards and expectations.
Last updated: August 7, 2024
Outpost's primary aim is to assist the Community in promoting Open, Collaborative, and Responsible Machine Learning. The achievements of Outpost are largely due to the incredible Community on our Platform.
We value these relationships and strive to maintain an environment where individuals feel welcome, supported, and able to make the most of their contributions and experiences. Thus, we have established the following Content Guidelines and Policy (these "Guidelines") for our Platform and its Users.
These Guidelines outline Outpost's efforts to protect our Community. Our objective is to enable the Community to identify and flag types of Content that pose a higher risk of harm, so we can give such Content additional scrutiny as detailed in the following Guidelines.
Please read these Guidelines carefully, as they contain essential information about the types of Content permitted on our Platform.
These Guidelines are incorporated into our Terms of Service, forming a binding agreement between us and you. You should also review our other guidelines, policies, and documents available on our Website, including our Terms of Service and Privacy Policy.
By accessing or using our Platform, you agree to these Guidelines and all other policies and terms. If you do not agree with any of these, please do not use our Platform.
We may update these Guidelines periodically. Changes will become effective 10 days after posting the updated Guidelines on the Website. Continuing to use our Platform after this period signifies acceptance of the changes.
Capitalized terms not defined herein shall have the meanings assigned to them in our Terms of Service, Privacy Policy, and all other policies available on our Website.
Content types may include:
"ML Artifacts": Code and assets hosted in Outpost's Repositories, including Models, Datasets, Spaces;
"Community Content": Content found in the Community section of the Outpost Platform, including discussions, comments, usernames, and related documentation such as READMEs, model cards, data cards, pull requests, and merges.
"Community" encompasses all Users of the Outpost Platform, including Outpost personnel.
"Community Tab" is a collaborative feature for discussing specific Repositories, providing feedback, brainstorming ideas, and opening pull requests for improvements.
"Outpost" refers to Outpost Inc., including its affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees.
"Platform" or "Outpost Hub," or "Hub," refers to the hosting platform where Users can build, benchmark, share, version, and deploy Repositories, which may include Models, Datasets, and Machine Learning Applications.
"Repository" is a data structure containing all project files and the entire revision history. Repositories may be:
"Repository Label" refers to a label assigned to a Repository, such as:
"Team" or "Outpost Team" refers to Outpost personnel.
These Guidelines address two categories of Content:
Restricted Content: Inappropriate for the Platform and subject to removal and further consequences based on severity. This Content is detailed in the Restricted Content section and will be handled directly by the Outpost Team.
Moderated Content: Requires an iterative approach to determine appropriate hosting conditions. This Content is detailed in the Moderated Content section and will be addressed in collaboration with the Repository owner and concerned parties, fostering communication and potential improvements to the Repository's code and documentation. We focus on the origin of the ML artifact, its handling by developers, and its usage.
The following Content is prohibited on our Platform:
Content not listed but requiring attention will be addressed on a case-by-case basis.
Additionally, if personal information of individuals under 13 is collected without parental consent, we will remove this data from our Platform (see §7 of our Privacy Policy).
Moderated Content requires extra scrutiny and a collaborative iterative approach to classify and respond accordingly. This includes Content with a higher risk of harm, such as Content with dual-use potential or uncertain legal status. Community-reported Content triggers the moderation process.
Consent is a core value in this process, supporting forethought and empathy toward stakeholders and proactive measures addressing cultural and contextual factors.
We prioritize collaborative solutions for ML Artifacts and Community Content, involving Repository owners to ensure modifications or additional guardrails meet Guidelines.
When Content is reported, the Repository owner typically has 72 hours to respond. Non-engagement or other circumstances may lead to unilateral actions by the Outpost Team. Two levels of intervention are identified:
A. Community features: To reduce problematic outcomes, we may require:
B. Not-for-all-Audiences tag: Request flagging applicable Content to allow Users to choose whether to see it by default. The Outpost Team may also tag Content meeting specific criteria.
Flagged Content includes, but is not limited to:
C. Outpost tools: If high risk persists despite guardrails, direct actions may be taken:
A collaborative approach is taken to moderate Community Content, ensuring adherence to our Code of Conduct. Measures include:
Collective responsibility is encouraged to maintain a healthy Community. The Community Tab allows issue discussions, proposing Pull Requests, and suggesting solutions. Harmful Content can be flagged via the "Report" button, opening a public discussion and notifying the Outpost Team.
The Outpost Team may also flag Content based on external requests or concerns. Abusive flagging, such as spamming or harassment, is not tolerated.
Our Platform offers additional tools for Content moderation:
For claims of Content violating intellectual property rights, send a detailed complaint to [email protected], including flagging the allegedly infringing Content. You represent and warrant not providing misleading information.
For feedback, contact us at [email protected] with any questions or concerns.