upstream-archive/presidio
1
0
Fork 0
mirror of https://github.com/data-privacy-stack/presidio.git synced 2026-09-21 13:38:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

Revise project transition details for clarity

Browse Source 
Updated the project transition documentation to reflect the completion of Presidio's transition to a community-owned project, including changes in wording for clarity and accuracy.
This commit is contained in:
Omri Mendels
2026-09-20 11:33:16 +03:00
committed by GitHub
parent 56f576d7d3
commit 463580e01f
1 changed files with 20 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/project_transition.md
+20 -22
View File
@@ -1,47 +1,45 @@
# Presidio is transitioning to a community-owned project
# Presidio has transitioned to a community-owned project
We want to share an important update regarding the future of Presidio.
The Presidio project is in the process of transitioning from a Microsoft-owned project to an independent, community-governed open source project under the new GitHub organization Data Privacy Stack. Its new URL is: <https://github.com/data-privacy-stack/presidio>
The Presidio project has completed its transition from a Microsoft-owned project to an independent, community-governed open source project under the GitHub organization Data Privacy Stack. Its official URL is: <https://github.com/data-privacy-stack/presidio>
Microsoft supports this transition and the continued success of the Presidio project as an open source community initiative.
Microsoft supported this transition and the continued success of the Presidio project as an open source community initiative.
Our goal is to ensure Presidio continues to serve the privacy engineering and data protection community as an open, transparent, and vendor-neutral project.
Our goal remains to ensure Presidio serves the privacy engineering and data protection community as an open, transparent, and vendor-neutral project.
## What this means
* Presidio will continue to be open source under the MIT license.
* Existing functionality, APIs, and documentation will remain available.
* The project will continue to be maintained by contributors and volunteers from the community.
* The project will not be owned or operated by a commercial entity.
* Presidio continues to be open source under the MIT license.
* Existing functionality, APIs, and documentation remain available.
* The project is maintained by contributors and volunteers from the community.
* The project is not owned or operated by a commercial entity.
* The focus on privacy, responsible AI, and data protection tooling remains unchanged.
## Microsoft and Azure users
This transition does not change the experience for existing users of Presidio, including organizations using Presidio alongside Microsoft and Azure services.
This transition does not change the experience for users of Presidio, including organizations using Presidio alongside Microsoft and Azure services.
Existing integrations, dependencies, and usage patterns are expected to continue working as they do today.
Integrations, dependencies, and usage patterns continue to work as expected.
## Why this change
Over the years, Presidio has grown beyond its original scope and has been adopted by organizations, researchers, and developers across industries. We believe the project is best positioned for long-term sustainability, broader collaboration, and open governance as an independent community initiative.
Over the years, Presidio has grown beyond its original scope and has been adopted by organizations, researchers, and developers across industries. Moving to an independent community initiative positions the project for long-term sustainability, broader collaboration, and open governance.
## What to expect during the transition
During the migration process:
Now that the migration is complete:
* Repositories, documentation links, and package references may gradually change.
* Some GitHub URLs and documentation pages may redirect temporarily.
* New Docker image releases are published to [GitHub Container Registry](https://github.com/orgs/data-privacy-stack/packages) under the Data Privacy Stack organization. Legacy Microsoft Container Registry (MCR) images remain available for older tags but are no longer updated; update `mcr.microsoft.com/presidio-*` image references to `ghcr.io/data-privacy-stack/presidio-*`.
* Contribution and governance processes will evolve and become more community-driven.
* The technical steering committee (TSC) will expand to include maintainers and contributors from outside Microsoft.
We will do our best to keep the transition smooth and minimize disruption for users and contributors.
* Repositories, documentation links, and package references have moved to the new organization. Please update your references.
* Legacy GitHub URLs and documentation links redirect to the new location.
* New Docker image releases are published to[GitHub Container Registry](https://github.com/orgs/data-privacy-stack/packages) under the Data Privacy Stack organization. Legacy Microsoft Container Registry (MCR) images remain available for older tags but are no longer updated; update `mcr.microsoft.com/presidio-*` image references to `ghcr.io/data-privacy-stack/presidio-*`.
* Contribution and governance processes are now community-driven.
* The Technical Steering Committee (TSC) includes maintainers and contributors from across the community.
## Maintainers and contributors
Many of the current maintainers and contributors intend to remain involved during and after the transition. We also welcome new contributors who care about privacy-preserving technologies and responsible data handling.
Maintainers and contributors continue to actively drive the project. We welcome new contributors who care about privacy-preserving technologies and responsible data handling.
More details regarding governance, contribution guidelines, maintainership, Docker image publishing, and roadmap planning will be shared as the transition progresses.
Details regarding governance, contribution guidelines, maintainership, Docker image publishing, and roadmap planning are available in the repository documentation.
Thank you to everyone who has supported Presidio so far and helped make it a valuable resource for the broader privacy engineering community.
Thank you to everyone who supported Presidio through this transition and helped make it a valuable resource for the privacy engineering community.