Skip to content
This repository was archived by the owner on Aug 21, 2026. It is now read-only.
This repository was archived by the owner on Aug 21, 2026. It is now read-only.

Rebrand legacy server product to "ownCloud Classic" across docs #5111

Closed

Description

@DeepDiver1975

Goal

Consistently name the legacy ownCloud server product ownCloud Classic across all user-facing documentation in the owncloud and owncloud-docker organisations. The version (10, or soon 11) is applied only as additional information where relevant — e.g. "ownCloud Classic 10".

The new product, ownCloud Infinite Scale (oCIS), must never be renamed.

Canonical naming rule

From To
ownCloud Server, owncloud Server (product sense) ownCloud Classic
ownCloud Classic Server, Classic Server ownCloud Classic
ownCloud 10 / ownCloud 11 ownCloud Classic 10 / ownCloud Classic 11
OC10 / oc10 (prose shorthand only) ownCloud Classic

Never touch: ownCloud Infinite Scale, Infinite Scale, oCIS, ocis; xref:/include:: targets; module slugs (classic_ui, oc10-app); URLs/paths; anchors/IDs; inline code/literals; and the generic "a server running ownCloud" instance sense (not a product-name use).

Scope

Documentation / user-facing text only (.adoc, .md, READMEs, release notes, website copy). Source code, identifiers, and xref targets are out of scope. Translation files (*.po/*.pot) are a separate downstream follow-up.

Process per repo

branch docs/rebrand-owncloud-classic → apply ruleset (space-containing patterns are inherently prose-only; they cannot match URLs/slugs which contain no spaces) → review oc10 shorthand by hand → verify (URL/xref targets byte-identical, oCIS count unchanged, docs build introduces no new errors) → signed commit → PR titled docs: normalize legacy server product name to "ownCloud Classic".

Repositories

Tier A — docs repos

Tier B — code repos with embedded docs (docs files only)

Enumerated via clone-and-grep (changelogs excluded as frozen release history). PRs open:

No actionable doc-prose hits (verified, no PR needed): smaller app repos not listed above.

owncloud-docker org

Zero actionable hits (verified, no PR): base, ocis, php, web, ubuntu, trivy-presets, appliance, openshift, compose-playground.

Phase 4 — drift-prevention attribute

Added: oc-classic-name (ownCloud Classic), oc-ocis-name (ownCloud Infinite Scale), oc-ocis-name-short (oCIS). Verified with a full antora site.yml build (exit 0, no new errors). Substituting these attributes into the existing .adoc occurrences is a separate, later stage and intentionally out of scope here — the attributes are inert until referenced.

Backports to maintained version branches

Re-derived per branch (content drift made cherry-pick infeasible); same ruleset, verified per branch (targets byte-identical, oCIS unchanged, build error-set unchanged where buildable).

docs-main, docs-webui, docs (aggregate) publish from a single branch — no backport needed. Archived x_archived_* branches are intentionally left untouched.

Activity

  1. 2 remaining items

  2. DeepDiver1975 commented on Jun 24, 2026

    @DeepDiver1975
    ContributorAuthor

    Tier B + owncloud-docker round opened

    Enumerated the deferred Tier B (code-repo docs) and owncloud-docker scopes via clone-and-grep and opened 8 PRs. Historical changelogs were excluded (frozen release history); the oCIS sweep was a full pass including dev/architecture/ADR/flow docs.

    Repo PR Notes
    core owncloud/core#41651 README prose
    web owncloud/web#13902 own docs/ + README; oc10 paths/config identifiers kept
    ios-app owncloud/ios-app#1562 README, KNOWN_ISSUES, Account Setup bookmark
    client owncloud/client#12573 README
    android owncloud/android#4900 README + Play Store copy; instance-sense uses kept
    ocis owncloud/ocis#12458 full sweep of docs/ocis/; oc10 codename/env/diagram ids kept
    docker/server owncloud-docker/server#647 CONTRIBUTING.md, agents.md
    docker/helm-charts owncloud-docker/helm-charts#109 Chart.yaml + generated README

    Ruleset applied consistently with Tier A. Preserved throughout: the oc10 technical codename (counterpart to the ocis codename — routing policies, OC10_* env vars, endpoints/namespaces, file ids, diagram participant ids), xref/include targets, file names (oc10_ocis_parallel.md), URLs, DB table/column names, source code, and oCIS/Infinite Scale references. Instance-sense phrasing ("a server running ownCloud", "connect to your ownCloud server") was left as-is.

    Per-repo verification: URL/xref targets byte-identical, zero residual product-name prose in doc files, no Classic Classic doubling.

    Repos with zero actionable doc-prose hits (no PR): docker base/ocis/php/web/ubuntu/trivy-presets/appliance/openshift/compose-playground.

    Remaining: the optional Phase 4 drift-prevention attribute.

  3. DeepDiver1975 commented on Jul 6, 2026

    @DeepDiver1975
    ContributorAuthor

    Verification — complete ✅

    Verified every referenced PR and the live post-merge content. All done.

    PR status (34 PRs)

    • Tier A / Tier B / owncloud-docker (17 PRs): all merged.
    • Backports (15 PRs): 11 merged; 4 intentionally closed because the target version branch is no longer live — docs-ocis#1269 (7.2), docs-client-android#257 (4.5) & Encryption: Use environment vars for recovery and occ password #258 (4.6), docs-client-ios-app#285 (12.5). Correctly checked off; work rightly skipped for retired branches.

    Live content verification (default branches, post-merge)

    Check docs-server docs-main docs-webui docs-ocis
    Product-sense ownCloud Server (cap-S) 0 0 0 0
    Bare ownCloud 10/11 not already Classic 0 0 0 0
    ownCloud Classic present 105 235 3 5
    Classic Classic doubling 0 0 0 0
    oCIS / Infinite Scale preserved ✓ ✓ (691) ✓ (9) ✓ (1238)

    Lowercase instance-sense uses ("your ownCloud server administrator", "connect to your ownCloud server") are correctly preserved per the ruleset — not product-name references.

    The canonical naming holds across the live docs with no drift and no over-application, and oCIS/Infinite Scale is untouched. Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions