Hello Osmocom community, Over the past several months I developed my own RTP endpoint implementation library (alternative to libortp), and I seek to get it merged into libosmo-netif so it can be used by OsmoBTS as an option: https://gerrit.osmocom.org/c/libosmo-netif/+/39280 https://gerrit.osmocom.org/c/libosmo-netif/+/39281 https://gerrit.osmocom.org/c/libosmo-netif/+/39291 I am now working on documentation, which I need to finish before I can lift these patches out of WIP in Gerrit. The last of the 3 WIP patches linked above is the one adding an adoc manual, built with the same tools as other Osmocom manuals, and I need some help with this one: 1) When I run './configure --enable-manuals' followed by 'make' on the Debian machine which Vadim provided to me for Osmocom documentation work, everything seems successful and I get a PDF rendering of my WIP manual. However, as soon as I uploaded this patch to Gerrit, I see a build failure in Jenkins. What am I doing wrong? I'm afraid that my knowledge of Autotools is not good enough to figure this one out. 2) My progress in writing the actual manual has reached the point where I need to insert some graphical diagrams showing the flow of RTP packets and the latency and jitter they experience in transit. I am thinking of one horizontal axis showing regularly spaced packets as they are emitted by the source, then forward-and-down arrows showing their transit with fixed or variable latency, then another horizontal axis below showing the receiver's view of time, with marked arrival times of packets (endpoints of latency arrows) and fixed-spacing times when the GSM or TDM system polls the jitter buffer. Question: what is the appropriate tool within the accepted Osmocom adoc suite for drawing such diagrams? If I weren't trying to get my RTP implementation accepted into Osmocom, I would have written this manual in troff on my favorite 1980s UNIX system, using pic preprocessor in the troff suite for graphical drawings like this one - but I reason that I need to write my manual within Osmocom documentation framework in order to maximize the chance of the associated code library being accepted into libosmo-netif, with follow-on patches to osmo-bts to use it optionally as an alternative to libortp. 3) When I do successful test builds on Vadim's Debian machine and get a PDF rendering of my WIP manual, the cover page in the PDF features both Sysmocom and Osmocom logos just like the mainstream Osmocom manuals, with Sysmocom logo on top. While this arrangement is probably appropriate for the existing manuals which were written predominantly by members of Sysmocom crew, it seems quite wrong for an external contributor's manual that does not contain a single sentence written by Sysmocom. How do I tweak things to remove that Sysmocom logo from the cover page, or even better, put San Diego 2G Association logo in its place? My contributions to Osmocom are directly linked to my efforts to build a new GSM network in San Diego, hence there is some symmetry between Sysmocom and SD2G in terms of Osmocom FLOSS project contributions, except for the rather big asymmetry in that SD2G is strictly non-profit. M~