The Document Foundation Redmine: Issueshttps://redmine.documentfoundation.org/https://redmine.documentfoundation.org/favicon.ico?16960560022015-09-01T08:11:04ZThe Document Foundation Redmine
Redmine Release Engineering - Task #1425 (Closed): Release Managementhttps://redmine.documentfoundation.org/issues/14252015-09-01T08:11:04ZFlorian Effenbergerfloeff@documentfoundation.org
<p>We do regular</p>
<ul>
<li>alphas</li>
<li>betas</li>
<li>release candidates</li>
<li>releases</li>
</ul>
<p>of</p>
<ul>
<li>LibreOffice
<ul>
<li>x86 and x64</li>
<li>for Windows, Linux and Mac OS X</li>
</ul>
</li>
<li>LibreOffice Viewer for Android <strong>incl. publication at F-Droid</strong></li>
<li>LibreOffice Impress Remote for Android <strong>incl. publication at F-Droid</strong></li>
<li>LibreOffice Impress Remote for iOS</li>
</ul>
<p>as well as distribution of</p>
<ul>
<li>LibreOffice Portable for Windows</li>
</ul> Marketing - Task #1416 (In Progress): Press Clippingshttps://redmine.documentfoundation.org/issues/14162015-08-26T11:28:03ZFlorian Effenbergerfloeff@documentfoundation.org
<p>With LibreOffice, TDF and its projects mentioned in various media around the globe, we need to do regular collection of press clippings.<br />Goal of this task is to have them collected at least internally for use when needed, if not even for sharing with the community.</p>
<p>Tasks involve:</p>
<ul>
<li>collect clippings around the globe in various languages</li>
<li>add them to a database or to-be-defined tool</li>
<li>share them with the private group of marketeers</li>
<li>extract numbers and statistics to measure how we're doing</li>
<li>if required, try to get permission and clarify attribution for selected clippings to make them public</li>
</ul> Release Engineering - Task #1403 (In Progress): QA and bughuntinghttps://redmine.documentfoundation.org/issues/14032015-08-18T10:22:00ZFlorian Effenbergerfloeff@documentfoundation.org
<p>We regularly do QA and bughunting. This includes:</p>
<ul>
<li>stress testing LibreOffice development builds and pre-releases (alpha, beta, RCs) on multiple platforms, x86 and x64 architecture, including Android viewer, Android Remote and iOS Remote</li>
<li>confirming bugs and fixes, with bibisecting when necessary</li>
<li>triaging unconfirmed bugs on master</li>
<li>running test builds/daily builds/snapshots (“master”) to try to find regressions early in release cycles</li>
<li>keeping a continuous overview and reporting on the state and progress of LibreOffice QA as seen on its bug trackers, mailing lists, and other communication channels (e.g. IRC)</li>
</ul>
<p>To make the whole process scale well, keep in mind the following best practice:</p>
<ol>
<li>Prioritizing (do not waste too much time on this)
<ol>
<li>go through bugs with status NEW in reverse chronological order (to catch recently reported issues first)</li>
<li>quickly <strong>skim</strong> title and comments (give a cursory glance!)</li>
<li>then decide on the priority, identifying crashes, data loss etc.</li>
<li>add a quick comment about the change</li>
</ol>
</li>
<li>Tagging (without the need to triage fully)
<ol>
<li>Identify areas where tagging is missing (e.g. regressions need bibisectRequests on them unless it is specifically requested to not have that)</li>
</ol>
</li>
<li>Documentation
<ol>
<li>Updating documentation as needed pertaining to QA related tools and recommended "best practices" </li>
</ol>
</li>
<li>Onboarding of volunteers
<ol>
<li>Regularly reach out to different channels to grow the team</li>
<li>Document what was done, what works, set goals (e.g. number of new volunteers per month)</li>
<li>Use social media, triaging (leaving a comment with an invitation to join), mailing lists (reaching out on other mailing lists)</li>
<li>NB: Recruitment through in person events should be the exception, and we should frequent events where concrete new members are gained more often</li>
</ol></li>
</ol> 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 #1397 (Closed): EasyHacks compilationhttps://redmine.documentfoundation.org/issues/13972015-08-13T10:10:25ZFlorian Effenbergerfloeff@documentfoundation.org
<p>In time for the LibreOffice Conference, we should compile a list of EasyHacks to be presented during your talk. A starter can be found in Redmine by filtering for the specific tag.</p> Infrastructure - Task #1395 (In Progress): infra callhttps://redmine.documentfoundation.org/issues/13952015-08-13T10:02:37ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Every 3rd Tuesday every month at 1830 Berlin time, we will have an admin meeting call</p>
<ol>
<li>We need to have an agenda developed in time, some ideas are added at <a class="external" href="http://pad.documentfoundation.org/p/infra">http://pad.documentfoundation.org/p/infra</a></li>
<li>An invitation needs to be sent to the project@ and website@ lists in time, i.e. ideally <strong>one or two weeks in advance</strong></li>
<li>Individual admin team members as well as interested volunteers should be invited via private mail in addition</li>
<li>No later than <strong>three days after the call</strong>, send out the minutes to the project@ and website@ lists</li>
</ol> Infrastructure - Task #1389 (Closed): license renewal for IntelliJ and PHPStormhttps://redmine.documentfoundation.org/issues/13892015-08-12T13:37:51ZFlorian Effenbergerfloeff@documentfoundation.org
<p>The free licenses for IntelliJ and PHPStorm need renewal once a year, shortly before they expire.<br />Contact is <a class="email" href="mailto:opensource@jetbrains.com">opensource@jetbrains.com</a>, mentioning our existing license ID. From 2015 on, we might need to use their webform instead.</p> Marketing - Task #1376 (In Progress): month of LibreOffice contributionhttps://redmine.documentfoundation.org/issues/13762015-07-24T08:46:05ZBjoern Michaelsenbjoern.michaelsen-tdf@libreoffice.org
<p>To foster our social media coverage, create more visibility for procut and project, and have better inclusion of contributors, we want to have social media banner & badge campaigns.</p>
<p>All campaigns should provide:</p>
<ul>
<li>a tagline</li>
<li>a small banner or badge for use on social media or blogs (proper license is crucial)</li>
<li>a fixed "start" date for the campaign to focus the initial impact, including a possible day of week in the month (e.g. Patch Tuesday)</li>
</ul>
<p>So keep this alive and to not wear out contributors/oversaturate channels, these campaign should not happen more often than once a month and not less often than every two months. It might be a task for the marketing intern to drive this forward on a regular basis, with internally planning this every month, to be able to skip every once in a while.</p>
Here are some ideas for taglines/topics from previous months, some of them can easily be re-used:
<ul>
<li>August: "I contributed to LibreOffice 5.0" <<LibreOffice 5.0 banner>></li>
<li>September: "I am attending the #LibreOffice conference in #Aarhus on Sept. 23-25" <<Aarhus pics>></li>
<li>October: "I will (remotely) attend the #LibreOffice Hackfest in Hamburg on Oct. 23-25" <<Hamburg pics>></li>
<li>November: "Proud member of the meritocratic electorate of LibreOffice" <<TDF logo>> (Board elections)</li>
<li>December: "I will take part in the LibreOffice Bug Hunting Sessions for LibreOffice 5.1" <<Bug picture>></li>
<li>January: "I support/am part of the LibreOffice FOSDEM 2016 team." </li>
<li>February: "I contributed to LibreOffice 5.1"</li>
</ul> Marketing - Task #1333 (In Progress): event calendarhttps://redmine.documentfoundation.org/issues/13332015-06-22T06:05:45ZFlorian Effenbergerfloeff@documentfoundation.org
<p>We do have an events calendar at <a class="external" href="https://wiki.documentfoundation.org/Events">https://wiki.documentfoundation.org/Events</a> and <a class="external" href="https://wiki.documentfoundation.org/EventsCalendar">https://wiki.documentfoundation.org/EventsCalendar</a><br />This calendar needs regular updating</p>
<p>Information for events where at least one LibreOffice representative</p>
<ul>
<li>attends, or</li>
<li>gives a talk, or</li>
<li>joins a panel discussion, or</li>
<li>staffs a booth</li>
</ul>
<p>need to be compiled. Data required is:</p>
<ul>
<li>country, citiy and location of the event</li>
<li>event's name</li>
<li>organizer(s) on behalf of the LibreOffice project</li>
<li>attendees on behalf of the LibreOffice project</li>
<li>URL of conference</li>
<li>URL of slideware/videos</li>
</ul>
<p>Optionally, we can split up into various categories and tags, e.g. by</p>
<ul>
<li>continent</li>
<li>country</li>
<li>size</li>
<li>audience</li>
<li>category: conference, trade show, informal meeting</li>
</ul>
<p>Optionally, we can also collect dates for Call for Papers (CfP), Call for Booths (CfB), and Call for Locations (CfL).</p> Infrastructure - Task #1278 (Closed): license renewal for PyCharmhttps://redmine.documentfoundation.org/issues/12782015-05-25T13:39:47ZFlorian Effenbergerfloeff@documentfoundation.org
<p>The free licenses for PyCharm needs renewal once a year, shortly before it expires.<br />Contact is <a class="email" href="mailto:opensource@jetbrains.com">opensource@jetbrains.com</a>, mentioning our existing license ID. From 2015 on, we might need to use their webform instead.</p> 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> Infrastructure - Task #942 (Rejected): StartSSL renewalshttps://redmine.documentfoundation.org/issues/9422014-12-02T10:11:33ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Our StartSSL certificates and validations need to be renewed on a regular basis.</p>
<ul>
<li>personal validation: 2017-01-27</li>
<li>organization validation: 2017-02-18</li>
<li>EV code signing certificate: 2018-05-31</li>
<li>documentfoundation.org certificate: 2019-03-24</li>
<li>libreoffice.org certificate: 2019-03-24</li>
</ul>
<p>Especially the EV validation takes some time upfront, as legal documents and signature need to be provided.</p> Infrastructure - Task #894 (In Progress): libreoffice.org adress managementhttps://redmine.documentfoundation.org/issues/8942014-11-12T13:19:42ZFlorian Effenbergerfloeff@documentfoundation.org
<p>Shortly after the begin of every quarter, when the new members have been approved, their libreoffice.org addresses need to be set-up, alongside with a welcome mail</p>
Steps:
<ol>
<li>wait for members to be subscribed to the tdf-members@ lists (<a class="issue tracker-4 status-2 priority-2 priority-default overdue" title="Task: update tdf-members@ subscriber list (In Progress)" href="https://redmine.documentfoundation.org/issues/893">#893</a>)</li>
<li>send e-mail to members and point them to <a class="external" href="https://wiki.documentfoundation.org/Website/MailAccounts">https://wiki.documentfoundation.org/Website/MailAccounts</a></li>
<li>wait for members confirming the legal template with an e-mail to legal@</li>
<li>set up the addresses</li>
<li>add the addresses into the spreadsheet</li>
</ol> Infrastructure - Task #893 (In Progress): update tdf-members@ subscriber listhttps://redmine.documentfoundation.org/issues/8932014-11-12T13:19:25ZFlorian Effenbergerfloeff@documentfoundation.org
<p>To reflect the changed membership composition, shortly after the beginning of each quarter, tdf-members@ needs to be propagated with the new subscriber list.<br /><strong>NOTE</strong>: Don't confuse with tdf-membership@ mailing list</p>
<ul>
<li>MC will have their meeting and send draft notes</li>
<li>Sophie and Florian will prepare the paperwork</li>
<li>MC will send a list of e-mail addresses, containing all current subscribers</li>
<li>all subscribers need to be removed via the web interface (remember to disable notification)</li>
<li>the current subscriber list needs to be added via the web interface (disable notification again)</li>
<li>e-mail Sophie, so she can follow-up to the new members on the list</li>
</ul> Board Public - Task #803 (In Progress): Membership Committee electionhttps://redmine.documentfoundation.org/issues/8032014-11-04T16:15:26ZFlorian Effenbergerfloeff@documentfoundation.org
<p>The bi-yearly elections for the Membership Committee need to be prepared very well in advance, to meet the deadlines set forth in the statutes. Adding this recurring ticket so Sophie can track it.<br />Remember: Daylight savings might change during the election</p>