<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Rename "kde5" VCL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125922#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Rename "kde5" VCL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125922">bug 125922</a> from <a class="email" href="mailto:m.weghorn@posteo.de" title="Michael Weghorn <m.weghorn@posteo.de>"> Michael Weghorn</a> <pre>@Nate: Can you give a hint how important it is from your respective to get it renamed for the kf5 life cycle? In reply to Michael Weghorn from <a href="show_bug.cgi?id=125922#c7">comment #7</a>) > But in case we rename it, I think it's better to rename it everywhere, since > I think it would be rather counter-produtive wrt the intent mentioned in the > initial report ("reduce confusion and improve consistency") to have it > called "kde5" at some places and "kf5" at others. Though another thought I had while thinking about it a little more in the last weeks was that if we rename it from "kde5" everywhere, this would require action at several levels, like * other developers, and config for builders like Jenkins/tinderboxes (if we change build option name) * distros, to take into account the new build option and library name(s) Given that, I currently see following options: 1) Rename everywhere + Consistency inside LO and with KDE project's naming for kf5 - most action required on different levels 2) Rename it in some places/keep old name around to some extent + consistent with KDE project's naming for kf5 in UI - inconsistent inside LO (different terms used), may be confusing 3) Keep name "kde5", rename with next major version + no effort at all for now - inconsistent with KDE project's naming until qt6/kf6 is there Any more ideas on this? (In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=125922#c10">comment #10</a>) > (In reply to Xisco Faulí from <a href="show_bug.cgi?id=125922#c9">comment #9</a>) > > @Michael, @jmux, should the topic be discussed in the ESC meeting ? > > Yeah - I just forgot about it the last two weeks. jmux: Are you taking the topic there? (I think it might just be fair if a person that's a bit more convinced than myself at the moment would suggest that...) @Nate: ESC call is public and everybody can join, so if you and/or others from KDE want to join, please do. :-) It takes place Thu, 16:00 CEST via Jitsi at [1]. [1] <a href="https://meet.jit.si/TDFESC">https://meet.jit.si/TDFESC</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>