diff --git a/src/components/Pages/HostingPolicy/hosting-policy/version-1.vue b/src/components/Pages/HostingPolicy/hosting-policy/version-1.vue index 6d38a82a..a60dfb88 100644 --- a/src/components/Pages/HostingPolicy/hosting-policy/version-1.vue +++ b/src/components/Pages/HostingPolicy/hosting-policy/version-1.vue @@ -3,8 +3,232 @@ -

Hosting Policy for Wikibase Cloud Staging Fake Version

-

Rest of the content would be here.

+

Hosting Policy for Wikibase Cloud

+

1. Purpose and Scope

+

This policy defines Wikimedia Deutschland’s (WMDE) expectations and criteria for hosting on Wikibase Cloud. It explains what kinds of datasets and use cases are supported by WMDE and how those decisions are made and implemented.

+

The policy exists to ensure that Wikibase Cloud technical and financial resources, as well as staff capacity are used responsibly, intentionally, in alignment with WMDE’s mission. Wikibase Cloud is not intended to be a generic free hosting service for any purpose. The policy helps us maintain visibility into how the platform is used and provides a framework to support and encourage use cases aligned with the role we want Wikibase Cloud to play in the Wikibase Ecosystem, and to address cases that clearly fall outside that role.

+

1.1 Target Audience

+
    +
  • Primary audience: the Review Committee responsible for reviewing and approving Wikibase Cloud hosting requests for continued use. The policy provides a shared framework for making consistent, transparent decisions grounded in mission alignment, resource realities, and inclusivity goals.
    • +
  • Secondary audience: Wikibase Cloud's current and prospective users, who can use this document to understand the reasoning behind WMDE’s hosting criteria and to self-assess whether their use case is likely to be accepted.
    • +
+

1.2 Relationship to other governance documents

+

(These relationships matter to ensure hosting criteria remain coherent with other governance documents, prevent contradictory expectations for contributors, and avoid overlap between responsibilities of WMDE, WMF, and individual communities.)

+ +

References to Wikidata policies are included for context only. Wikidata’s content policies, including notability criteria, do not apply to Wikibase Cloud instances. Wikibase Cloud exists specifically to support use cases that may not fit Wikidata’s scope, including non-notable, domain-specific, or preparatory datasets, while still aligning with the broader Wikimedia mission.

+

1.3 What This Policy is Not

+
    +
  • The policy defines WMDE’s own hosting criteria as the platform operator. It does not replace the policies of individual communities running their instances on Wikibase Cloud.
    • +
  • It does not describe the technical capabilities of Wikibase as a piece of software or Wikibase Cloud as a platform.
    • +
+

2. Principles

+

The following principles guide WMDE’s decisions about what can be hosted on Wikibase Cloud. They reflect WMDE’s mission, resource limitations and responsibilities as the platform operator, as well as Wikibase Cloud's intended role in the Wikibase Ecosystem.

+

Mission alignment

+

Wikibase Cloud prioritizes use cases that contribute to the creation, preservation, or sharing of open knowledge in ways that align with the WMDE statutes and support Wikimedia’s mission and the public good.

+

Wikibase Cloud's intended role: Lowering barriers to participation and experimentation

+

Wikibase Cloud exists to reduce barriers for people who want to work with structured data using Wikibase, especially those who cannot self‑host. It supports:

+
    +
  • people sharing free and open knowledge with the world for access, reuse and contribution to the Wikimedia projects,
    • +
  • people preparing and shaping knowledge for contribution to the other parts of the Wikibase Ecosystem (for example, to Wikidata) in an isolated environment,
    • +
  • people teaching Wikibase as a piece of software,
    • +
  • people evaluating, learning, or experimenting with Wikibase in an isolated environment at the start of their Wikibase journey.
    • +
+

We will support this role of Wikibase Cloud by ensuring that:

+
    +
  • the longer-term use cases aligned with it have increased chances of staying hosted,
    • +
  • the short-term use cases aligned with it can happen easily without additional procedural or bureaucratic overhead.
    • +
+

Inclusivity and support for underrepresented knowledge

+

Supporting knowledge equity is an explicit priority and expected outcome of lowering barriers. Wikibase Cloud welcomes and supports datasets that represent marginalized or underrepresented knowledge domains and use cases, unless they pose risks to platform stability.

+

Non-disruptive use

+

Wikibase Cloud operates on finite infrastructure and limited staff capacity. Hosting decisions must account for long‑term sustainability, including technical load, operational effort, and cost. Wikibase instances that would jeopardize platform stability or disproportionately consume resources may be limited or declined.

+

3. Hosting Criteria

+

Wikibase Cloud hosting decisions are based on distinct types of criteria, each serving a different purpose in the evaluation process.

+

Members of the Review Committee will independently assess these criteria. To ensure decisions are fair, consistent, and repeatable, each member reviews the application individually and documents the results with respect to each criterion. These assessments are then compared and discussed to reach a shared decision.

+

If information is insufficient to evaluate an instance, the reviewers request clarification before making a final decision.

+

If after discussion the committee cannot reach a shared decision, this indicates that certain criteria are not defined clearly enough. In such cases, the Review Committee will initiate clarification of the hosting policy before proceeding.

+

3.1 Prerequisites

+

The following conditions must be satisfied before an instance can be hosted on Wikibase Cloud. These conditions are non-negotiable and cannot be offset by positive signals.

+

mdi-circle Required Conditions (must be true)

+

These conditions must be met for an instance to be eligible for hosting.

+ +

mdi-circle Disqualifying Conditions (must not be true)

+

If any of the following conditions apply, the instance cannot be hosted.

+
    +
  • Any indication that the dataset or behavior may violate or already violates the Terms of Use (e.g., copyright violations, prohibited content, abusive behavior, harassment, privacy violations). mdi-alert Violations of the Terms of Use are governed exclusively by the Terms of Use and are not subject to the procedures described in this policy.
    • +
  • Misinformation, disinformation, or impersonation.
    • +
  • Primarily commercial or promotional purpose (for example, e-Commerce databases, a dataset for SEO optimization).
    • +
  • The instance manager is unreachable or unresponsive for over 3 months.
    • +
  • The instance manager failed to confirm either their intention to take further care of the instance, or agreement to pass it over to another manager with Terms of Use-based responsibility.
    • +
  • The instance contains (or is intended to contain) data about living people and other sensitive topics without appropriate local rules and processes to handle the content responsibly and ensure respectful collaboration.
    • +
  • The observed dataset size, traffic patterns, or write/read load are abusive and unjustified.
    • +
  • The intended or observed dataset size or load exceeds the technical capacity that Wikibase Cloud can realistically support. For example, the hosting of this dataset would require significant technical changes or infrastructure expansion, and WMDE determines that such effort is not justified for this use case.
    • +
+
+ +

Assessment of size and load

+

Wikibase Cloud does not operate with fixed numerical limits for dataset size or traffic at this stage. Decisions about size and load will be made empirically, based on observed platform behavior and past incidents. When an instance creates significant strain on the infrastructure, the situation will be investigated, discussed with the instance manager and documented in a public log together with the decision taken.

+

If a high-load use case is meaningful, the Review Committee may assess whether technical improvements and the effort to make them are reasonable. If they are, the use case will only produce a Concerning Signal.

+

Over time, documented cases will inform future decisions, creating a growing body of precedent. In all cases, instance managers will be contacted and involved in finding a reasonable solution before further action is taken.

+ +
+

mdi-minus-thick3.2 Concerning Signals

+

These signals indicate potential risk or misalignment. They do not automatically lead to rejection, but must be counterbalanced by positive signals.

+
+ +
    +
  • 2 concerning signals lead to disqualification.
    • +
  • 1 concerning signal must be counterbalanced with 2 positive signals.
    • +
+ +
+
    +
  • + The instance is only intended to be used by the contributing individual or organization with no clear external audience (people or groups who meaningfully benefit from it), including use cases that support purely internal workflows, private organizational processes, or personal documentation, like internal CRM systems, business asset management.
    The exceptions that do not produce this concerning signal are: +
      +
    • The instance is a staging ground for a dataset being prepared for later contribution to the other parts of the Wikibase Ecosystem (for example, to Wikidata)
      • +
    • The instance supports teaching Wikibase as a piece of software.
      • +
    • The instance is used in the context of building a software tool intended to benefit the Wikidata/Wikibase Ecosystem - for example, a bot, data importer, or gadget. The instance holds real or mock data that the tool can operate on during development.
      • +
    +
    • +
  • The intended or observed dataset size or read/write load exceeds or approaches excess of current sustainable limits, or the instance exhibits sudden or disproportionate spikes in traffic that strain infrastructure. WMDE decides that allocating additional technical effort to support the use case in the future is justified (see the explanation of how the assessment of size and load happens above).
    • +
  • Used purely as a MediaWiki, no structured data involved
    • +
  • Ongoing unattended infestation with spammers and other vandalism
    • +
+

mdi-plus-thick3.3 Positive Signals

+

These signals indicate alignment with the value proposition of Wikibase Cloud and provide a chance for instances that raised concerning signals to recover from them and stay hosted.

+
    +
  • The instance advances knowledge equity or representation of marginalized or underrepresented knowledge domains and use cases (this one produces 2 positive signals).
    • +
  • The instance contributes to education, cultural preservation, research or public benefit.
    • +
  • The contributing individual, organization or community has limited technical skills, hosting capacity or financial resources to run and maintain a self-hosted Wikibase, , or their existence in the future is uncertain. The project can only realistically proceed and survive because Wikibase Cloud removes financial, technical, or infrastructural barriers in the long-term.
    • +
+

4. Decision Process

+

4.1 Temporary-by-Default Rule

+

All instances created on Wikibase Cloud are temporary by default. Temporary instances allow people to experiment with Wikibase or Cloud’s capabilities without needing to go through a full application process.

+

For their instance to remain hosted on Cloud on a long-term basis, the manager must submit an application. Temporary instances that never applied for long-term hosting get suspended after 3 months.

+

The following process outlines how decisions are made for initial acceptance and continued hosting.

+

4.2 Application

+

When applicants request long‑term hosting on Wikibase Cloud, they will be required to:

+
    +
  • provide information about their use case;
    • +
  • take steps to meet the Hosting Criteria.
    • +
+

4.3 Review

+
    +
  • The Review Committee reviews new applications on an ongoing basis, subject to the availability of its members.
    • +
  • Each reviewer evaluates the use case independently against the Hosting Criteria, noting the situations where essential information is missing or unclear.
    • +
  • + Reviewers compare their evaluation and decide on the next steps. +
      +
    • If essential information is missing or unclear, reviewers request clarification from the applicant.
      • +
    • Applicants may be asked to make adjustments before the review can continue.
      • +
    +
    • +
  • Reviewers discuss and, once confident, reach a final decision on whether the instance may remain hosted on Cloud on a long-term basis.
    • +
  • If the instance cannot remain hosted on Cloud, it is scheduled for suspension in at least 2 weeks, but not earlier than 3 months from its creation (see Suspended Instances).
    • +
+

4.4 Ongoing Re‑Evaluation

+
    +
  • All hosted instances may be re‑evaluated periodically to ensure continued alignment with Cloud’s principles and criteria.
    • +
  • Re-evaluation is scheduled on an individual basis when the instance gets approved by the committee, or happens sooner if WMDE notices that a specific instance is being used in a way that is not compliant with any Wikibase Cloud policy.
    • +
  • If an instance no longer meets the hosting criteria, the manager may be asked to make adjustments. If the required adjustments are not made, or if meeting hosting criteria is deemed impossible from the outset, the instance will be suspended.
    • +
+

4.5 Suspended Instances

+

Unless there is a clear violation of Terms of Use, instances get suspended with a two weeks' notice.

+

Suspended instances remain unavailable for access, but the data in them is not physically deleted yet.

+

Suspended instances get permanently deleted after 3 months, with the domain name being released back to the pool.

+

4.6 Appeals

+

If an instance is scheduled to be or already is suspended and the manager believes the decision was based on incomplete or incorrect information, they may submit an appeal. Appeals must:

+
    +
  • explain what information was missing, inaccurate, or misunderstood;
    • +
  • provide any additional information for reconsideration.
    • +
+

The Review Committee will review the appeal with priority over new applications. A suspension may be reversed if the additional information resolves the concerns that led to the suspension.

+

4.7 Review Committee

+

The group participating in decision-making is:

+
    +
  • Wikibase Ecosystem Portfolio Manager
    • +
  • Wikibase Cloud Product Manager
    • +
  • Head of Product Strategy
    • +
  • A rotating member of the Wikibase Cloud team
    • +
+

We also welcome participation from community members who wish to contribute to hosting decisions. If volunteers express interest and have the capacity to join, WMDE will establish a process for including them in the Review Committee.

+

4.8 Migration of Existing Instances

+

When this policy is implemented, all existing instances must undergo the hosting application process.

+
    +
  • WMDE will set a clear deadline by which all instance managers must submit their application.
    • +
  • Instances that do not submit an application by the deadline will transition to suspended status.
    • +
  • If an instance needs or chooses to move away from Wikibase Cloud, we aim to provide reasonable support in this transition where possible.
    • +
+

5. Transparency and Communication

+

We aim to make hosting decisions clear, predictable, and respectful for all applicants.

+

5.1 Communication of Decisions to Applicants

+
    +
  • Applicants receive a written decision summarizing the Review Committee’s assessment.
    • +
  • When an instance is not accepted, the decision references relevant criteria, provides the minimum necessary reasoning for suspension (without revealing internal deliberations) and lists any actions required to bring the instance into compliance.
    • +
+

5.2 Public Log of Decisions

+
    +
  • To support transparency and trust, WMDE will maintain a public log summarizing the statistics of hosting decisions made by the Review Committee. Its purpose is to help the community understand how the policy is applied in practice.
    • +
  • Sensitive or private information from the applications will not be published.
    • +
+

5.3 Requests for Clarification

+
    +
  • Applicants may request clarification about the decision, the interpretation of criteria, or what changes might improve future eligibility.
    • +
  • The Review Committee provides clear, concise answers, but does not engage in negotiation or redefining criteria.
    • +
+

6. Policy Revision and Updates

+

To ensure this policy remains accurate, effective, and aligned with WMDE’s mission and operational realities, it will be revised and updated on a regular basis.

+

6.1 Revision Cycle

+
    +
  • + The policy will undergo a formal revision at least once per year, or sooner if: +
      +
    • significant changes in infrastructure, mission priorities, ecosystem needs, or WMDE’s resource constraints arise,
      • +
    • the decision process is found unsustainable, too time‑consuming, unclear, or inconsistent to apply in practice,
      • +
    • the criteria do not reliably lead to aligned decisions within the Review Committee.
      • +
    +
    • +
  • Interim updates may be made if issues are identified during application reviews, re‑evaluations or appeals.
    • +
+

6.2 Responsible Parties

+
    +
  • The Review Committee performs the policy revision.
    • +
  • Community members may be consulted on proposed updates, especially when changes affect expectations for contributors or project eligibility.
    • +
+

6.3 Update Process

+
    +
  • Proposed changes are drafted by the Review Committee based on identified needs, operational learnings, or feedback.
    • +
  • Draft updates are shared internally and externally for review and alignment.
    • +
  • Once approved, updates are published on the relevant documentation pages.
    • +
+

6.4 Previously Suspended Instances

+
    +
  • Instances suspended under an earlier version of this policy are not automatically re‑evaluated retrospectively.
    • +
  • However, users may submit an appeal requesting a new review.
    • +
  • Appeals for previously suspended instances are assessed according to the updated policy.
    • +
+

6.5 Versioning

+
    +
  • Major outdated versions are archived but remain accessible for reference.
    • +
diff --git a/src/router/index.js b/src/router/index.js index 4c22ff57..1a0efb38 100644 --- a/src/router/index.js +++ b/src/router/index.js @@ -19,7 +19,7 @@ import Privacy from '@/components/Pages/Privacy/Privacy' import User from '@/components/Pages/User' import Discovery from '@/components/Pages/Discovery/Discovery' import Complaint from '@/components/Pages/Complaint.vue' -import HostingPolicyPilot from '@/components/Pages/HostingPolicyPilot.vue' +import HostingPolicy from '@/components/Pages/HostingPolicy/hosting-policy/version-1.vue' import HostingPolicyRenderer from '@/components/Pages/HostingPolicy/HostingPolicyRenderer.vue' import DsaInfo from '@/components/Pages/DsaInfo/DsaInfo' @@ -92,9 +92,9 @@ const router = new Router({ component: HostingPolicyRenderer, }, { - path: '/hosting-policy/pilot', // Remove after T408316 - name: 'HostingPolicyPilot', - component: HostingPolicyPilot, + path: '/hosting-policy/', + name: 'HostingPolicy', + component: HostingPolicy, }, { path: '/hosting-policy/:activeFrom',