This repo chef/omniauth-chef-oauth2 is being considered for archival #9
Description
What's happening?
This repository is being considered for archival as part of the Chef OSS Repository Lifecyle Management process. Archiving means that the repo will still be available for read-only access, but no further changes will be made to it after it is decommissioned.
Why?
For details on the rationale and criteria for selection, please see Chef OSS Repository Lifecycle Management - Categorization
What will happen?
For details on the decommissioning process, please see Chef OSS Repository Lifecycle Management - Decommissioning
When will it happen?
This notice was posted on 2025-12-12.
On or after 2026-01-04, this repository will be archived unless a decision is made to keep the repo open based on feedback.
What can I do?
Suggest Alternatives
If you have suggestions for alternatives to this repository, please comment on this issue with your suggestions. Chef archivists will review these suggestions and may update the issue with additional information.
Make Keep Requests
To request that the repository not be archived, please do both of the following:
- React with a thumbs-down to this issue
- Make a comment on this issue explaining your need
Chef archivists will search for such reactions and collate such comments. Not all requests can be honored. Discussion will be held in the comments of this issue.
If you cannot or do not wish to provide feedback via the GitHub interface, you may also use the alternate contact form at Chef OSS Repository Lifecycle Management Contact Form.
Fork the Repository
As most of our projects are open source, you are welcome to fork the repository and continue development on your own. Please read the Chef OSS Repository Forking Information for more information on how to best coordinate, including how to be listed as the successor.