Glossary

Glossary

This is an incomplete record of names used in the drafting process. It serves as a somewhat informal page to redirect to when a name change occurs or to record naming ideas. This way it is kept out of other discussions.

See the Feature Request Tracker tracker for more detailed explanations.

Workshop Node (WSN)

The global node on one device. It is responsible for your global resources and knows about all the other nodes and workbenches you have.

Alternive Names

• Studio
• Lab

Nothing beats the workbench analogy in "Workshop" however.

Drone Node

A remote controlled, partial WSN in a VM or in the cloud. Useful to have a clear security boundary. Can also be instantiated on a separate device, e.g. for testing purposes.

Workbench

Your workplace for one project or several combined projects.

Workbench Bot

A lightweight, fully specified, independent, remote controllable, partial instance of a workbench. Used as a worker instance for tasks and as a tool provider on Drones.

It was previously known as Workbench Slave. Using just the term "slave" in day-to-day discussions would be terrible. Also, bots can be inactive resource providers on Drone nodes.

K-Loc

A Known Location. The workbench abstracts the directory structure and not every location is a source code repository that contributes to an application. You can, for example, have known locations managed by syncing tools, and some location might be just a dumping ground for artifacts. Others can contain project-repos.

Alternative Names

• m-loc: Managed Location. Contra: Not every location is managed. You might use one to dump artifacts.

Project Repo

A k-loc that contains resources provided by the project.