The Document Foundation Redmine: Issueshttps://redmine.documentfoundation.org/https://redmine.documentfoundation.org/favicon.ico?16960560022019-10-07T08:21:14ZThe Document Foundation Redmine
Redmine Events - Task #2993 (New): emergency precautions for eventshttps://redmine.documentfoundation.org/issues/29932019-10-07T08:21:14ZFlorian Effenbergerfloeff@documentfoundation.org
<p>As shared by Marina, we want to have emergency precautions for future events (cf. her mail from July 17).<br />We should factor this in for the next CfL.</p> DE - Task #2984 (In Progress): Investigate German volunteering platformshttps://redmine.documentfoundation.org/issues/29842019-09-30T13:49:35ZMike Saundersmike.saunders@documentfoundation.org
<p>Ilmari has had success using VolunteerMatch to bring new people into the LibreOffice project, so let's try to recreate this on a local level. He has found some German volunteering platforms:</p>
<p><a class="external" href="https://www.youvo.org/">https://www.youvo.org/</a><br /><a class="external" href="https://www.gute-tat.de/">https://www.gute-tat.de/</a><br /><a class="external" href="https://vostel.de/de/">https://vostel.de/de/</a><br /><a class="external" href="https://letsact.de/">https://letsact.de/</a></p>
<p>As they're in German, I will investigate and see what are usable, taking advice from Ilmari on the way.</p> Release Engineering - Task #2943 (New): Announce pre-releases in the QA blog, Bugzilla, ReleaseNoteshttps://redmine.documentfoundation.org/issues/29432019-08-06T12:30:35ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>In order to get as much testing as possible, we announce pre-releases ( alpha1, beta1, beta1, RC1, RC2 and RC3 ) in the qa blog < <a class="external" href="https://qa.blog.documentfoundation.org/">https://qa.blog.documentfoundation.org/</a> >, Bugzilla, and the ReleaseNotes</p>
<p>Steps:<br />1. Create the release plan wiki page --> See <a class="external" href="https://redmine.documentfoundation.org/issues/2942#change-17290">https://redmine.documentfoundation.org/issues/2942#change-17290</a><br />2. Create the banner --> <a class="external" href="https://wiki.documentfoundation.org/QA/BugHuntingSession/Organization#LibreOffice_6.0_Testing_Series">https://wiki.documentfoundation.org/QA/BugHuntingSession/Organization#LibreOffice_6.0_Testing_Series</a>. E.g: <a class="external" href="https://wiki.documentfoundation.org/File:BHS_large_6.3_RC3.png">https://wiki.documentfoundation.org/File:BHS_large_6.3_RC3.png</a><br />3. Update <a class="external" href="https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases">https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases</a> with the correct links<br />4. Add [[File:BHS_large_6.3_RC3.png|600px|center|link=https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases]] to <a class="external" href="https://wiki.documentfoundation.org/ReleaseNotes/6.3">https://wiki.documentfoundation.org/ReleaseNotes/6.3</a> (Use versioning accordingly )<br />5. In Bugzilla, Go to "Administration - Parameters - General" and add</p>
<p><center><a href="<a class="external" href="https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases&quot;">https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases&quot;</a>><br /><img border="0" src="<a class="external" href="https://wiki.documentfoundation.org/images/7/7f/BHS_large_6.3_RC3.png&quot;">https://wiki.documentfoundation.org/images/7/7f/BHS_large_6.3_RC3.png&quot;</a> width="500" height="125"></a></center></p>
<p>to announcehtml (Use versioning accordingly )<br />6. Write a blog post in the QA blog. E.g: <a class="external" href="https://qa.blog.documentfoundation.org/2019/07/09/libreoffice-6-3-rc1-ready-for-testing/">https://qa.blog.documentfoundation.org/2019/07/09/libreoffice-6-3-rc1-ready-for-testing/</a> (Use versioning accordingly )</p>
<p>Before the final release, remove the banner from Bugzilla and the ReleaseNotes wiki page</p> Release Engineering - Task #2942 (New): Create ReleasePlan wiki pages before they are releasedhttps://redmine.documentfoundation.org/issues/29422019-08-06T12:15:31ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Every time a new pre-release or final release is created, its wiki page needs to be created as well. For instance, see: <a class="external" href="https://wiki.documentfoundation.org/Releases/6.3.0/RC2">https://wiki.documentfoundation.org/Releases/6.3.0/RC2</a></p>
<p>How to do it ( taking <a class="external" href="https://wiki.documentfoundation.org/Releases/6.3.0/RC2">https://wiki.documentfoundation.org/Releases/6.3.0/RC2</a> as a example):<br />1. Copy content from <a class="external" href="https://wiki.documentfoundation.org/Releases/6.2.0/RC2">https://wiki.documentfoundation.org/Releases/6.2.0/RC2</a> to <a class="external" href="https://wiki.documentfoundation.org/Releases/6.3.0/RC2">https://wiki.documentfoundation.org/Releases/6.3.0/RC2</a><br />2. Replace all 6.2.0 with 6.3.0<br />3. Change [[Category:Release|6202]] to [[Category:Release|6302]]<br />4. Remove content from 'List of fixed bugs' section<br />5. Get the new content from <a class="external" href="https://dev-builds.libreoffice.org/pre-releases/src/">https://dev-builds.libreoffice.org/pre-releases/src/</a>' ( for 6.3.0 RC2 the file is called 'bugs-libreoffice-6-3-0-release-6.3.0.2.wiki' )</p>
if it doesn't exists, you can create it yourself.
<ol>
<li>Go to the local repository</li>
<li>./g pull -r</li>
<li>./g fetch --tags</li>
<li>mkdir outdir</li>
<li>cd outdir</li>
<li>bootstrapdir=/home/xisco/releases/</li>
<li>export lo_tag=6.3.0.2</li>
<li>export lo_tag_last=6.3.0.1</li>
<li>$bootstrapdir/bin/lo-commit-stat --cherry --commits --bugs --bugs-wiki --bugs-changelog --log-suffix=release-${vendor_use:+libreoffice-}$lo_tag $bootstrapdir libreoffice-$lo_tag_last libreoffice-$lo_tag</li>
<li>'bugs-libreoffice-6-3-0-release-6.3.0.2.wiki' will be created</li>
</ol>
<p>6. Update the link in the Translations section</p> Marketing - Task #2932 (Closed): Map of Journalists on TDF Databasehttps://redmine.documentfoundation.org/issues/29322019-07-24T07:26:10ZFlorian Effenbergerfloeff@documentfoundation.org
<p>As discussed during our in-person meeting in Munich, we want to make a map of journalists in phpList, to encourage PR translations</p> DE - Task #2912 (In Progress): DE-Veranstaltungen 2022https://redmine.documentfoundation.org/issues/29122019-06-28T08:01:28ZKlaus-Jürgen Weghornk-j@libreoffice.org
<p>Wir können hier mal Ideen für DE-Veranstaltungen 2020 sammeln.</p> DE - Task #2877 (Rejected): Bilder für Landing Pagehttps://redmine.documentfoundation.org/issues/28772019-05-13T12:37:58ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Eine Aufgabe aus dem DE-Meeting in Essen ist, die derzeitige Landing Page öfters zu aktualisieren und die Bildergalerie ersetzen mit Blog-Highlights/Events</p> DE - Task #2873 (New): DE-Blog mit Inhalten befüllen, Twitter und Telegramhttps://redmine.documentfoundation.org/issues/28732019-05-13T12:29:26ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Eine Aufgabe aus dem DE-Meeting in Essen ist das regelmäßige Befüllen des DE-Blogs mit Inhalten und das Posten auf Twitter und Telegram</p> Infrastructure - Task #2679 (Closed): mailing list statisticshttps://redmine.documentfoundation.org/issues/26792018-11-26T14:42:35ZFlorian Effenbergerfloeff@documentfoundation.org
<p>As per our team meeting in Tirana, we want to</p>
<ul>
<li>regularly check subscribers for public lists</li>
<li>find out which lists are subscribed the most</li>
</ul>
<p>to see how we can improve our communication channels</p> Infrastructure - Task #2653 (In Progress): Publish the monthly reports to the QA bloghttps://redmine.documentfoundation.org/issues/26532018-09-10T17:47:39ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>How to proceed:<br />1. Execute <a href="https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/qa/createBlogReport.py" class="external">createBlogReport script</a>.<br />Sample: August 2018 -> ./createBlogReport.py 2018-08-01 2018-09-01<br />2. Upload the charts created in /tmp to the QA Blog's admin website<br />3. Copy the text from /tmp/blogReport.txt into a new blog post<br />4. Replace PATH_HERE by the path to the images uploaded in step 2<br />5. Check the development activities in git and the release notes and add them to the 'General Activities' section<br />6. Add comments from <a class="external" href="https://nextcloud.documentfoundation.org/s/2qbepFYXXan4ief">https://nextcloud.documentfoundation.org/s/2qbepFYXXan4ief</a> to the 'General Activities' section</p> Infrastructure - Task #2638 (In Progress): Badges for the community (OpenBadges)https://redmine.documentfoundation.org/issues/26382018-08-14T11:25:23ZSophie Gautiergautier.sophie@gmail.com
<p>This task is to follow-up the setting of badges and OpenBadges for the community. Attached is a document explaining what we want to achieve using Fedora badges and OpenBadges technologies.</p> Marketing - Task #2560 (Rejected): A/B testing for Google Play listing of LibreOffice Viewerhttps://redmine.documentfoundation.org/issues/25602018-03-13T15:08:38ZMike Saundersmike.saunders@documentfoundation.org
<p>We can do A/B testing using "store listing experiments" with our Android app. We can test variants of the store listing's graphics and text, experiment with the order of screenshots, and make other changes. This is all backed with proper data from Google Play.</p>
<p>This may be worth investigating at some point, when the app is more polished. Further reading: <a class="external" href="https://developer.android.com/distribute/best-practices/grow/store-listing-experiments.html">https://developer.android.com/distribute/best-practices/grow/store-listing-experiments.html</a></p> Design - Task #2498 (In Progress): Commenting on tickets that needs UX advicehttps://redmine.documentfoundation.org/issues/24982018-01-19T11:47:13ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>Supporting QA and development with advices on tickets<br />The number of open tickets should be close to zero so that in the design meeting only new topics are discussed</p>
<p><a class="external" href="https://bugs.documentfoundation.org/report.cgi?keywords=needsUXEval%2C%20&keywords_type=allwords&resolution=---&x_axis_field=bug_severity&y_axis_field=component&format=table&action=wrap&saved_report_id=24">https://bugs.documentfoundation.org/report.cgi?keywords=needsUXEval%2C%20&keywords_type=allwords&resolution=---&x_axis_field=bug_severity&y_axis_field=component&format=table&action=wrap&saved_report_id=24</a></p> Design - Task #2497 (In Progress): Design meetinghttps://redmine.documentfoundation.org/issues/24972018-01-19T11:44:32ZHeiko Tietzeheiko.tietze@documentfoundation.org
<p>Weekly meeting to discuss design and UX topics, mostly based on requests on Bugzilla</p>
<p>Time: Wednesday, 7pm UTC / 20:00 CET<br />Minutes: <a class="external" href="https://pad.documentfoundation.org/p/design">https://pad.documentfoundation.org/p/design</a><br />Jitsi: <a class="external" href="https://meet.jit.si/LibreOfficeDesign">https://meet.jit.si/LibreOfficeDesign</a></p> Marketing - Task #2415 (In Progress): make regular "This Month in LibreOffice" posts on the bloghttps://redmine.documentfoundation.org/issues/24152017-11-20T15:57:37ZMike Saundersmike.saunders@documentfoundation.org
<p>An idea came up a while back to do monthly recaps (ie at the end of each month) summarising what has happened inside the LO project and community. It wouldn't be very long but be useful for people outside of the project to see what progress is being made. Ideas for content:</p>
<ul>
<li>Links to release announcements (if any) made in the month</li>
<li>New features that were added for the next release, with screenshots</li>
<li>Updates about events</li>
<li>Thanks to new contributors</li>
</ul>
<p>It's important to give it a good name. "This Month in LibreOffice" might get mixed up with the "Month of LibreOffice". Some other ideas:</p>
<ul>
<li>LibreOffice catch-up, $MONTH $YEAR</li>
<li>What's going on in LibreOffice, $MONTH YEAR</li>
</ul>
<p>Setting initial target as this for Q4, to do the first in December. After that, if it works I'll set to recurring.</p>