- Issue created by @Anybody
- Status changed to Postponed
over 1 year ago 2:24pm 12 April 2023 - 🇪🇸Spain marcoscano Barcelona, Spain
Thank you @Anybody and @Grevil for the offering to collaborate! 👏
Unfortunately I still feel this module isn't ready for production (or at least for being promoted as "ready"), since less experienced site builders and developers could blindly install it and oversee some scenarios where it could actually be exposing private information on their sites. The main point of concern to my eyes is 📌 Implement list access control / query alter Active , which would be a blocker since list access is as important as standalone routes access.
Concerning co-maintainership, I'm open to having others on board, but let's first work on issues together for some time, that will help us to know each other better and have a better co-maintenance over time. I'd suggest to try to work on 📌 Implement list access control / query alter Active as a first step, and then maybe go from there?
Thanks!
- 🇩🇪Germany Anybody Porta Westfalica
Hi @marcoscano thanks for your feedback and nice to hear you're interested in pushing things forward here.
Regarding the risks and readyness, I totally agree. That point was based on ✨ Split experimental access modes into submodules Active . Perhaps you could have a look, if you like the plan?
As first step I'd like to fix 📌 Drupal 9/10 compatible release and plan? Fixed so that the module is usable and testable with Drupal 9 and 10 again, even if still experimental. - 🇩🇪Germany Anybody Porta Westfalica
@marcoscano: We updated some of the issues, would be nice if you could have a first look and provide feedback. Furthermore it would be great, if the Drupal 9 / 10 compatibility fix would be pushed to make the module usable there asap.
Thanks :)
Let us hear, what you think about the separate issues.