-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The future of plugin? #228
Comments
Hi everyone! |
Hi @JellyBellyDev , I am no longer with the Organization, have informed the required folks, please allow sometime for them to respond here. |
Hi @satrox28, |
Hi guys! |
Hi @JellyBellyDev, Sorry for the late response! I'm onboarding on the repo this week and we will review the pull requests within a week. Thanks! |
Hi @amandeepsingh-bhamra, sorry but me and our company could not wait any longer. |
Any update on the future of this plugin? |
updates? |
Hi @gelopfalcon |
Hi @gelopfalcon, @sbarrypoppulo, |
Hi @satrox28!
My name is Andrea and I work for @immobiliare.
I want to thank you so much for the amazing work done on this plugin.
We really appreciate your work and have also contributed to your plugin with my colleagues
@antoniomuso and @simonecorsi.
We also love backstage and the open source world and we are introducing it in the company in a very central way.
For some time now we have noticed a decrease in maintenance activities on this plugin.
If I may, may I ask why? Perhaps you are doing something else and are no longer interested?
We are currently stuck advancing our backstage version if this plugin also doesn't continue to evolve and keep up with the backstage advancements.
I wanted to ask what projects do you have for this plugin? Do you have a vision?
If you have little time to dedicate to it, can we give you a hand as maintainer of the plugin?
We are currently already maintaining another plugin in our organization: https://github.com/immobiliare/backstage-plugin-ldap-auth
Let me know and thanks again for all you do!
I await yours!
Best
The text was updated successfully, but these errors were encountered: