The Document Foundation Redmine: Issueshttps://redmine.documentfoundation.org/https://redmine.documentfoundation.org/favicon.ico?16960560022019-09-17T12:33:02ZThe Document Foundation Redmine
Redmine Marketing - Task #2963 (In Progress): Breakdown on Recurring Donationshttps://redmine.documentfoundation.org/issues/29632019-09-17T12:33:02ZFlorian Effenbergerfloeff@documentfoundation.org
We want to get a breakdown on recurring donations (at PayPal and Stripe):
<ul>
<li>monthly</li>
<li>quarterly</li>
<li>annually</li>
</ul>
<p>Given the costs involved, we should try to move from monthly to quarterly, and knowing the breakdown would help a lot</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> 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 #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 #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> 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> Release Engineering - Task #2351 (In Progress): Bugzilla's gardening taskshttps://redmine.documentfoundation.org/issues/23512017-08-21T10:22:35ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
Automated taks <br />See <a class="external" href="https://wiki.documentfoundation.org/QA/Bugzilla/AutomatedTasks">https://wiki.documentfoundation.org/QA/Bugzilla/AutomatedTasks</a>
Manual tasks <br />See: <a class="external" href="https://wiki.documentfoundation.org/QA/Bugzilla/Gardening">https://wiki.documentfoundation.org/QA/Bugzilla/Gardening</a> Release Engineering - Task #2350 (In Progress): Clean deletionrequest componenthttps://redmine.documentfoundation.org/issues/23502017-08-21T09:33:40ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Steps:<br />1. Enable allowbugdeletion in Administration -> Parameters -> Administrative Policies.<br />2. Once you have added all the soon to be deleted bugs to your trash component go back to the component list in the administration page (Administration -> Products -> LibreOffice -> Edit Components). You should see an “Action” column on the far right of the table with all your components with a Delete link. Find the deletionrequest component and click the associated “Delete” link.<br />3. Confirm the deletion.<br />4. Disable allowbugdeletion in Administration -> Parameters -> Administrative Policies</p>
<p>More Information: <a class="external" href="https://devzing.com/blog/index.php/how-to-delete-bugs-from-bugzilla/">https://devzing.com/blog/index.php/how-to-delete-bugs-from-bugzilla/</a></p> Documentation - Task #2263 (In Progress): documentation callshttps://redmine.documentfoundation.org/issues/22632017-06-12T13:41:13ZFlorian Effenbergerfloeff@documentfoundation.org
<p>There's a weekly documentation call<br />Wednesdays, 1930 Berlin time, via Jitsi</p> Release Engineering - Task #1481 (In Progress): Bibisect repositorieshttps://redmine.documentfoundation.org/issues/14812015-09-21T12:51:25ZFlorian Effenbergerfloeff@documentfoundation.org
<p>We want to have our own TDF-provided Bibisect repositories.<br />The scope of this ticket is to regularly produce Bibisect repositories for</p>
<ul>
<li>Windows</li>
<li>Linux</li>
<li>Mac OS X</li>
</ul>
<p>with all the flavors and branches we need. These should be produced by TDF staff, on officially TDF-hosted machines. The platform should be maintained by infra, while the Bibisect repositories should be managed by assignee.</p>
<p>How to setup a new repository ( using lode )<br />- ./setup --help<br />- ./setup --new bibisect/coreXX<br />- mv /dev/bibisect/coreXX to bibisect/<br />- copy autogen.input from previous builds to the current one<br />- copy old .bibisect/loXX to .bibisect/loYY<br />- edit the new loYY<br />- go to jenkins - new item - copy existing item ( lo_bibisect_XX_Y_Y )</p>
<p>How to setup a new repository in gerrit<br />- <a class="external" href="https://gerrit.libreoffice.org/#/admin/create-project/">https://gerrit.libreoffice.org/#/admin/create-project/</a><br />- Write project name ( use these as reference --> <a class="external" href="https://gerrit.libreoffice.org/#/admin/projects/?filter=bibisect">https://gerrit.libreoffice.org/#/admin/projects/?filter=bibisect</a> )<br />- Change rights to 'Inherit from Dev-ACL-Template'<br />- ssh <a class="email" href="mailto:gerrit@gerrit.libreoffice.org">gerrit@gerrit.libreoffice.org</a> <del>p 22<br /></del> cd /srv/repositories/<new repository name><br />- copy config file from another existing repository<br />- Edit the config file<br />- touch git-daemon-export-ok<br />- git remote update ( While the origin repo is not being built )</p>
<p>Use this script < <a class="external" href="https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/bibisect/buildReleasesRepository.sh">https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/bibisect/buildReleasesRepository.sh</a> > for building bibisect-linux-64-releases</p> DE - Task #1459 (In Progress): deutschsprachige Community-TelKoshttps://redmine.documentfoundation.org/issues/14592015-09-17T07:41:00ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Einmal im Monat führen wir eine deutschsprachige Community-Telefonkonferenz durch, um uns über aktuelle Ereignisse und anstehende Veranstaltungen auszutauschen.</p>
<p>Termin ist alternierend jeweils der vierte Mittwoch im Monat um 19 Uhr, gefolgt von jeweils dem vierten Donnerstag im Monat um 18 Uhr</p>
Für die Telefonkonferenzen müssen wir:
<ul>
<li>ca. eine Woche vorher eine Erinnerung an discuss@de schicken</li>
<li>die Agenda unter <a class="external" href="http://pad.documentfoundation.org/p/de_discuss">http://pad.documentfoundation.org/p/de_discuss</a> erstellen</li>
<li>am Abend der Telefonkonferenz den Raum bei talkyoo öffnen (Florian hat die Zugangsdaten)</li>
<li>ein kleines Protokoll schreiben</li>
</ul> Infrastructure - Task #1402 (In Progress): Bugzilla maintenancehttps://redmine.documentfoundation.org/issues/14022015-08-18T10:05:46ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Our Bugzilla instance needs regular maintenance. This involves:</p>
<ul>
<li>updating to most recent minor/micro version</li>
<li>dealing with locked accounts</li>
<li>helping new users to confirm their accounts</li>
<li>managing user rights</li>
</ul> Infrastructure - Task #964 (In Progress): Bugzilla removal of old LibreOffice versionshttps://redmine.documentfoundation.org/issues/9642014-12-10T16:33:11ZRobinson Tryonqubit@runcibility.com
<p>6 months after EOL of a release branch, we clean the Bugzilla version dropdown and remove all the RC's, leaving just the final releases.</p>
<p>Next due dates:</p>
<ul>
<li>4.3 EOL is May 27, 2015, so our due date is November 27, 2015, see <a class="external" href="https://wiki.documentfoundation.org/ReleasePlan/4.3#End_of_Life">https://wiki.documentfoundation.org/ReleasePlan/4.3#End_of_Life</a></li>
<li>4.4 EOL is November 18, 2015, so our due date is May 18, 2016, see <a class="external" href="https://wiki.documentfoundation.org/ReleasePlan/4.4#End_of_Life">https://wiki.documentfoundation.org/ReleasePlan/4.4#End_of_Life</a></li>
<li>4.5 EOL is May 29, 2016, so our due date is November 29, 2016, see <a class="external" href="https://wiki.documentfoundation.org/ReleasePlan/4.5#End_of_Life">https://wiki.documentfoundation.org/ReleasePlan/4.5#End_of_Life</a></li>
</ul>