[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-website] Minutes from the Tue Feb 19 infra call


1. guilhem
2. cloph
3. Brett
4. wget (joined when discussing about weblate)
5. Dennis (very late + connection problems)


* SophiaS: Future of Gerrit (upgrade to 2.16, if possible?), some ETA
+ No plan to move away from 2.13 for the time being.
+ FWIW 2.9 are still supported and we'll upgrade to 2.13.x as the release
come along.
+ BTW what's so interesting about 2.16?
. buovjaga (IRC): 2.16 has a codemirror plugin for inline editing, which
documentation team could use
+ tdf#2715: current gerrit-oauth-provider plugin is using old endpoint
(Google+), will be deprecated on March 07
. AI guilhem (cloph to test, apply to prod instance during the evening or
* Migration Plan for Pootle? Weblate, etc, ETA
+ test instance available at https://weblate.documentfoundation.org
(point your local resolver to
+ initial import quite slow (just like pootle), estimated time ~1week
+ need to agree/decide (with the NL teams) how to split the translation
+ no rush, still have to decide what to switch to (ETA ~summer or ~libocon)
* ES 5.6.x on the pootle box: EOL'ed on March 11, upgrade to 6.x needs some
testing (API change etc.)
* tb31 upgrade (actually reinstall from Ubuntu 14.04.5 LTS to CentOS):
+ postponed (AI guilhem: still need to poke someone with physical access to
get a KVM)
+ LCOV 1.14 is on the way, just an hint, so waiting for it wouldn't hurt
* download counter / update checks (Brett)
+ TODO increase the number of custom dimension, need a (very slow) schema
migration (took ~2 days in the past), can disable statistic recording
. poke Italo and/or Florian ask the preferred time when it's acceptable to
have a flat graph
+ Brett, guilhem: upstream's script doesn't seem to be targeting live data
+ the exporter needs to run in “fire and forget” mode, ignoring failures from
matomo (having a flat graph occasionally is acceptable, but starving the
httpd or recording only half the metrics is not)
+ in the 'matomo-log-processing' branch, substitute upstream's python
importer with guilhem's perl script (to be adapted)
+ avoid socket activated units (fewer moving pieces, easier to monitor
failure state), instead use a static named pipe (either created by salt
in a persistent file system, or by adding `ExecStartPre=…` to nginx.service's
override unit)
+ next step: import old logs, can use upstream's script for that (no need
to “fire and forget”)
* wget: News from AskBot situation? No news from TDF board or Florian at the
* wget: following discussion with cloph at FOSDEM: ability to move
SilverStripe website source code to our gerrit instance
+ we have repo on github - not up-to-date in terms of php/page-types, but
theme and general idea: https://github.com/tdf/newdesign_wip
. cloph: will update it soonish (but if you want to work on css/the
theme, then no reason to wait for that)
. cloph: prefer git-send-email(1) over github pull requests for now
* Next call: Tuesday March 19 2019 at 18:30 Berlin time (17:30 UTC).


To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/website/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-website] Minutes from the Tue Feb 19 infra callFlorian Effenberger <floeff@documentfoundation.org>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.