The Document Foundation Redmine: Issueshttps://redmine.documentfoundation.org/https://redmine.documentfoundation.org/favicon.ico?16960560022023-05-12T07:57:17ZThe Document Foundation Redmine
Redmine Extensions - Task #3655 (New): Tight integration not updatedhttps://redmine.documentfoundation.org/issues/36552023-05-12T07:57:17ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>Extensions can be tagged and appear in the program-internal search. For example, tools > options > language > writing aids: more dictionaries. However, recently uploaded extensions are not listed. For example the "Oxford English Spellchecker".</p> Extensions - Task #3630 (Feedback): Assigning an unclaimed extension clears all contenthttps://redmine.documentfoundation.org/issues/36302022-11-18T07:55:35ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>1. Search for an existing extension, like "Maths for knitted Socks" <br />2. Set the maintainer to the correct address<br />(2a. add proper tags like Calc in the example; not sure if this has an impact)<br />3. Save<br />=> looks good but on the admin overview you see that the name, short summary, and the detailed description are gone</p> Extensions - Task #3612 (Resolved): Special tags for filtering in LibreOffice tight extensionshttps://redmine.documentfoundation.org/issues/36122022-07-27T17:15:57ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>Follow-up to rdm#3428.</p>
<p>We should... "either have another type of tag (one for the extensions site and the other for the application) or have an option with the tag to show it in the extensions site filters or not (we would need to define two tags in this case like "Configuration" and "Font Replacement", where only the first one is shown).</p> Extensions - Task #3608 (New): The login link asks to login once againhttps://redmine.documentfoundation.org/issues/36082022-06-15T09:35:13ZJean-Francois Nifeneckerjean-francois.nifenecker@sud-ouest.org
<p>Hi,</p>
<p>when an author wants to login, there's a 'Login' entry at the top of the Extensions page.</p>
<p>Clicking this entry brings to a page where one has to click 'Login' once again using a 'Login' button:<br /><a class="external" href="https://extensions.libreoffice.org/Security/login?BackURL=%2Fadmin%2Fpages%2F">https://extensions.libreoffice.org/Security/login?BackURL=%2Fadmin%2Fpages%2F</a><br />Well, I did say I want to login. Why on earth have I to repeat it?</p>
<p>I'd suggest that the first 'Login' entry directly leads to the actual login page (<a class="external" href="https://extensions.libreoffice.org/admin/extensions/">https://extensions.libreoffice.org/admin/extensions/</a>). This woul make a clearer and simpler UI.</p>
<p>Thanks,<br />-- <br />Jean6francois Nifenecker</p> Extensions - Task #3607 (New): Localized extensions pageshttps://redmine.documentfoundation.org/issues/36072022-06-15T08:52:57ZJean-Francois Nifeneckerjean-francois.nifenecker@sud-ouest.org
<p>Hi,</p>
<p>(follow-up on ticket <a class="issue tracker-4 status-5 priority-2 priority-default closed" title="Task: Localized Extension Site Availability (Closed)" href="https://redmine.documentfoundation.org/issues/3260">#3260</a>, now closed)</p>
<p>the extensions pages seem to not be localized. Ex: coming from the FR main site (<a class="external" href="https://fr.libreoffice.org/">https://fr.libreoffice.org/</a>) using an FR OS and browser, you get an English-speaking extensions website (path: Découvrir > Modèles et extensions, LibreOffice Extensions link). The FR user is then dropped at: <a class="external" href="https://extensions.libreoffice.org/">https://extensions.libreoffice.org/</a> where everything is in English.</p>
<p>This behaviour refrains many non-EN speaking people to simply browse pages they don't understand.</p>
<p>For instance, are there FR-localized extensions pages? The referenced ticket above suggests there are, but I couldn't find any. Adding /fr to the main extensions URL is accepted but everything remains in EN.</p>
<p>Best,<br />-- <br />Jean-Francois Nifenecker</p> Extensions - Task #3606 (New): Allow having extensions projects "on hold"https://redmine.documentfoundation.org/issues/36062022-06-15T08:25:22ZJean-Francois Nifeneckerjean-francois.nifenecker@sud-ouest.org
<p>Hi again,</p>
<p>An extension author might want/need to enter a (new) extension information progressively. That is, s-he might not have time to enter all and every details at once.</p>
<p>As I understand things, once you start creating an extension, you've got to go the whole process route, otherwise you may lose the previously entered details. For instance, I may create an extension infrastructure but not add the .oxt file yet. As of current process, this doesn't stop the (inexistant) "extension" to be updated from the 'Draft' status to 'Published'. Thus the UI is... well... "strange": users can read a description but there's nothing to download.</p>
<p>As an author, I'd prefer having the following states: 'Draft' (remains as such as long as the author decides) -> 'Ready' (the administrator is allowed to check and publish) -> 'Published'</p>
<p>Best,<br />-- <br />Jean-Francois Nifenecker</p> Infrastructure - Task #3584 (In Progress): Strings containing suggestions take long time to savehttps://redmine.documentfoundation.org/issues/35842022-05-09T13:48:06ZSophie Gautiergautier.sophie@gmail.com
<p>Reporting this one encountered by Leo and I think related to:<br /><a class="external" href="https://github.com/WeblateOrg/weblate/issues/7300">https://github.com/WeblateOrg/weblate/issues/7300</a><br />Mainstream has closed the bug as being an issue on our side.<br />--------------------------------</p>
<p>When I started, the problem seemed to have been resolved, but at the 10th string problems arose again:</p>
<p>- nl/helpcontent2/source/text/swriter/01.po, tekenreeks 76</p>
<pre><code>Context</code></pre>
<p>02110000.xhp<br />par_id3149802<br />help.text</p>
<pre><code>Locatie van bronomschrijving</code></pre>
<p>uXgCi</p>
<pre><code>Locatie van brontekenreeks</code></pre>
<p>02110000.xhp <<a class="external" href="https://git.libreoffice.org/help/+/libreoffice-7-2/source/text/swriter/01/02110000.xhp#0">https://git.libreoffice.org/help/+/libreoffice-7-2/source/text/swriter/01/02110000.xhp#0</a>></p>
<p>There was a suggestion, I modified it and then it took 22 seconds before being saved.</p>
<p>- nl/helpcontent2/source/text/shared.po, tekenreeks 215</p>
<pre><code>Context</code></pre>
<p>main0650.xhp<br />par_id3153822<br />help.text</p>
<pre><code>Locatie van bronomschrijving</code></pre>
<p>ApwuB</p>
<pre><code>Locatie van brontekenreeks</code></pre>
<p>main0650.xhp <<a class="external" href="https://git.libreoffice.org/help/+/libreoffice-7-2/source/text/shared/main0650.xhp#0">https://git.libreoffice.org/help/+/libreoffice-7-2/source/text/shared/main0650.xhp#0</a>><br />------------------------------------</p>
<p>Could you have a look? let me know if we should reopen the github issue instead.</p> Infrastructure - Task #3442 (Feedback): rename "master" branch in core.git to new git defaulthttps://redmine.documentfoundation.org/issues/34422021-01-14T16:22:20ZMichael Stahl
<p>as discussed in ESC today:</p>
<ul>
<li>rename master to main in git? (Stephan)<br /> + LLVM already did this<br /> + how far should we go there? (Cloph)<br /> + do we look bad if we don’t do anything? (Stephan)<br /> + when creating a new branch: (Cloph)<br /> + IRC notify, tinderbox, .gitreview, documentation (wiki e.g.) (Sophie)<br /> + dashboard data may be tricky (Cloph)<br /> + in favor of doing it (Michael S)<br />AI: + file a TDF infra ticket on redmine (Michael S)<br /> + to get input from infra<br /> + prefer to get 7.1 out of the door first (Cloph)</li>
</ul>
<p>so this mainly requires adapting infra things like CI etc. to the new branch name, but hopefully the effort required should be rather small (and of course it's not the most urgent task in the world).</p>
<p>for motivation see:<br /><a class="external" href="https://tools.ietf.org/html/draft-knodel-terminology-02">https://tools.ietf.org/html/draft-knodel-terminology-02</a><br /><a class="external" href="https://github.com/github/renaming">https://github.com/github/renaming</a></p> Extensions - Task #3402 (New): Indicate that the last image uploaded will be the primary imagehttps://redmine.documentfoundation.org/issues/34022020-10-02T06:57:16ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>Probably via frame around the image; would be nice to change the primary or to change the order.</p> Extensions - Task #3275 (In Progress): No notification for feedback at the extensionhttps://redmine.documentfoundation.org/issues/32752020-07-17T08:33:53ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>People comment on the extension but I don't receive a notification, for example <a class="external" href="https://extensions.libreoffice.org/en/extensions/show/galaxy-icon-theme">https://extensions.libreoffice.org/en/extensions/show/galaxy-icon-theme</a></p>
<p>It's crucial to have a working communication channel => high priority.</p> Infrastructure - Task #3262 (New): make gimli (crashreports) more backup-friendlyhttps://redmine.documentfoundation.org/issues/32622020-07-13T14:57:53ZChristian Lohmaiercloph@documentfoundation.org
<p>gimli's backup is over 15 Million files, biggest chunk of that are static/non-changing logfiles from crashreport runs.<br />There is no point in hardlinking those 15 million files over and over, more efficient would be to backup archives (tarball/zip) of those runs with all logs in a single file and ignore the webdirectory with the extracted files.</p>
<p>Biggest problem with current setup is that a backup run doesn't complete within a single day, and of course it causes unnecessary I/O load on the VM as well.</p> Infrastructure - Task #1701 (In Progress): Silverstripe maintenance and updateshttps://redmine.documentfoundation.org/issues/17012016-01-13T14:28:55ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Our Silverstripe needs regular maintenance and updates, including:</p>
<ul>
<li>software updates</li>
<li>fixing issues</li>
<li>creating new users</li>
<li>removing people from CMS e-mails</li>
</ul>