On Mon, 10 Nov 2025 15:00:12 +0100, Albert Astals Cid wrote: > I would prefer you do not create an issue if you are going to create > a MR.
> There's two different sets of stale MRs, the ones I have had not time > to review and the ones that the authors have not followed up after my > comments. > > For the first set, a review from other people is always welcome. For > the second set, you can always adapt the MR if you think the changes > are worth it. > I feel that consolidating bugs is sometimes "impossible" (and thus a > waste of time). > > You can only really know it's the same bug once you fix it and it > fixes both issues. That all makes sense to me; I'll keep it in mind going forward. > What kind of documentation are you thinking about? Mainly basic contributor's notes: design overview (maybe with a diagram or two), process details, tips for trickier parts of the code, where to find the PDF standard reference, things like that. On a slightly related note, does poppler now require pkg-config for all supported build targets? I saw that even the Appveyor pipeline for Windows pulls it in now. I'm going through the build-system first to familiarize myself, and it may be possible to consolidate a lot with the current required CMake and build environment. Kyle > Cheers, > Albert
