<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Provide arm64 or x86-64/arm64 Universal Binary builds for macOS on Apple Silicon" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138192#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Provide arm64 or x86-64/arm64 Universal Binary builds for macOS on Apple Silicon" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138192">bug 138192</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>@Bouvjaga Not directed to you personally (more mentor question). You might know question. People are working on arm64 support (see <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Support Apple Silicon (arm64) on macOS" href="show_bug.cgi?id=138191#c5">bug 138191 comment 5</a>) and Apple Silicon. It's even running already as far I understand. However I don't know they lines well enough within TDF. This is not a pure infra, pure dev call. Does TDF want to support even more eco-systems, is it worth costs work. If not will this maybe result in a master builds server somewhere else. See Online. This includes they how to handle making returns topic. And internal division/directionlessness drives me pretty nuts. As there is no consent at any level BoD/MC/Members. While the world keeps moving on. I fear LibreOffice by TDF will be hollowed out from within. I don't see any status quo. But more a (partly) self-inflicted, self-full filling, fork in progress. I do see building blocks already. If you can't join the, eat them :-). So LibreOffice attempting to 'eat' OpenOffice (get them on board), while LibreOffice is eaten again?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>