Search the Community
Showing results for tags 'important'.
Found 1 result
-
Dear froxlor community, today we'd like to share some thoughts about the current state of froxlor development and where we see the project heading in the future. Many of you know that froxlor has been an open-source project for a very long time. Some of us have been maintaining and developing it for well over a decade, through countless releases, feature additions, bug fixes and architectural changes. Over the years, one thing has always driven us: building something useful while actually enjoying the process. Recently, however, the nature of project maintenance has changed significantly. Like many other open-source projects, we are receiving an increasing number of security reports generated or heavily assisted by AI tools. While some of these reports identify legitimate issues and are absolutely appreciated, a large portion require extensive manual investigation before we can even determine whether a vulnerability actually exists. The result is that an ever-growing amount of development time is spent reviewing, reproducing, verifying and responding to reports instead of improving the software itself. As the froxlor development team currently consists of only two active developers, this has become a serious challenge. We want to be very clear: Security remains important and we will continue to investigate and fix legitimate issues. At the same time, we also need to ensure that project maintenance does not completely consume the time and energy required for actual development. For this reason, we have decided to gradually shift our focus: The current 2.x branch will enter a maintenance-oriented phase. Critical bugs and important security issues will continue to be addressed, but development on the 2.x series will be kept to an absolute minimum. Our primary goal moving forward is to focus our efforts on the next major generation of froxlor: version 3.0. We believe that investing our limited time into a modernized architecture, long-term maintainability and future improvements will ultimately benefit the project and the community far more than endlessly extending the lifecycle of the current branch. froxlor exists because of its users, contributors and supporters, and we are incredibly grateful for everyone who has helped the project grow over the years. Thank you for your understanding, your feedback and your continued support. Let's build the next chapter together. — The froxlor Team
