El dissabte, 8 de novembre del 2025, a les 0:59:10 (Hora estàndard d’Europa 
central), Kyle Auble va escriure:
> I'm planning to start contributing more to Poppler (easing back into
> programming after a long break). I had some process questions for the
> mailing list first though:
> 
> 1. Do you like to have a corresponding issue for every merge-request? Or do
> you just want the merge-request if it's for yeoman's work (various
> build-chain warnings, refactoring, etc.)?

I would prefer you do not create an issue if you are going to create a MR.
 
> 2. Do you have any particular plans for the stale merge-requests? Are those
> something that you would like to see triaged at some point?

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.

> 
> 3. Many of the old (but still open) bug-reports have significant overlap
> with a common theme (e.g. RTL has fundamental issues or complex graphics
> slow down rendering). Is there any interest in consolidating those under a
> single report per deeper issue? It's probably unnecessary, but it might
> help if all the different threads are summarized and files are kept in one
> place.

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.

Even if the user facing issue seems similar it may be that it's caused by two 
different things and then you can't close the bug beause you only fixed one 
side of it.

> 4. Last one, but for new documentation, would you still focus on the old
> wiki at freedesktop.org/wiki/Software/poppler ? Or have you been leaning
> towards starting a wiki through the Gitlab instance?

What kind of documentation are you thinking about?

Cheers,
  Albert

> 
> Thanks again, and hopefully I can help a lot in the coming months,
> Kyle Auble




Reply via email to