Replies: 5 comments 2 replies
-
I could help with the Infrastructure area maintenance in the new repo, but I'm not a developer, so it doesn't make sense to become a repo owner from my side - that is why I am asking here for volunteers with relevant development experience, willing to step in |
Beta Was this translation helpful? Give feedback.
-
Just FYI, message from maintainer:
https://discord.com/channels/794576839813234688/794576839813234696/1149785865049079840 |
Beta Was this translation helpful? Give feedback.
-
As a next step in this discussion, I've created a PR #910 with the most interesting and ready-to-be-merged fixes and improvements for the product. So, feel free to check that PR and use it. The PR's description contains a how-to guide to deploy the app from the source code. BTW, while I cover outdated base image and 3rd-party software issue by rebuilding the image locally, we still have outdated dependencies in the source code, so if we have some skilled backend and frontent developers, who would like to contribute and help the community, it will be great to see PRs with updated dependencies and migration to the latest Node LTS version |
Beta Was this translation helpful? Give feedback.
-
The project restarted with 2 active maintainers, so closing this discussion |
Beta Was this translation helpful? Give feedback.
-
According to the frequency of commits and amount of pending PRs, it looks like the current repo owner @viktorstrate doesn't maintain it anymore.
But as new issues are reported, PRs created, and even sometimes new discussions are started, there is an active community of product users, interested in product growth and bug fixes.
So, I'd like to ask whether we have here a developer (or a group of developers), familiar with the technology stack and has enough experience to take ownership of the product and maintain it.
From my point of view, the requirements for this role are:
Technically I see the process as:
Waiting for your opinions in the comments)
Beta Was this translation helpful? Give feedback.
All reactions