Participants
============
1. guilhem
2. wget
3. Brett
4. Luke
5. Cloph
Agenda
======
* Luke: Move forward on x86 tinderbox:
http://document-foundation-mail-archive.969070.n3.nabble.com/minutes-of-ESC-call-td4262438.html
+ interested to revive x86 tinderbox
+ Cloph: machine is ready, waiting to be used, can set up access early next
week, or even during the week-end
+ cloph@documentfoundation.org not @libreoffice.org (please also CC
hostmaster@documentfoundation.org)
+ didn't realize the keys were pasted via IRC, was waiting for a mail :-P
+ alternatively: create a ticket to Redmine
* Brett: has spare computing capacity, can offer to host more TBs
+ intel 6700k CPU (i7) lying around, also samsung 850 EVO (might use that one for
something else though)
- MB has some issues (for GPU) but the machine is fully functional, 16GiB DDR4
+ cloph: could be used as replacement for hetzner/EC2 cloud depending on how
fast the machine is
+ less urgent than having the 32-bits tb back though
+ cloph: for linux bots one needs centos7, create "tdf" user, clone LODE ->
will come back with precise instructions
+ guilhem: come back to Brett with the VPN creds
* Brett: has (yet!) another box available, dell poweredge R210 II (1x Xeon
E3-1270v2 3.50GHz Processor, 4GB RAM, 1TB WD Blue 7200 RPM).
+ Older/slower machine; could use as 32-bits TB
* [rdm#1481] move bibisect repos off gerrit (to dev-downloads?)
+ deprecate old git:// URLs, uses https://bibisect.libreoffice.org
+ cloph: they don't need to be hosted as .git repos for the *inactive* repos,
tarballs/bundles would be fine as well
- for inactive repos like https://bibisect.libreoffice.org/linux-64-6.1.git
redirect to tarball instead of suggesting the git-clone command
- use `git bundle create` once the repo is inactive
* wget: move website repos from GitHub to gerrit
+ Ability to contribute and integrate patches more easily
+ cloph: can stay on github as it makes sense to allow pull-requests/patches for that
+ wget: users are confused about the double standard workflow gerrit vs github
+ cloph: we could have both (using gerrit's github plugin)
- also for core/online/etc
- [this is blocking on the upgrade to 2.16]
+ AI cloph: import website repo to gerrit and use it as authoritative source,
with github as mirror
* wget: Disable issue tracker and ability to contribute on Git repos hosted on GitHub
+ cloph: couldn't find a way to disable pull-requests & issue tracker
+ AI wget: providing a rdm ticket about instructions for the pr/issues tracker
removal from github
* wget: Consistency between /tdf and /libreoffice on GitHub + validate domains
+ AI wget: provide rdm ticket with instructions
* wget: get whole copy of blog instance VM for dev purpose
+ Because of GDPR issues, data leaks to third parties
- g. nothing beyond 3rd party services listed at privacy policy
https://libreoffice.org/privacy
+ Nuke WordPress auth tokens first?
- g. Way too overkill, can't afford to go through the entire db and upload
tree to prune private stuff
- wget: ok to export config tables + extensions config files to reproduce
the config locally (dev instance)
. guilhem: fill a redmine ticket + discussion on the website mailing list
+ guilhem: should be doable to have a test instance like we do with silverstripe
+ KVM or LXC based?
- KVM
* Weblate
+ AI guilhem: consolidate saltstack (hosts.vm137 vs hosts.weblate)
+ cloph: everything migrated off pootle except the website translations
+ should reclaim translations.tdf name at some point, but no need to rush
(can wait until FOSDEM)
* Update check
+ two HTTP requests (GET + OPTIONS/PROPFIND) per check
- cloph: will look into that
+ AI cloph: need to add the map to the repo
- Lua source location?
. make it clear that the .php script has been subsumed
* Download metrics: https://downloadcounter.libreoffice.org/
+ more accurate metrics (and slightly lower) now available in Matomo
+ once we deprecate downloadcounter we'll need to find another way to publish
that data to the world, for instance with static images/exports
* wget: Easily accesss very old discussions for third party FOSS projects
(Mattermost Inc's request)
+ full text search?
- could use xapian with a drop-down menu to select list archives to search
from, but that doesn't offer much more than searches using a search engine
+ g: "site:https://listarchives.documentfoundation.org/www/board-discuss/ foobar"
in your favorite search engine should work
- wget: not really usable in practise because search results may be
truncated depending on the mailing list and search engine used :(
* wget: Mastodon Update cf. rdm#3033?
+ none. ticket will be updated when time allows
* Gerrit SSO + upgrade: https://listarchives.libreoffice.org/global/projects/msg02641.html
+ ~90% of active accounts (in the past 30 days) have a linked SSO account
+ everyone has been warned: banner + 2x announce + 2x individual mails
+ 3rd individual mail this week-end, then *lock out*
* PiTR
+ Brett has been travelling through the land of 7/11 and Wal-mart and sadly
hasn't had any time to work on anything useful for the world. Holiday
shenanigans will conclude next week.
+ guilhem: didn't find time to work on the prometheus exporters either
* Next call: Tue Jan 21 17:30:00 UTC 2020
--
Guilhem.
--
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
Context
- [libreoffice-website] Minutes from the Tue Dec 17 infra call · Guilhem Moulin
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.