Skip to content

Clarify terminology and role names #3

Description

@aaaaalbert

This isn't a big issue right now, but we'll want to start using a consistent terminology in our website and docs to make sure it's always obvious who the target audience is. For example, the "Using EdgeNet" page mentions "developers"; actually, the paragraph is relevant for experimenters using EdgeNet.

Potential problems

  • user, end user --- I suggest "experimenter" instead
  • website --> Could be this repo or the portal or the dashboard, so choose wisely
  • operator --> Make clear what component they control, e.g. "portal operator"

You can possibly spot other instances, please list them here.

Activity

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