# TC meeting minutes

**URL:** <https://forum.collaboraonline.com/t/tc-meeting-minutes/4581>\
**Category:** Development\
**Created:** [April 8, 2026, 2:43pm UTC](https://forum.collaboraonline.com/t/tc-meeting-minutes/4581 "2026-04-08T14:43:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmeeks](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/mmeeks/32/371_2.png) [@mmeeks](https://forum.collaboraonline.com/u/mmeeks)\
**Post date:** [April 8, 2026, 2:43pm UTC](https://forum.collaboraonline.com/t/tc-meeting-minutes/4581/1 "2026-04-08T14:43:12Z")

</div>

\* Present  
&nbsp;&nbsp;+ Michael S, Michael M, Andras, Stephan, Samuel Ruegger,  
&nbsp;&nbsp;&nbsp;&nbsp;Thibaut P, Szymon, Tomaz (Quikee), Dennis, Darshan, Hubert, Andreas K

\* Action items

\* Releases (Andras)  
&nbsp;&nbsp;+ doing releases from the stable branches as normal  
&nbsp;&nbsp;+ more interesting - plan to have a 26.04 Beta before COOL-days  
&nbsp;&nbsp;+ like to release new Collabora Office from same 26.04 code-base  
&nbsp;&nbsp;&nbsp;&nbsp;+ for Windows/Mac/Linux etc.

\* CI status (Szymon)  
&nbsp;&nbsp;+ now reasonable, but was failing because of some C++ compiler  
&nbsp;&nbsp;&nbsp;&nbsp;issue on the core side  
&nbsp;&nbsp;&nbsp;&nbsp;+ two patches in at once an auto-merging collision  
&nbsp;&nbsp;&nbsp;&nbsp;+ one renaming the header, one used the old  
&nbsp;&nbsp;+ re-base on top of new main branch  
&nbsp;&nbsp;+ recent cypress-desktop is failing many builds  
&nbsp;&nbsp;&nbsp;&nbsp;+ Szymon will look at this too.

\* Patch review (Darshan)  
&nbsp;&nbsp;+ gerrit - around 100 open patches  
&nbsp;&nbsp;+ github - around 127 open patches

&nbsp;&nbsp;+ hoping to catch up with reviews after the move soon.

&nbsp;&nbsp;\<put top five people authors say - with un-reviewed  
&nbsp;&nbsp;&nbsp;patches for next week\>

&nbsp;&nbsp;+ PRs without reviewers around 16 of them

&nbsp;&nbsp;[Collabora Online · GitHub](https://github.com/orgs/CollaboraOnline/projects/3/views/2)

&nbsp;&nbsp;+ Welcome board - is a bit broken, so added a welcome github action (Darshan)  
&nbsp;&nbsp;&nbsp;&nbsp;+ AI: explore what is possible with gerrit for welcoming (Darshan)  
&nbsp;&nbsp;&nbsp;&nbsp;+ expect not having such a rich UI on gerrit (Andras)

\* Monorepo (Andras)  
&nbsp;&nbsp;+ work underway to have the source-code for COOL + CO in one git repo.  
&nbsp;&nbsp;+ most reviewers prefer gerrit to github  
&nbsp;&nbsp;+ so we plan to move everything into gerrit  
&nbsp;&nbsp;+ github will be a readonly mirror  
&nbsp;&nbsp;+ have a core branch which has submodules - will merge some of these  
&nbsp;&nbsp;&nbsp;&nbsp;+ dictionaries & help-content  
&nbsp;&nbsp;&nbsp;&nbsp;+ merge under online & push to gerrit  
&nbsp;&nbsp;+ but not the translations - which will be separate  
&nbsp;&nbsp;+ Andras planning how to reflect all of this in the build-system  
&nbsp;&nbsp;+ could stay as a submodule if people don't use it (Stephan)  
&nbsp;&nbsp;+ persistent problems with them (Michael)  
&nbsp;&nbsp;+ could merge the repo flattened - but it will grow huge.  
&nbsp;&nbsp;+ schedule: when do we have time ?  
&nbsp;&nbsp;&nbsp;&nbsp;+ changing all the jenkins jobs is quite a big task.  
&nbsp;&nbsp;&nbsp;&nbsp;+ several hundred open-patches on both-sides to re-do.  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ will always be work going in.  
&nbsp;&nbsp;&nbsp;&nbsp;+ prepare by having a trial-run ... ?  
&nbsp;&nbsp;+ Jenkins scripts can detect one or the other way? (Michael M)  
&nbsp;&nbsp;&nbsp;&nbsp;+ so we can seamlessly transition  
&nbsp;&nbsp;+ if we only merge main branch - need old github repos (Michael S)  
&nbsp;&nbsp;&nbsp;&nbsp;+ for building the old versions of COOL  
&nbsp;&nbsp;&nbsp;&nbsp;+ still need the separate core with submodules  
&nbsp;&nbsp;&nbsp;&nbsp;+ have this on gerrit.  
&nbsp;&nbsp;&nbsp;&nbsp;+ when checkout release branch from repo will get old online repo.  
&nbsp;&nbsp;+ start work tomorrow

\* Bug reporting  
&nbsp;&nbsp;+ continue using github issues for now for community bug reports  
&nbsp;&nbsp;&nbsp;&nbsp;until we work out what to do  
&nbsp;&nbsp;+ should we add a way to distinguish core issues ? (Darshan)  
&nbsp;&nbsp;&nbsp;&nbsp;+ will be the same thing (Michael M)  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ can tag with App-Windows/ etc. for that.

\* Removing Poppler (Michael S)  
&nbsp;&nbsp;+ seems we depend both on poppler and pdfium  
&nbsp;&nbsp;+ seems un-necessary as a duplication  
&nbsp;&nbsp;+ both tend to have a lot of security issues over time  
&nbsp;&nbsp;+ would be quite useful to reduce the number to one  
&nbsp;&nbsp;+ won't break anything (Andras)  
&nbsp;&nbsp;&nbsp;&nbsp;+ not configured in to begin with.  
&nbsp;&nbsp;=\> lets get rid of it.  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make pdfium the default  
&nbsp;&nbsp;+ Caolan did a chunk of work on pdfium import -\> draw  
&nbsp;&nbsp;+ Classic may still have poppler for a while (Andras)

\* TTT talks  
&nbsp;&nbsp;+ [TTT talks .ods - Nextcloud](https://staging-perf.eu.collaboraonline.com/nextcloud/index.php/s/geAKbYAg4GJagqe)

\* What's next  
&nbsp;&nbsp;+ Michael S  
&nbsp;&nbsp;&nbsp;&nbsp;+ reviewing patches and sitting in meetings, and some RTF issues  
&nbsp;&nbsp;+ Stephan  
&nbsp;&nbsp;&nbsp;&nbsp;+ COWASM and on/off-line transitions  
&nbsp;&nbsp;&nbsp;&nbsp;+ getting that into CODA-Q  
&nbsp;&nbsp;+ Samuel R  
&nbsp;&nbsp;&nbsp;&nbsp;+ trying to understand the code  
&nbsp;&nbsp;&nbsp;&nbsp;+ found bugs on PC - with COOL on Linux  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ trying to fix them  
&nbsp;&nbsp;+ Thibaut P  
&nbsp;&nbsp;&nbsp;&nbsp;+ curious about inner working of things  
&nbsp;&nbsp;+ Szymon  
&nbsp;&nbsp;&nbsp;&nbsp;+ trying to finish reviews  
&nbsp;&nbsp;&nbsp;&nbsp;+ back-ports for stable branches of perf. fixes  
&nbsp;&nbsp;+ Quikee  
&nbsp;&nbsp;&nbsp;&nbsp;+ cleaning up the code  
&nbsp;&nbsp;&nbsp;&nbsp;+ PDF primitives / renderer  
&nbsp;&nbsp;&nbsp;&nbsp;+ horrors with fonts  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ text-box issues with CODA  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ only in the flatpak - problem is  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Carlito is a different version in flatpak  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ some changes in the font that affects  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;paragraph spacing & slide layout.  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ have a solution - will be ok for the  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Carlito case - but ...  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ both fonts are ok - but wanted to move  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;some ascending/descending to a more  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;windows-compatible approach.  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ multiple tables in fonts - sometimes one  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is used, sometimes another, sometimes a  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;combination.  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ a general problem in editengine  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ fixing it may influence back-compat(?)  
&nbsp;&nbsp;+ Dennis F  
&nbsp;&nbsp;&nbsp;&nbsp;+ working on converting context-menus from jquery-based to  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;internal JSDialog - three more call-sites and we're done  
&nbsp;&nbsp;&nbsp;&nbsp;+ converting some JS -\> TS - some in review.  
&nbsp;&nbsp;+ Darshan  
&nbsp;&nbsp;&nbsp;&nbsp;+ bug on view-mode, D&D in view-mode changing the document  
&nbsp;&nbsp;&nbsp;&nbsp;+ should not be allowed in view mode - different from readonly  
&nbsp;&nbsp;+ Hubert  
&nbsp;&nbsp;&nbsp;&nbsp;+ just listening in to follow infra migration  
&nbsp;&nbsp;+ Michael M  
&nbsp;&nbsp;&nbsp;&nbsp;+ typing text, not code sadly.  
&nbsp;&nbsp;&nbsp;&nbsp;+ looking forward to having Miklos back.

---

<div class="post-metadata">

**Author:** ![ljo](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/ljo/32/2028_2.png) [@ljo](https://forum.collaboraonline.com/u/ljo)\
**Post date:** [April 8, 2026, 3:08pm UTC](https://forum.collaboraonline.com/t/tc-meeting-minutes/4581/2 "2026-04-08T15:08:00Z")

</div>

I unfortunately missed the meeting since the Mastodon post said 17 CEST. I will change my recurring calendar event …

---

<div class="post-metadata">

**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\
**Post date:** [April 9, 2026, 6:42am UTC](https://forum.collaboraonline.com/t/tc-meeting-minutes/4581/3 "2026-04-09T06:42:56Z")

</div>

Hi @ljo,

Sorry for the confusion. It’s that time of the year again, I forgot about the time change, which caused this mix-up. I’ve now updated the timings (CEST or CET based on the current timezone) on our community site.

Going forward, it will always be at 16:00 Berlin time, so there shouldn’t be any confusion in the future.

Thanks  
Darshan