Re: [xml] Resuming maintenance

12 Jan 2022, 10:24 by xml@gnome.org: > Personally, I think the main problem is funding. The pool of competent > programmers willing to spend months of their time to work on a rather > outdated code base implementing mostly legacy technology for free is tiny or > even non-existent. It's really th

Re: [xml] Resuming maintenance

On 12/01/2022 17:30, Stefan de Konink wrote: If you're seeing degraded performance on large documents, it's likely another issue with quadratic runtime. Fixing such issues algorithmically should typically yield much better results than trying to work around them with multi-threading. What can

Re: [xml] Resuming maintenance

On Jan 12, 2022, at 7:24 AM, Nick Wellnhofer via xml wrote: > On 10/01/2022 20:47, Mike Dalessio wrote: >> Although I'm relieved, the potential loss of maintainers from the project >> was >> alarming. Perhaps another goal to con

Re: [xml] Resuming maintenance

Hi Nick, On Wednesday, January 12, 2022 3:49:07 PM CET, Nick Wellnhofer wrote: I didn't make any performance improvements to the XSD code personally. You're probably seeing improvements from the following commit which wasn't authored by me: https://gitlab.gnome.org/GNOME/libxml2/-/commit/

Re: [xml] Resuming maintenance

On 11/01/2022 11:38, Daniel Veillard wrote: So you want to reintegrate libxml2 within the GNOME framework ? TBH now that I have very limited bandwidth that's probably the right thing to do. I didn't mean the GNOME desktop environment itself, but the infrastructure that the GNOME Foundation o

Re: [xml] Resuming maintenance

On 10/01/2022 20:47, Mike Dalessio wrote: Although I'm relieved, the potential loss of maintainers from the project was alarming. Perhaps another goal to consider for the year is to expand the pool of contributors and maintainer

Re: [xml] Resuming maintenance

On 10/01/2022 16:51, Stefan de Konink wrote: This is great news, thanks Google for acknowledging the importance of maintaining core open source products. Your previous improvements on XSD validation made a great difference, but from my prototype in Python (LXML) I assume that multithreaded cons

Re: [xml] Resuming maintenance

On Mon, Jan 10, 2022 at 03:20:09PM +0100, Nick Wellnhofer via xml wrote: > Hello, > > Thanks to a donation from Google, I'm able to resume maintenance of libxml2 > (and libxslt) for the remainder of 2022. Yay ! :-) > My immediate plans are: > > - Make a bug fix release fixing many regression

Re: [xml] Resuming maintenance

Nick Wellnhofer via xml schrieb am 10.01.22 um 15:20: Thanks to a donation from Google, I'm able to resume maintenance of libxml2 (and libxslt) for the remainder of 2022. I'm very happy to read this, Nick. All the best for 2022. Stefan ___ xml mailin

Re: [xml] Resuming maintenance

I'm so happy to hear that you'll be able to spend time on libxml2 this year, Nick. Thank you and thanks to Google. Although I'm relieved, the potential loss of maintainers from the project was alarming. Perhaps another goal to cons

Re: [xml] Resuming maintenance

Dear Nick, This is great news, thanks Google for acknowledging the importance of maintaining core open source products. Your previous improvements on XSD validation made a great difference, but from my prototype in Python (LXML) I assume that multithreaded constraint validation and a more effi

[xml] Resuming maintenance

Hello, Thanks to a donation from Google, I'm able to resume maintenance of libxml2 (and libxslt) for the remainder of 2022. My immediate plans are: - Make a bug fix release fixing many regressions. - Establish a new release schedule, possibly with multiple branches being maintained. - Move