Hi Kendy, On 15/03/2022 10:45, Jan Holesovsky wrote:
You really don't have to assure me. I started programming 35 years ago, I was there in the 80's and 90's, so I can compare with the present.
If you were a professional developer 35 years ago?Then you have to tell me how you can look so young as I thought you were in your early 40.
Maybe a small number of passionate and capable developers will be able to fix the CVEs and bring LOOL to a state where it could work well with the features left since the fork for those that don't need new fancy features.The most important "new fancy features" are in the area of making the editing more fluent, optimized & pleasant, do you really think there are people who don't need them?
That is always nice but maybe other features are less important to many.
The point is that we don't know until we open the repository and let people know that is available with all the relevant warnings.It is git, anybody can clone it & work on it if they want. If there were passionate and capable developers interested in this, they'd be bombarding the development mailing list with their patches the last >12 months; passionate and capable developers always find their way to get their code integrated one way or the other. But I'm not aware of any such patches.
As people have been told that the project has been forked and LOOL has been frozen I guess that no one bothered sending patches to LOOL.
Maybe if we announce that we will re open the repository, with the due warnings, we will see if some people are actually interested in contributing or not.
All the best, Kendy
Ciao Paolo -- Paolo Vecchi - Member of the Board of Directors The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts Legal details: https://www.documentfoundation.org/imprint
OpenPGP_signature
Description: OpenPGP digital signature
