Skip to content

Qualify the use of the word "tenant" to be specific to Developer Studio #926

@tillig

Description

@tillig

Context

Probably related to #922, #923, #924: The word "tenant" is used through many repositories (create a tenant, promote a tenant) but it is very confusing because the context is not conveyed. These are Developer Studio tenants, not tenants in various products. For example, my group also has a multi-tenant/multi-region product, so when consumers of that product see information about "tenants" in public repos without context, it's not obvious that these things don't pertain to them.

Solution

Anywhere "tenant" is referenced, qualify it with the product unless it's obvious otherwise.

  • In README documentation, unless the product has been made clear first in the content, require qualification of the word "tenant" to be alongside the product name (e.g., "content for Developer Studio tenants" not "content for tenants").
  • In repository descriptions, require qualification of the word "tenant" even if the product name is right in the name of the repo. ("Config and scripts for Developer Studio tenants")
Image

Alternatives

One alternative might be to remove use of the term "tenant" altogether but it seems like qualifying it with a product name would solve the problem better.

Additional Context

No response

Region

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions