Public projects glossary
Azure DevOps Services - Public Projects
This glossary describes terms used when working with public projects in Azure DevOps Services. See also:
An unauthenticated user of a project. The user is visiting a project and has not signed in to Azure DevOps.
An authenticated user of a project who was granted the Basic access level to a project. To learn more, see Default roles & access for public projects.
A person who has read and write access to most functions and features of a project. A contributor is an authenticated user of a project who was granted the Basic access level and belongs to the Contributors security group. Contributors can add and modify code, add and modify work items, define and edit build and release pipelines, and more. To learn more, see Default permissions and access.
User-configurable interactive signboards that provide real-time information. Dashboards are associated with a team and display configurable widgets to display information. Learn more: Add and manage dashboards.
A Git repository supports a distributed version control system for tracking changes, reviewing contributions to the code, and more. Each developer has a copy of the source repository on their dev machine. You can add multiple Git repositories to a project. Learn more: Git Repositories.
Git in Visual Studio and Azure DevOps is standard Git. You can use Visual Studio with third-party Git services, and you can also use third-party Git clients with Azure DevOps.
Either a public user or an anonymous user. Many of the controls in place for public projects apply equally to public and anonymous users. To learn more, see Default roles & access for public projects.
Open source software refers to freely available software that you can download, use, modify, and share. To explore Microsoft Open Source projects, see Open Source at Microsoft. Learn more: What is open source?.
The Azure DevOps platform associated with a URL (for example,
https://dev.azure.com/OrganizationName/ProjectName/) that supports adding both private and public projects. Owners and administrators can manage user access to their organization's data through security groups, access levels, and other administrative options.
Pipelines are artifacts that you define to run concurrent builds or deploy concurrent releases. Two types of pipelines are supported, private and hosted. To learn more, see CI/CD concurrent jobs.
A project created within an organization that is visible only to members of the organization hosting the project. Only organizational members can discover them. Administrators can control who gets to fully contribute. Administrators can switch a project from private to public, and vice-versa, as described in Change the project visibility.
A project, which was previously known as a team project, provides a repository for source code. A project provides a place where a group of people can plan, track progress, and collaborate on building software solutions. A project is defined for an Azure DevOps Services organization or within a TFS project collection. You can use it to focus on those objects defined within the project. To learn more, see About projects and scaling your organization.
A project created within an Azure DevOps Services organization that is visible to the whole world. Everyone in the world can discover them and perform limited operations. You can use the Azure DevOps CLI to discover a list of projects. Administrators can control who gets to fully contribute. Administrators can switch a project from private to public, and vice-versa, as described in Change the project visibility.
An authenticated user of a project who is not a member of the project.
An authenticated user of a project who was granted Stakeholder access. An unlimited number of users can be granted membership as Stakeholders for free. Stakeholders can add and modify work items, approve releases, view dashboards and wikis. Learn more: Access levels, Stakeholder access.
A team corresponds to a selected set of project members. With teams, organizations can subcategorize work to better focus on all the work they track within a project. Each team gets access to a suite of Agile tools. Teams can use these tools to work autonomously and collaborate with other teams across the enterprise. Each team can configure and customize each tool to meet their work requirements. To learn more, see About teams and Agile tools.
Widgets display information and charts on dashboards. Many of them can be configured. Many widgets display information available from one or more data stores or charts created by the system. To learn more, see Widget catalog.