Is 3 alpha ready for production and what is the roadmap for a production release

I was wondering this, too. The 8.x-1.x releases are marked as recommended, yet they have many fewer features, fewer fixes, and half as many reported installs (6k vs 12k).

At this moment, the main objective is to make sure that the 3.x branch works on Drupal 11. I'd love that someone that actively used this module would be interested in taking it over. One of my objectives with the 3.x branch would use the code from https://oauth2-client.thephpleague.com/ in order to have a sane codebase. Not sure if that objective is realistic, as the small add-ons for OIDC added to this module may not be possible with the pure OAuth 2.0 code that that package uses.

Given there are already 12000+ sites using 3.x I'd suggest releasing a stable version of what's in the alpha that supports 11.x, and open up a 4.x branch to investigate the package mentioned in #4.

I agree with the idea of releasing a stable version of what's there right now in 3.x and then starting 4.x to start implementing oauth2-client.

@jcnventura regarding finding another maintainer, this project already has five! Has it not really been maintained?

I would like to make a further suggestion:

• Release 3.0.0 based on 3.0.0-alpha3. Provide only security support for the 3.0.x branch; no other development.
• Open branch 3.1.x. Set the minimum to Drupal 10.3 (no Drupal 9 support). Implement Drupal 11 compatibility only here.

This gets around the challenges of supporting Drupal 11 along with much older versions of Drupal while avoiding dropping support for older versions in a patch-level release.

A release plan of first beta/RC allowing the maintainers to list what is currently "blocking" a stable release? Would also allow users to jump in on those issue and perhaps help out getting them tested and merged. The maintainers are very active, but it would be helpful (at least to me) to see a release plan. Still on alpha often means there are features missing...