[Libreoffice-commits] core.git: logerrit
logerrit |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit d144fe04e7689b0298239b78ee6a6638e136fd55 Author: Guilhem Moulin AuthorDate: Wed Jan 15 05:22:20 2020 +0100 Commit: Guilhem Moulin CommitDate: Thu Jan 16 01:01:58 2020 +0100 logerrit: Upgrade URIs to https:// Change-Id: I0dc259178e5df6334a13ab04850ec662499fe7d3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86821 Reviewed-by: Guilhem Moulin Tested-by: Jenkins diff --git a/logerrit b/logerrit index 618686e012bd..ac33c4bf38f4 100755 --- a/logerrit +++ b/logerrit @@ -63,7 +63,7 @@ case "$1" in echo " " echo echo "advanced users should consider using git review instead:" -echo "http://wiki.documentfoundation.org/Development/GitReview"; +echo "https://wiki.documentfoundation.org/Development/GitReview"; exit ;; setup) @@ -236,7 +236,7 @@ case "$1" in echo >> ../commitmsg echo "branch is at:" >> ../commitmsg git log -1|sed -e "s/Change-Id:/XX:/" >> ../commitmsg -git fetch git://gerrit.libreoffice.org/core.git feature/$BRANCH && \ +git fetch https://git.libreoffice.org/core feature/$BRANCH && \ git checkout -b featuretst FETCH_HEAD && \ cp -a .git-hooks/* .git/hooks git commit --allow-empty -F ../commitmsg && \ ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: logerrit
logerrit | 61 +
1 file changed, 33 insertions(+), 28 deletions(-)
New commits:
commit 1e6428deed42a1ede1d5adbef5676438e6e9e898
Author: Guilhem Moulin
AuthorDate: Wed Jan 15 06:00:36 2020 +0100
Commit: Guilhem Moulin
CommitDate: Thu Jan 16 00:01:03 2020 +0100
logerrit setup: refactor key-based SSH handling
* Don't select existing ~/.ssh/id_dsa.pub. Since 7.0 (released
2015-08-11) OpenSSH servers won't accept DSA user keys anyway, so
users have likely rotated their legacy key material by now.
* The pubkey to copy into gerrit is derived from the first existing file
among ~/.ssh/id_ecdsa, ~/.ssh/id_ed25519, and ~/.ssh/id_rsa. These
algorithms are ordered as found in PubkeyAcceptedKeyTypes' default
value as of OpenSSH 8.1. (EC keys are only supported since Gerrit
1.14.) Generate an RSA key when ~/.ssh doesn't exist, as before,
since it's still the default in ssh-keygen(1) from OpenSSH 8.1.
* In the ssh_config(5) stanza, only include the IdentityFile when a
the private key file exists. The private key material might reside
somewhere else, for instance in a smartcard or in an external agent's
key store; in both cases the ssh client can authenticate the user
without direct access to the key material. While it's possible to
set IdentityFile to a pubkey (with IdentitiesOnly={yes,no}) it's not
documented and thus shouldn't be used.
Change-Id: Id73a2798747ce5c394b0cf2d0dc40107a1f2c599
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86858
Reviewed-by: Guilhem Moulin
Tested-by: Guilhem Moulin
diff --git a/logerrit b/logerrit
index 04ce54414904..618686e012bd 100755
--- a/logerrit
+++ b/logerrit
@@ -27,7 +27,9 @@ submit() {
logerrit() {
echo "Host logerrit gerrit.libreoffice.org"
-echo "IdentityFile ~/.ssh/id_rsa"
+if test -n "${2-}" && test -f "$HOME/.ssh/id_$2"; then
+echo "IdentityFile ~/.ssh/id_$2"
+fi
echo "User $1"
echo "Port 29418"
echo "HostName gerrit.libreoffice.org"
@@ -82,25 +84,28 @@ case "$1" in
echo "Hit enter to generate an ssh key - you will need to enter a
pass-phrase"
echo
read
- ssh-keygen -t rsa -f "$ssh_home/id_rsa"
- fi
- if test -d $ssh_home; then
- if test -f "$ssh_home/id_rsa.pub"; then
- ssh_key=$(cat $ssh_home/id_rsa.pub);
- elif test -f "$ssh_home/id_dsa.pub"; then
- ssh_key=$(cat $ssh_home/id_dsa.pub);
- fi
+ ssh-keygen -t rsa -f "$ssh_home/id_rsa" # default type as of
OpenSSH 8.1
fi
-echo "Please go to https://gerrit.libreoffice.org/ and:"
-echo "- press the 'register' button in the top right corner"
-echo "- after login set yourself a username (it is recommended to use
your IRC-nick)"
- if test "z$ssh_key" = "z"; then
-echo "- add your public ssh-key into the ssh keys settings."
- else
- echo "- paste the key below into the 'Add SSH Public Key' box."
- echo
- echo "$ssh_key"
- echo
+if test -d "$ssh_home"; then
+# order algos based on the PubkeyAcceptedKeyTypes option from OpenSSH
8.1
+for ssh_key_type in ecdsa ed25519 rsa; do
+pk="$ssh_home/id_${ssh_key_type}.pub"
+ssh_key=""
+if test -f "$pk" && ssh_key="$(< "$pk")" && test -n "$ssh_key";
then
+break
+fi
+done
+fi
+echo "Please go to https://gerrit.libreoffice.org/ and:"
+echo " - press the 'register' button in the top right corner"
+echo " - after login set yourself a username (it is recommended to use
your IRC-nick)"
+ if test -z "$ssh_key"; then
+echo " - add your public ssh-key into the ssh keys settings."
+else
+ echo " - paste the key below into the 'Add SSH Public Key' box."
+echo
+printf '%s\n' "$ssh_key"
+echo
fi
echo
echo "Note that you need to register additional email addresses, if
you want to"
@@ -108,15 +113,15 @@ case "$1" in
echo "invitation mail it sends you."
echo
read -p 'Which user name did you choose? ' GERRITUSER
- if test "
[Libreoffice-commits] core.git: logerrit
logerrit |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) New commits: commit 9276b117355c098bdfbe3cfa207aca869bf4bd01 Author: Guilhem Moulin AuthorDate: Wed Jan 15 05:22:20 2020 +0100 Commit: Guilhem Moulin CommitDate: Wed Jan 15 23:51:17 2020 +0100 logerrit: atomically create ~/.ssh with restrictive mode AFAICT `mkdir [-m mode]` is already defined in POSIX.1-1990. Change-Id: I159578eac16398f16d55578fbd818906b77cf373 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86852 Tested-by: Jenkins Reviewed-by: Ilmari Lauhakangas Reviewed-by: Michael Stahl diff --git a/logerrit b/logerrit index 33f45dc44c73..04ce54414904 100755 --- a/logerrit +++ b/logerrit @@ -76,8 +76,7 @@ case "$1" in created_ssh= if ! test -d $ssh_home; then echo "It appears that you have no ssh setup, running ssh-keygen to create that:" - mkdir $ssh_home - chmod 0700 $ssh_home + mkdir -m0700 "$ssh_home" created_ssh=TRUE echo echo "Hit enter to generate an ssh key - you will need to enter a pass-phrase" ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
Re: Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC
On Fri, 27 Dec 2019 at 17:13:26 +, Luke Benes wrote: > What is the URL to change that? There is none, and this is by design. > Some people might not want their email name to be changed to their SSO > login IDs. Their email name? You mean the RFC 5322 display-name? AFAICT that;s (mostly) free form, gerrit will check that your email address matches one of your identities, but you should be able to use anything as display-name. This is configurable locally with `git config user.name "Foo Bar"`. In fact most commits seem have “proper” authorship info, your examples seem to be the only afected ones: https://git.libreoffice.org/core/log -- Guilhem. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC
On Fri, 27 Dec 2019 at 14:56:28 +, Luke Benes wrote: > Where is the new username being pulled from? I suppose that's the username you chose when you created your account on our Single Sign On system. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
EC keys for [gerrit.libreoffice.org]:29418 (Was: Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC)
On Thu, 05 Dec 2019 at 07:03:54 +0100, Guilhem Moulin wrote: > 2.14 also adds support for ed25519 SSH keys; once in production we'll > send a known_hosts snippet with the new host key. Snippet enclosed. The RSA key remains unchanged, the DSA one is no longer supported (also client-side for OpenSSH ≥7.0), and new keys were generated for the NIST curves as well as for ed25519. EC keys can be added to one's profile at https://gerrit.libreoffice.org/settings/#SSHKeys , too. -- Guilhem. [gerrit.libreoffice.org]:29418 ssh-rsa B3NzaC1yc2EDAQABAAABAQDRYqhKltihIoORKo+i/mP3y/ie+gA5Nn7ghVf40w5QLzMMrkmcleTQQtiFInFmkL1VSaV0cs2hWLcEvPl8yKMwR3nCVcg25qoeZnq9w+MOTXvhHoDlUk8f1l6ttiiDis+55EPUbrlcs9IWbhBzbqksGCMf4XV5aQmmwcAXuHlzEXazNVb2nXhLE39HUUdD1FRAG+YPnmpQWwOPoDR4b+NdPgPneqNJaLIzcufynUmx20JGRX5jzej9a4boPoBRXFLjXCaCqzujDHRRDvx4IR7M7vH2hKr8zx47xjMay9VBEWB7q/ufcyamXc4+qkSWKAek1SIfd2jA6eyDSW0W7JlZ gerrit-code-rev...@gerrit.libreoffice.org [gerrit.libreoffice.org]:29418 ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBGE4VsSt5gCCdzRnI0QD7bqiD6dUM5F+plKvar3L6Y6eBipCGl2rK1cDmQCBTgoRvaKsEleh1rQDaxy2JVeeoN4= gerrit-code-rev...@gerrit.libreoffice.org [gerrit.libreoffice.org]:29418 ecdsa-sha2-nistp384 E2VjZHNhLXNoYTItbmlzdHAzODQIbmlzdHAzODQAAABhBC7yV2J1L3A5C5Bg9xvLpZkFbp5B87qvwdgBRoelGMpMj091DWdgRkfhw2poCuWbKoulGzIVlLm9w+/eRiOPHb5i+1qLnu8hMi61hjpDjTNWAZ2SvMptA3r+Cn+zoDCa6w== gerrit-code-rev...@gerrit.libreoffice.org [gerrit.libreoffice.org]:29418 ecdsa-sha2-nistp521 E2VjZHNhLXNoYTItbmlzdHA1MjEIbmlzdHA1MjEAAACFBAEhAmKU1EYDyXJFnSh1x2ld9AFM2OXyhJxNhOJWugKsmC2IWBk45QCQzp0lkRbvgANFfQlShc8b56f5ynpI7AWzQwDueZLczwuLac48n6OeeEZiz0OXOilfmQwgPC3t14wa+bshEG/NhjuAO/yQS6oljIB3uquKxCU27UCKbG/ftXGJvw== gerrit-code-rev...@gerrit.libreoffice.org [gerrit.libreoffice.org]:29418 ssh-ed25519 C3NzaC1lZDI1NTE5INDv6wjS6RZnesdVjCNtGeQGImd4H+Kl6n8+pl1crT+/ gerrit-code-rev...@gerrit.libreoffice.org signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Reminder] Planned Gerrit upgrade (and Google/GitHub/OpenID auth deprecation) on Wed, Dec 25 from 00:00 to 04:00 UTC
On Thu, 05 Dec 2019 at 07:03:54 +0100, Guilhem Moulin wrote: > We'll upgrade to Gerrit 2.16 on Wed, Dec 25 starting at 00:00 UTC. This > is a pretty long upgrade path and a pessimistic ETA is 04:00 UTC. > > *Important*: After completion it will no longer possible to log in using > third-party authentication methods such as Google and GitHub OAuth2 IdPs. > Authentication to the web frontend will need to be done with TDF's Single > Sign-On system. The upcoming migration is hopefully known to everyone involved. We reached out via public announcements to various mailing lists, weekly ESC notices, a shiny banner, and two individual reminders (will send a 3rd one later today). The handful of regular contributors who still can't be linked to our Single Sign-On service will be *locked out* from the web UI next Wednesday at 00:00 UTC. After that, manual intervention will be required to unlock old accounts; that'll be cumbersome for everyone and certainly not without delay. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Dec 17 at 17:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Dec 17 17:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC
Hi there, We'll upgrade to Gerrit 2.16 on Wed, Dec 25 starting at 00:00 UTC. This is a pretty long upgrade path and a pessimistic ETA is 04:00 UTC. *Important*: After completion it will no longer possible to log in using third-party authentication methods such as Google and GitHub OAuth2 IdPs. Authentication to the web frontend will need to be done with TDF's Single Sign-On system. Gerrit accounts not linked to our SSO system will effectively be *locked out* after that date, and unlocking require manual intervention from an infra team member. Please see the announcement message for details: https://listarchives.libreoffice.org/global/projects/msg02605.html . Authentication using SSH keys and HTTP credentials will keep working as now. 2.14 also adds support for ed25519 SSH keys; once in production we'll send a known_hosts snippet with the new host key. A Gerrit 2.16 preview, including the authentication part, is available on our stage instance at https://gerrit-stage.documentfoundation.org . Once on 2.16 we'll start migrating the change metadata backend from ReviewDb to NoteDb, and eventually upgrade to 3.0 in the not too distant future. That upgrade should be less intrusive to users. Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Nov 19 at 17:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Nov 19 17:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Oct 15 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Oct 15 16:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Sep 17 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Sep 17 16:30:00 UTC 2019"` (18:30:00 Berlin time). Note: that's tomorrow! We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra announce: Authenticating against gerrit using TDF's Single Sign-On system
Dear developers, Please visit https://user.documentfoundation.org/edit (use your Single Sign-On credentials to authenticate — if you don't have an account there then please create one) and check whether you have “Gerrit” in the “Linked profiles” section. If not, then add the preferred email address of your gerrit account [0] to the form above; a confirmation token will then be delivered to that address, and “Gerrit” should appear in the “Linked profiles” section after confirmation. About 68% of the gerrit accounts who uploaded a patch set in the past 30 days are known to the Single Sign-On system. These accounts can use TDF's new OAuth2 IdP at https://gerrit.libreoffice.org/login/ i.e., authenticate through The Document Foundation's Single Sign-On system. Unfortunately, due to the way the OAuth2 plugin work, if you try a new IdP that is not linked to your existing gerrit account, then a *brand new* account is created. (This is no different than for other providers like GitHub or Google.) If that happens, then please *do not* start using the new account, instead ask us to merge them ASAP at hostmas...@documentfoundation.org (or on IRC at #tdf-infra). While merging a fresh account is painless, the logic is more brittle (there is risk of breaking referential integrity) if they're both actively used, so again please poke us ASAP. In the not too distant future, TDF's OAuth2 IdP will become the *only* way to authenticate against our gerrit instance: authenticating using other OAuth2 or OpenID providers will no longer be possible. We're unable to give a precise ETA right now, as we need a higher ratio of patchsets authors in SSO, but that will definitely be *in 2019*. Later this week we'll individually poke all recent patchsets authors that are still unknown from our Single Sign-On system. Once we deprecate other OAuth2 and OpenID providers, gerrit accounts that are still missing from SSO will be effectively *locked out* until an infra team member manually tie them up to the relevant LDAP DIT entry. FWIW finalizing the migration to TDF's OAuth2 IdP is a prerequisite for upgrading gerrit to more recent versions (with shiny new Web UI, ed25519 SSH key support, CodeMirror editor plugin, and more [1]). -- Guilhem, for The Document Foundation's infra team. [0] The one shown at https://gerrit.libreoffice.org/#/settings/ . [1] https://www.gerritcodereview.com/releases-readme.html signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Aug 20 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Aug 20 16:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jul 16 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Jul 16 16:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jun 25 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Jun 25 16:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, May 21 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue May 21 16:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Apr 16 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Apr 16 16:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Gitiles VCS browser
On Fri, 05 Apr 2019 at 17:07:06 +, Kaganski Mike wrote: > On 05.04.2019 19:55, Guilhem Moulin wrote: >> On Fri, 05 Apr 2019 at 09:17:01 +0200, Miklos Vajna wrote: >>> One more aspect: perhaps I'm just unlucky, but on average, I found >>> cgit to load much faster than these git.libreoffice.org links. >> >> Hmm that's interesting. That's not something I'm able to reproduce by >> taking 100 random commits from the last 1 non-merge commits in >> master: > > From my observations, the older the commit, the longer it takes. It > might even timeout for some commits from early 2000s. I see, thanks for the tip. With very old commits I'm indeed able to reproduce Miklos' metrics. Should have taken the last 10 commits, I guess :-) That's odd and unfortunate, indeed. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Gitiles VCS browser
Hi Miklos, On Fri, 05 Apr 2019 at 09:17:01 +0200, Miklos Vajna wrote: > One more aspect: perhaps I'm just unlucky, but on average, I found > cgit to load much faster than these git.libreoffice.org links. Hmm that's interesting. That's not something I'm able to reproduce by taking 100 random commits from the last 1 non-merge commits in master: $ git log -n 1 --no-merges --pretty="%H" master | shuf -n 100 >/tmp/commit_list $ ./measure.sh "https://git.libreoffice.org/core/+/%s%%5E%%21/"; https://cgit.freedesktop.org/libreoffice/core/commit/?id=%s"; https://git.libreoffice.org/core/ average stddev minimum maximum --- --- -- --- --- size (byte)19691 17007 433464345 start transfer time 0.800.68 0.27 2.13 total time 0.860.66 0.29 2.17 start transfer time 0.120.09 0.08 0.38 total time 0.160.09 0.09 0.39 start transfer time 0.120.09 0.09 0.38 total time 0.160.09 0.09 0.39 https://cgit.freedesktop.org/libreoffice/core/ average stddev minimum maximum --- --- -- --- --- size (byte)52903 157673907794857 start transfer time 0.390.16 0.30 0.85 total time 0.730.30 0.31 1.17 start transfer time 0.230.15 0.17 0.67 total time 0.560.31 0.33 1.30 start transfer time 0.230.15 0.18 0.67 total time 0.560.37 0.18 1.48 So on first glance it appears that occasionally a gitiles page takes longer to load (though I wasn't able to reproduce the 20s you measured, more like 2-3s in my case). However it's AFAICT rare enough that it doesn't impact the average load time. And caching makes subsequent hits constantly faster. (I dunno what's the caching strategy here, something internal to JGit probably.) Cheers, -- Guilhem. measure.sh Description: Bourne shell script signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Gitiles VCS browser
On Wed, 20 Mar 2019 at 16:24:49 +, Luke Benes wrote: > In his last email, Mike explains how the gitiles timestamps lead to > confusion. This is a serious problem for my use case. You mean https://lists.freedesktop.org/archives/libreoffice/2018-November/081343.html ? This was addressed on Nov 9… *author* names are shown along with *committer* dates in /+log/…?pretty=oneline views (i.e. the default log view). Which timestamps are still confusing? > When I asked for feedback on the IRC dev channel, no one voiced > preference for gitiles. I only heard agreement that the URLs and log > format are inferior to cgit's. Was there more to it than these 3 messages from Fri, 15 Mar around 19:00 CET? 18:59:02 < slacka123> what are people's thoughts on gitiles vs cgit? There are a few issues that annoy me, like the format for logs and the "^!" symbols that it appends on the end of the URLs, making copy/paste of commit id's a pain 19:00:09 < slacka123> last message on the dev list was talk of putting cgit back as default commit bot. Would people like to see cgit back? 19:09:10 <@erAck> slacka123: the ^! is a tad annoying, but I don't mind that much, once followed there's the raw commit ID as well; the log was clearer with cgit I might have missed part of the exchange, because from the above I'd say that your conclusion is quite a stretch. Moreover IRC isn't really great for doing polls, especially on Friday evenings :-) That said the plan with gitiles was to replace gitweb, not cgit, which is not hosted nor maintained by TDF anyway. For what it's worth, Björn asked for the notification change in <20181028095501.GA21770@skorpion>. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Mar 19 at 17:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Mar 19 17:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Tentative Agenda: * Download logs & update checks - Now in Matomo - Adjust Custom Dimensions? - Pending: Import old logs * Future of GeoLite Legacy (and Mirrorbrain) - Accept that GeoLite Legacy databases are no longer updated? Use nginx's GeoIP2 module and patch Mirrorbrain to add support for the new MMDB format? Try out an alternative like Mirrorbits? * OCS-Webserver (new extension site) deployment * [Matrix] instance and bridges (not prod yet) See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Feb 19 at 17:30 UTC
Hi there, The next infra call will take place at `date -d "Tue Feb 19 17:30:00 UTC 2019"` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jan 15 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jan 15 17:30:00 UTC 2019'` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Dec 18 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Dec 18 17:30:00 UTC 2018'` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Nov 20 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Nov 20 17:30:00 UTC 2018'` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Tue, 30 Oct 2018 at 16:18:36 +, Luke Benes wrote: > The date gitiles displays in the log is the author date, rather than > the much more useful commit date. Quoting my own <20181023142926.GB21836@localhost.localdomain>: | It's shows the authored date, not the commit date. We can easily tweak | the template, but IMHO it's more consistent to show the authored date | given that the name that's beside it is the author's not the committer. | Gitweb, on the other hand, shows the *commit* date along with the | *author* name. > When trying to track down regressions, you care about the order of > commits, not when they were authored. I'm confused, neither commit date nor author date give any guaranty regarding the order of commits. AFAICT the only thing that helps here is to follow the Merkel tree (child → ancestor) back to the root. Unlike ordering by date, performing a topological order of the tree (e.g., following the output from git-log(1)) is reliable, as the relations are cryptographically secured. That being said, I don't care which of author or committer is shown in the log view. I believe it should be both committer name + date, or both author name + date for consistency, but if QA wants to mix the two then so be it. > Also, how do you search a range and author? I used both of these > searches very often. It's been asked and replied earlier in this thread, too. Authors and committers are links to their respective filtered log (by adding author=$AUTHOR or committer=$COMMITTER to the query string). Ranges are obtained with $COMMIT_ID1..$COMMIT_ID2 (similar to GitHub), for instance https://git.libreoffice.org/core/+log/647fc4..044122d (oneline) https://git.libreoffice.org/core/+log/647fc4..044122d?pretty=full (log + commit messages) https://git.libreoffice.org/core/+/647fc4..044122d (diff) > Without them, gitiles shouldn't be the default. I keep finding myself > manually switching back to cgit to access these. FWIW, Moggi hinted that there were good reasons for pointing bugzilla notifications to FreeDesktop, and he's planing to revert the change. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
Hi Björn, On Sun, 28 Oct 2018 at 10:55:01 +0100, Bjoern Michaelsen wrote: > Can we have it as the link in these "commit notifications" Sure, done: https://bugs.documentfoundation.org/show_bug.cgi?id=119410#c6 . Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Tue, 23 Oct 2018 at 04:29:05 -0500, Adolfo Jayme Barrientos wrote: > Since loading the whole diff for a commit would potentially crash my > browser, I find it very helpful to load each file’s individual diff in > a commit like this [1]. Also, I can open per-file diffs in separate > tabs for better organization. You'll now find links to per-file diffs at https://gerrit.libreoffice.org/plugins/gitiles/translations/+/master . Is your workflow covered, Adolfo? -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
Hi Eike, On Wed, 17 Oct 2018 at 21:03:45 +0200, Guilhem Moulin wrote: > On Wed, 17 Oct 2018 at 14:05:27 +0200, Eike Rathke wrote: >> For diffs I much prefer the gerrit view because it highlights changes >> within changed lines, for example >> >> https://gerrit.libreoffice.org/plugins/gitiles/core/+/9672d034b9e760f24ac9a6652ab45dee15ee260a%5E%21/ >> vs >> https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=9672d034b9e760f24ac9a6652ab45dee15ee260a >> >> Would that be possible also with gitiles? They both show marked changes now :-) > Not that I know of, and looking at the source I don't think so > > https://gerrit.googlesource.com/gitiles/+/master/java/com/google/gitiles/HtmlDiffFormatter.java#142 I patched this file to make use of Neil Fraser's ‘diff-match-patch’ library and find the array of differences to mark (with semantic cleanups so the result is readable). That array is also what's used to compute the Levenshtein distance, so it should be quite accurate ;-) On the other hand, gitweb's algorithm is rather dumb and crude. Only edits with the same number of deleted & inserted lines are considered; the marked part is what's left after removing the longest common prefix & suffix between a removed line is its corresponding insertion. It's therefore not possible to have more than one mark per line, and code reflowing might not marked properly. Complexity wise gitweb's algorithm has a lower worst case bound (linear vs. quadratic), but it shouldn't matter in practice as in our case the marks don't need to be optimal, and the algorithm will give up and return a sub-optimal solution if it hasn't found the best one under 50ms. Unfortunately that change is most likely not upstreamable since I had to abuse the JGit API quite heavily… :-/ -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Tue, 23 Oct 2018 at 13:42:34 +0200, Christian Lohmaier wrote: > On Tue, Oct 23, 2018 at 1:15 PM Adolfo Jayme Barrientos > wrote: >> Missatge de Kaganski Mike del dia dt., 23 d’oct. >> 2018 a les 4:40: >>> Well - e.g., >>> https://gerrit.libreoffice.org/plugins/gitiles/core/+/b0c6d587405af9e2263dc5073a9a965db46ff986 >>> shows the individual links for each file like this: >>> >>> icon-themes/breeze/links.txt[diff] >>> icon-themes/breeze_dark/links.txt[diff] >>> icon-themes/breeze_svg/links.txt[diff] >>> icon-themes/colibre/links.txt[diff] >>> icon-themes/karasa_jaga/links.txt[diff] >>> officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu[diff] >>> sw/uiconfig/sglobal/popupmenu/frame.xml[diff] >>> sw/uiconfig/sweb/popupmenu/frame.xml[diff] >>> sw/uiconfig/swform/popupmenu/frame.xml[diff] >>> sw/uiconfig/swreport/popupmenu/frame.xml[diff] >>> sw/uiconfig/swriter/popupmenu/frame.xml[diff] >>> sw/uiconfig/swxform/popupmenu/frame.xml[diff] >>> 12 files changed >> >> Yeah, but those links all open the same page with the complete diff, >> just jumping to the relevant file. > > gitiles has the feature, e.g. > https://gerrit.libreoffice.org/plugins/gitiles/core/+/b0c6d587405af9e2263dc5073a9a965db46ff986%5E%21/icon-themes/karasa_jaga/links.txt > > would show the diff of only the icon-themes/karasa_jaga/links.txt file > > or > https://gerrit.libreoffice.org/plugins/gitiles/core/+/b0c6d587405af9e2263dc5073a9a965db46ff986%5E%21/icon-themes/ > > would limit the view to just those in icon-themes directory. Right, I'll tweak the template so the “[diff]” anchors in the log page link to these per-files diffs then, to match what gitweb is doing :-) -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Tue, 23 Oct 2018 at 09:40:20 +, Kaganski Mike wrote: > What seems odd to me is why the log like > https://gerrit.libreoffice.org/plugins/gitiles/core/+log/HEAD shows > commit creatin time that is different from the time the commit was > pushed to the branch. I would like to see just-pushed commits to tell "5 > minutes ago" instead "3 days ago" like it might be now. It's shows the authored date, not the commit date. We can easily tweak the template, but IMHO it's more consistent to show the authored date given that the name that's beside it is the author's not the committer. Gitweb, on the other hand, shows the *commit* date along with the *author* name. Compare https://gerrit.libreoffice.org/plugins/gitiles/core/+log/e50f90bd21dc1116e5f1defc73f230ef1b687315 and https://gerrit.libreoffice.org/gitweb?p=core.git;a=log;h=e50f90bd21dc1116e5f1defc73f230ef1b687315 for this commit (authored by Serge Krot on Oct 5, committed by bubli on Oct 22): https://gerrit.libreoffice.org/plugins/gitiles/core/+/e50f90bd21dc1116e5f1defc73f230ef1b687315 https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=e50f90bd21dc1116e5f1defc73f230ef1b687315 -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Tue, 23 Oct 2018 at 09:42:54 +0200, Lionel Elie Mamane wrote: > On Tue, Oct 23, 2018 at 07:34:54AM +0200, Guilhem Moulin wrote: >> On Mon, 22 Oct 2018 at 17:25:11 +0200, Lionel Elie Mamane wrote: >>> On Mon, Oct 22, 2018 at 04:33:21PM +0200, Guilhem Moulin wrote: >>>> Might be orthogonal to the git:// vs. https:// vs. ssh:// >>>> discussion. Gerrit uses JGit as Git implementation, while >>>> git-daemon(1) spawns “normal” (C-based) git-upload-pack(1) >>>> processes. > >>> For us developers of LibreOffice, and thus consumers of the Gerrit >>> / Git service of freedesktop.org and TDF, whether the difference >>> comes from the protocol itself or a different git implementation on >>> the server to serve the different protocols is intellectually >>> interesting (thanks for that!), but materially inconsequential: if >>> using git: will be faster, we will use git:. > >> Following the same logic, you want gerrit.libreoffice.org to serve >> content over plain http:// so you can save the two round-trips when >> you launch your browser to submit your reviews? Oo > > Submission (write access) is something else entirely than code > download (read access); the security requirements are massively > different. (Yes, I would prefer to be certain that the code I get is > the right one; however, if I don't and try to submit a patch on top of > code that is not the on in the TDF repo, it will fail. Unless the > attacker also constructed git that exploits SHA collisions?) Another (theoretic) attack vector is to strip a reference from the initial git-upload-pack advertisement so the dev doesn't get a bugfix or something; at least not until said dev relocates to a safer network. > (The above analysis does not apply to gerrit-as-a-website, because > there the link between the code I see and the code I approve is not > on my local machine, but depends on the security of the connection; > and because I don't know how to secure reading but not writing on a > website.) One way is to add https:// to form action fields. Not suggesting that we do that, though :-) If GET requests are served over plaintext links even for authenticated users, then an eavesdropper could sniff session cookies and hijack connections. > If the two round trips are multiplied by many many requests to serve > one operation, then I may notice. Where "operation" is one action for > the user, not one action for the program. E.g., "git fetch", "git > push", One has to pay the the full TLS overhead for each `git fetch` (AFAIK libcurl doesn't do session sharing across processes.). And the full SSH2 overhead for each `git push`, modulo connection multiplexing. > "load a complete web page with all images, javascript, dependencies, > etc", "post an answer to a gerrit change", Login form aside, all content is served from the gerrit box, so a single connection is used to serve all resources on a given page. And our server is configured to cache TLS sessions IDs, so clicking around doesn't cost an extra handshake for each page. >> Things have changed since 2012, encryption is faster (there are >> modern stream ciphers and hardware acceleration is more widespread), >> and for situations like this one there is no reason not to encrypt >> data in transit. > > I would have thought symmetric encryption already wasn't a bottlneck, > at least on the client side (maybe on the server side it was?) in > 2012; I think one could even back then easily saturate a 100Mbps > connection using less than 100% of one core of an entry-level desktop > CPU. You're right, it was probably a few years before that. Perhaps the main changes of the past few years is public perception. For reference, GMail defaulted to https:// in early 2010 [0], Facebook in summer 2013 [1] (feeling the heat of the Snowden leaks?), Wikipedia in early 2015 (2013 for authenticated users) [2] > Many public key crypto operations per seconds is (was?) another issue > altogether. Is, esp. for RSA (we're not using EdDSA currently). -- Guilhem. [0] https://gmail.googleblog.com/2010/01/default-https-access-for-gmail.html https://transparencyreport.google.com/https/overview [1] https://www.facebook.com/notes/facebook-engineering/secure-browsing-by-default/10151590414803920/ [2] https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Mon, 22 Oct 2018 at 17:25:11 +0200, Lionel Elie Mamane wrote:
> On Mon, Oct 22, 2018 at 04:33:21PM +0200, Guilhem Moulin wrote:
>> On Mon, 22 Oct 2018 at 11:51:35 +0200, Lionel Elie Mamane wrote:
>>> On Wed, Oct 17, 2018 at 09:03:45PM +0200, Guilhem Moulin wrote:
>>>> SSH is only used for transport, a git processed is exec()'ed on the
>>>> remote just like for git-daemon(1), so the only overhead is
>>>> crypto-related. The handshake is a one-off thing, thus negligible
>>>> when you're transferring a large amount of data at once; (...) As
>>>> for symmetric crypto overhead, (...) the overhead should be
>>>> negligible.
>
>>> All I know is that about 1/2/3 years ago ('t was I think in some
>>> coworking space in Brussels, probably a hackfest) I showed Michael
>>> Meeks how to have a separate "push" url (with ssh: protocol) and
>>> "pull" url (with git: protocol) and he was very happy at the
>>> speed-up.
>
>> Might be orthogonal to the git:// vs. https:// vs. ssh://
>> discussion. Gerrit uses JGit as Git implementation, while
>> git-daemon(1) spawns “normal” (C-based) git-upload-pack(1)
>> processes.
>
> For us developers of LibreOffice, and thus consumers of the Gerrit /
> Git service of freedesktop.org and TDF, whether the difference comes
> from the protocol itself or a different git implementation on the
> server to serve the different protocols is intellectually interesting
> (thanks for that!), but materially inconsequential: if using git: will
> be faster, we will use git:.
Following the same logic, you want gerrit.libreoffice.org to serve
content over plain http:// so you can save the two round-trips when you
launch your browser to submit your reviews? Oo
FWIW, we're stuck with git:// for the years to come because there is no
smooth upgrade path for clients; if I were to deploy the service today I
would most likely skip git-daemon(1). Things have changed since 2012,
encryption is faster (there are modern stream ciphers and hardware
acceleration is more widespread), and for situations like this one there
is no reason not to encrypt data in transit.
>> I recall Norbert and I sat down during FOSDEM 2017 to solve perf
>> issues with our JGit deployment. Perhaps you configured your
>> ‘remote..pushurl’ at the same time :-)
>
> I can easily believe it was earlier.
Then it was before my time, so no idea what the bottleneck was.
>> Anyway, it's easy enough to benchmark no-op `git fetch` on core. master
>> is currently at c99732d59bc6, and I'm fetching from the same datacenter
>> to avoid metrics being polluted with network hiccups.
>
> Yes, but no. You also test in an environment where a network RTT is
> probably about one fifth to one third of a millisecond, and bandwidth
> at least 100Mbps if not 1000Mbps? In that case, everything will be
> fast. Time difference will be lost in noise.
I was arguing that C git and Jgit's performances are indistinguishable
on the current instance. Transport overhead is the normal batch-mode
SSH (resp. TLS) overhead for ssh:// (resp. https://) remotes.
As mentioned earlier the protocol is essentially the same for git:// and
http:// (on servers supporting smart HTTP). In both cases there is a
first round-trip (client hello + server git-upload-pack advertisement),
and another if the client is missing some object(s) (client sends list
of missing objects and receives a pack back). For http:// these are
done in two sequential requests to the same connection (resp. ‘GET
/$REPO/info/refs?service=git-upload-pack’ and ‘POST
/$REPO/git-upload-pack’); for git:// there are equivalent requests in
the Git wire protocol.
https:// is just http:// wrapped in TLS, which costs an extra 2 round-trips
(TLS 1.3 brings that down to a single extra round-trip, but we don't offer
it yet).
For ssh://, what happens under the hood (as witnessed when adding
“GIT_TRACE=1” to the environment) is that an ssh process is spawned to
run git-upload-pack on the remote machine:
ssh -p 29418 gerrit.libreoffice.org git-upload-pack "/core"
Counting round-trips for SSH isn't trivial, but let me try:
* Client & server greet each other (in parallel)
* Client & server initiate KEX (in parallel)
* Key EXchange
* Client & server send NEWKEYS (in parallel)
* Client requests service, wait for response
* Client send each pubkey one at a time, waits for response; for the
one that's accepted by the server, it sends the signed response and
waits for the server to ack
* Client asks to open a new channel, waits for response
* Client asks to execute command in said channel, wait for response
* […]
* Server sends EOF and closes channel
* Clie
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Mon, 22 Oct 2018 at 11:51:35 +0200, Lionel Elie Mamane wrote:
> On Wed, Oct 17, 2018 at 09:03:45PM +0200, Guilhem Moulin wrote:
>> On Wed, 17 Oct 2018 at 14:05:27 +0200, Eike Rathke wrote:
>>> On Wednesday, 2018-10-17 04:27:54 +0200, Guilhem Moulin wrote:
>>>> Lastly, it's now possible to clone and fetch git repositories over
>>>> https:// . While git:// URLs will remain supported for the foreseeable
>>>> future, they're intentionally no longer advertised in gerrit, and we
>>>> encourage you to upgrade the scheme of your ‘remote..url’ to
>>>> secure transports (SSH for authenticated access, or HTTPS for anonymous
>>>> access). We'll update ‘lode’ and chase remaining git:// URLs shortly.
>
>>> Why is git:// deprecated? From what I know it's more efficient when
>>> fetching/pulling than https:// (or ssh://?)
>
>> Since v1.6.6 it's no longer true [0], cf. git-http-backend(1) and
>> https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes
>
> That webpage doesn't seem to contain a discussion of the efficiency of
> the various protocols.
My bad, I probably copy the URL from a wrong tab. This is what I intended
to share: https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols .
As you can see the protocols are essentially equivalent.
For a high-level overview and pros and cons of each protocol, there is
also https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols ,
which reads
“There is very little advantage that other protocols have over
Smart HTTP for serving Git content.” :-)
To be fair, it also says that “The Git protocol is often the fastest
network transfer protocol available”, but that's just because no
encryption is always faster than the fastest encryption. In practice
however, this argument is moot on modern CPUs.
FWIW, GitHub doesn't mentioned git:// URLs either (even though they're still
supported): https://help.github.com/articles/which-remote-url-should-i-use/ .
>> SSH is only used for transport, a git processed is exec()'ed on the
>> remote just like for git-daemon(1), so the only overhead is
>> crypto-related. The handshake is a one-off thing, thus negligible
>> when you're transferring a large amount of data at once; (...) As
>> for symmetric crypto overhead, (...) the overhead should be
>> negligible.
>
> All I know is that about 1/2/3 years ago ('t was I think in some
> coworking space in Brussels, probably a hackfest) I showed Michael
> Meeks how to have a separate "push" url (with ssh: protocol) and
> "pull" url (with git: protocol) and he was very happy at the
> speed-up.
Might be orthogonal to the git:// vs. https:// vs. ssh:// discussion.
Gerrit uses JGit as Git implementation, while git-daemon(1) spawns
“normal” (C-based) git-upload-pack(1) processes. I recall Norbert and I
sat down during FOSDEM 2017 to solve perf issues with our JGit
deployment. Perhaps you configured your ‘remote..pushurl’ at the
same time :-)
Anyway, it's easy enough to benchmark no-op `git fetch` on core. master
is currently at c99732d59bc6, and I'm fetching from the same datacenter
to avoid metrics being polluted with network hiccups.
$ git config remote.origin.url git://git.libreoffice.org/core && time git
fetch
0:01.62 (0.42 user, 0.64 sys) 142108k maxres
## Network usage: up 252kiB (4312 packets), down 10168kiB (7197 packets)
$ git config remote.origin.url https://git.libreoffice.org/core && time git
fetch
0:01.63 (0.81 user, 0.29 sys) 141688k maxres
## Network usage: up 56kiB (924 packets), down 4194kiB (1241 packets)
$ git config remote.origin.url
"ssh://$u...@gerrit.libreoffice.org:29418/core" && time git fetch
0:01.55 (0.62 user, 0.46 sys) 141588k maxres
## Network usage: up 67kiB (993 packets), down 9859kiB (1305 packets)
Pretty much equivalent, aren't they? :-) (Network usage for https:// is
smaller because the TLS termination proxy is also compressing responses
from the git backend. For git:// I guess the system time is higher than
the user time because it uses use sendfile(2) and friends since there
are no user-space encryption.)
As one might notice, network usage (~10MiB down, and growing) is really
high for a no-op `git fetch`. That's caused by the >140k refs/changes/…
in the initial git-upload-pack advertisement(1):
$ git ls-remote https://git.libreoffice.org/core | awk '
$1 ~ /^[0-9a-f]{40}$/ {
refs++;
if ($2 ~ /^refs\/changes\//)
changes++;
}
END {
printf "refs=%d, changes=%d (%.1f%%)\n",
refs, changes, 100*changes/refs;
}
'
refs=144709, changes=
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Wed, 17 Oct 2018 at 18:51:31 +, slacka wrote: > Thanks Guilhem! I like the look of gitiles, but they both need better > integration. Could you add hyperlinks to referenced commit messages > and to bugzilla? > […] > Note how gitiles is missing both and gitweb does not link to the bug > tracker. I'd like to get rid of gitweb so I'm reluctant to try to fix this at the moment; especially since AFAIK it's been like this forever. :-P But the Gitiles instance does anchor issue tracker references as well now (same links and regexps as gerrit), and also the full commit IDs. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
On Wed, 17 Oct 2018 at 22:31:37 +, Xisco Fauli wrote: > Sometimes i use the range search from cgit. e.g > > https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=647fc41763d1310479d59262734caa296f6e558d..044122de1153bd785ed555c96b6aca67e9d0f739 > > Do you know how I can do it with gitiles? Looks like https://gerrit.libreoffice.org/plugins/gitiles/core/+log/647fc4..044122d if you want the commit messages you can also add a “pretty=full” to the query string: https://gerrit.libreoffice.org/plugins/gitiles/core/+log/647fc4..044122d?pretty=full or if you want the diff: https://gerrit.libreoffice.org/plugins/gitiles/core/+/647fc4..044122d (These URLs work with the full 40-hexdigits commit IDs, too.) -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
Hi, On Wed, 17 Oct 2018 at 14:05:27 +0200, Eike Rathke wrote: > On Wednesday, 2018-10-17 04:27:54 +0200, Guilhem Moulin wrote: > >> * diff: https://gerrit.libreoffice.org/plugins/gitiles/core/+/master%5E%21/ >> vs. >> https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=refs/heads/master > > For diffs I much prefer the gerrit view because it highlights changes > within changed lines, for example > > https://gerrit.libreoffice.org/plugins/gitiles/core/+/9672d034b9e760f24ac9a6652ab45dee15ee260a%5E%21/ > > vs > > https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=9672d034b9e760f24ac9a6652ab45dee15ee260a > > Would that be possible also with gitiles? Not that I know of, and looking at the source I don't think so https://gerrit.googlesource.com/gitiles/+/master/java/com/google/gitiles/HtmlDiffFormatter.java#142 There is a feature request for a side-by-side view in Gitiles (mimicking the gerrit view), which I assume includes change highlighting; no update there, though: https://code.google.com/archive/p/gitiles/issues/2 . >> Lastly, it's now possible to clone and fetch git repositories over >> https:// . While git:// URLs will remain supported for the foreseeable >> future, they're intentionally no longer advertised in gerrit, and we >> encourage you to upgrade the scheme of your ‘remote..url’ to >> secure transports (SSH for authenticated access, or HTTPS for anonymous >> access). We'll update ‘lode’ and chase remaining git:// URLs shortly. > > Why is git:// deprecated? From what I know it's more efficient when > fetching/pulling than https:// (or ssh://?) Since v1.6.6 it's no longer true [0], cf. git-http-backend(1) and https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes . We're using the so-called “smart” HTTP protocol, with a git-upload-pack(1) service on the server. SSH is only used for transport, a git processed is exec()'ed on the remote just like for git-daemon(1), so the only overhead is crypto-related. The handshake is a one-off thing, thus negligible when you're transferring a large amount of data at once; and if you're connecting so often to an SSH remote that the handshake undermines performance, you should probably activate connection multiplexing in your client, cf. ssh_config(5) :-) As for symmetric crypto overhead, these days everyone has CPUs with AES-NI instructions (at least on build machines), hence the overhead should be negligible. Cheers, -- Guilhem. [0] https://github.com/git/git/blob/master/Documentation/RelNotes/1.6.6.txt signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
Hi Miklos,
On Wed, 17 Oct 2018 at 09:26:40 +0200, Miklos Vajna wrote:
> On Wed, Oct 17, 2018 at 04:27:54AM +0200, Guilhem Moulin
> wrote:
>> Right now https://gerrit.libreoffice.org/#/c/$CHANGENUM/ has both gitweb
>> and Gitiles links, but unless we hear strong objection we'll disable
>> gitweb at the end of the month, and serve requests to
>> ‘/gitweb?p=${REPOSITORY}.git;a=${ACTION};h=${REF}’ as 302-redirections
>> to the corresponding Gitiles paths.
>
> The gitweb link takes me to a diff of the whole change, while in the
> gitiles case I need one more additional click to the "diff" text to get
> there. Would it be possible to keep showing the diff by default?
Ah, yeah. There is even a custom setting in gerrit.config's “[gitweb]” section
in that effect: “revision = "?p=${project}.git;a=commitdiff;h=${commit}"” :-)
Done on our gerrit stage instance (https://vm178.documentfoundation.org/); will
do the same thing on the prod instance next time we have to restart the service.
> A second point: gitweb supports searching by name, e.g.
> <https://gerrit.libreoffice.org/gitweb?p=core.git&a=search&st=author&s=caolan>.
> Does gitiles support something like this, or from now on one must clone
> the repo to be able to do queries like this?
It does indeed, but it's a bit hidden :-P
https://gerrit.libreoffice.org/plugins/gitiles/core/+log/?author=caolan
How attached are you to the search form? We could definitely add one to
the template, but for now I only changed it (on the stage instance) to
make authors & committers clickable on the relevant views, and filter on
their email:
commit
https://vm178.documentfoundation.org/plugins/gitiles/help/+/master
commitdiff
https://vm178.documentfoundation.org/plugins/gitiles/help/+/master%5E%21
log (oneline)
https://vm178.documentfoundation.org/plugins/gitiles/help/+log/master/
log (full)
https://vm178.documentfoundation.org/plugins/gitiles/help/+log/master/?pretty=full
Cheers,
--
Guilhem.
signature.asc
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
[TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs
Dear developers,
As announced a few hours ago in the infra call minutes, we deployed
another git browser — Gitiles — alongside gitweb. It's also what the
Google folks are using (in fact they're upstream), and IMHO has quite a
nicer feel than the venerable gitweb/cgit:
* summary: https://gerrit.libreoffice.org/plugins/gitiles/core/
vs. https://gerrit.libreoffice.org/gitweb?p=core.git;a=summary
* commit: https://gerrit.libreoffice.org/plugins/gitiles/core/+/master
vs.
https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=refs/heads/master
* diff: https://gerrit.libreoffice.org/plugins/gitiles/core/+/master%5E%21/
vs.
https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=refs/heads/master
* log: https://gerrit.libreoffice.org/plugins/gitiles/core/+log/master/
vs.
https://gerrit.libreoffice.org/gitweb?p=core.git;a=shortlog;h=refs/heads/master
* tree: https://gerrit.libreoffice.org/plugins/gitiles/core/+/master/
vs.
https://gerrit.libreoffice.org/gitweb?p=core.git;a=tree;h=refs/heads/master
It also integrates better with gerrit (in the form a plugin), scales
better, and doesn't have CGI.pm's clunkiness, subtle bugs, and not so
pretty security record (yet). And of course fancy Markdown rendering is
always a plus :-)
Right now https://gerrit.libreoffice.org/#/c/$CHANGENUM/ has both gitweb
and Gitiles links, but unless we hear strong objection we'll disable
gitweb at the end of the month, and serve requests to
‘/gitweb?p=${REPOSITORY}.git;a=${ACTION};h=${REF}’ as 302-redirections
to the corresponding Gitiles paths.
Also, while AFAIK the canonical VCS browser for LibreOffice is currently
https://cgit.freedesktop.org/libreoffice/core/ , if you'd like to use
something in TDF infra, like https://git.libreoffice.org/core/, we could
alias it to https://gerrit.libreoffice.org/plugins/gitiles/core/ . (And
similarly for the other repos.)
Lastly, it's now possible to clone and fetch git repositories over
https:// . While git:// URLs will remain supported for the foreseeable
future, they're intentionally no longer advertised in gerrit, and we
encourage you to upgrade the scheme of your ‘remote..url’ to
secure transports (SSH for authenticated access, or HTTPS for anonymous
access). We'll update ‘lode’ and chase remaining git:// URLs shortly.
Cheers,
--
Guilhem, for The Document Foundation's infrastructure team.
PS: please preserve the CC when replying.
signature.asc
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Oct 16 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Oct 16 16:30:00 UTC 2018'` (18:30:00 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Sep 18 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Sep 18 16:30:00 UTC 2018'` (18:30:00 Berlin time). The meeting will take place at https://jitsi.documentfoundation.org/infra . See https://pad.documentfoundation.org/p/infra for details. Here what we have in the agenda at the moment: * New infra status page (powered by cachetHQ) + Meant to give users a quick overview, not to replace the more verbose internal infra metrics + Atom & RSS subscription + 24 HTTP sites monitored at the moment (status code only) + graph metrics for the website + Metrics and outages are automatically filled using the cachet API; scheduled maintenance can be added too, and text/status can be edited manually + Advertise the page at LibOCon? * Single Sign On + Auth method switched from SilverStripe's own backend to SAML 2.0 on the LibreOffice & TDF websites (SS3/newdesign) See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Aug 21 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Aug 21 16:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jul 17 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jul 17 16:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jun 19 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jun 19 16:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. In particular, if you have input regarding the change of authentication method for the Wiki (from username/password to SAML), feel free to send your feedback to webs...@global.libreoffice.org or add it to the pad. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, May 15 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue May 15 16:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-commits] core.git: instsetoo_native/CustomTarget_setup.mk instsetoo_native/util
instsetoo_native/CustomTarget_setup.mk |4 ++--
instsetoo_native/util/openoffice.lst.in | 28 ++--
2 files changed, 16 insertions(+), 16 deletions(-)
New commits:
commit ba69036c8e889237da4bb312d7c5c94066abbfd3
Author: Guilhem Moulin
Date: Mon Feb 5 13:00:14 2018 +0100
Upgrade update check and extension URLs to https
Change-Id: I697458fb3deba508e61e414c43fcfc85aff76f9b
Signed-off-by: Olivier Hallot
Reviewed-on: https://gerrit.libreoffice.org/49237
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/instsetoo_native/CustomTarget_setup.mk
b/instsetoo_native/CustomTarget_setup.mk
index 95de9f7202fa..315e5c825de3 100644
--- a/instsetoo_native/CustomTarget_setup.mk
+++ b/instsetoo_native/CustomTarget_setup.mk
@@ -157,11 +157,11 @@ $(call
gb_CustomTarget_get_workdir,instsetoo_native/setup)/$(call gb_Helper_get_
&& echo 'AllLanguages=$(if
$(gb_WITH_LANG),$(gb_WITH_LANG),en-US)' \
&& echo 'BuildVersion=$(BUILD_VER_STRING)' \
&& echo 'buildid=$(shell cd $(SRCDIR) && git log -1
--format=%H)' \
- && echo
'ExtensionUpdateURL=http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update'
\
+ && echo
'ExtensionUpdateURL=https://updateexte.libreoffice.org/ExtensionUpdateService/check.Update'
\
&& echo 'UpdateChannel=$(if $(ENABLE_ONLINE_UPDATE_MAR),$(shell
cd $(SRCDIR) && bin/update/get_update_channel.py $(UPDATE_CONFIG)))' \
&& echo 'ReferenceOOoMajorMinor=4.1' \
&& echo 'UpdateID=$(PRODUCTNAME)_$(LIBO_VERSION_MAJOR)_en-US' \
- && echo 'UpdateURL=$(if
$(ENABLE_ONLINE_UPDATE),http://update.libreoffice.org/check.php$(if
$(filter-out WNT,$(OS)),?pkgfmt=$(PKGFORMAT)))' \
+ && echo 'UpdateURL=$(if
$(ENABLE_ONLINE_UPDATE),https://update.libreoffice.org/check.php$(if
$(filter-out WNT,$(OS)),?pkgfmt=$(PKGFORMAT)))' \
&& echo 'UpdateUserAgent= ($${buildid}; $${_OS};
$${_ARCH}; )' \
&& echo 'Vendor=$(OOO_VENDOR)' \
) > $@
diff --git a/instsetoo_native/util/openoffice.lst.in
b/instsetoo_native/util/openoffice.lst.in
index 24bb9761f7f0..b94b7c330e40 100644
--- a/instsetoo_native/util/openoffice.lst.in
+++ b/instsetoo_native/util/openoffice.lst.in
@@ -56,7 +56,7 @@ LibreOffice
ABOUTBOXPRODUCTVERSIONSUFFIX @LIBO_VERSION_SUFFIX_SUFFIX@
BASEPRODUCTVERSION @LIBO_VERSION_MAJOR@.@LIBO_VERSION_MINOR@
PCPFILENAME libreoffice.pcp
-UPDATEURL http://update.libreoffice.org/check.php
+UPDATEURL https://update.libreoffice.org/check.php
ADD_INCLUDE_FILES
cli_ure/version/version.txt,unoil/climaker/version.txt
ADDSYSTEMINTEGRATION 1
PACKAGEVERSION
@LIBO_VERSION_MAJOR@.@LIBO_VERSION_MINOR@.@LIBO_VERSION_MICRO@.@LIBO_VERSION_PATCH@@LIBO_VERSION_SUFFIX@
@@ -68,10 +68,10 @@ LibreOffice
OOODOWNLOADNAME 1
CHANGETARGETDIR 1
PATCHCODEFILE ooo_patchcodes.txt
-STARTCENTER_ADDFEATURE_URL http://extensions.libreoffice.org/
+STARTCENTER_ADDFEATURE_URL https://extensions.libreoffice.org/
STARTCENTER_INFO_URL https://www.libreoffice.org/
-STARTCENTER_TEMPLREP_URL http://templates.libreoffice.org/
-DICT_REPO_URL http://extensions.libreoffice.org/dictionaries/
+STARTCENTER_TEMPLREP_URL https://templates.libreoffice.org/
+DICT_REPO_URL https://extensions.libreoffice.org/dictionaries/
STARTCENTER_HIDE_EXTERNAL_LINKS 0
}
active 1
@@ -107,7 +107,7 @@ LibreOfficeDev
UREPACKAGEPREFIX libreofficedev
SOLSUREPACKAGEPREFIX libreofficedev
REGISTRYLAYERNAME LayerDev
-UPDATEURL http://update.libreoffice.org/check.php
+UPDATEURL https://update.libreoffice.org/check.php
ADD_INCLUDE_FILES
cli_ure/version/version.txt,unoil/climaker/version.txt
ADDSYSTEMINTEGRATION 1
PACKAGEVERSION
@LIBO_VERSION_MAJOR@.@LIBO_VERSION_MINOR@.@LIBO_VERSION_MICRO@.@LIBO_VERSION_PATCH@@LIBO_VERSION_SUFFIX@
@@ -121,10 +121,10 @@ LibreOfficeDev
PATCHCODEFILE ooodev_patchcodes.txt
CODEFILENAME codes_ooodev.txt
LOCALUSERDIR $ORIGIN/..
-STARTCENTER_ADDFEATURE_URL http://extensions.libreoffice.org/
+STARTCENTER_ADDFEATURE_URL https://extensions.libreoffice.org/
STARTCENTER_INFO_URL https://www.libreoffice.org/
-STARTCENTER_TEMPLREP_URL http://templates.libreoffice.org/
-DICT_REPO_URL http://extensions.libreoffice.org/d
Infra call on Tue, Apr 17 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Apr 17 16:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Mar 20 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Mar 20 17:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Feb 20 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Feb 20 17:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Jan 16 at 17:30 UTC
On Tue, 09 Jan 2018 at 18:47:41 +0100, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Jan 16 17:30:00 UTC > 2018'` > (18:30:00 Berlin time). > > See https://pad.documentfoundation.org/p/infra for details; agenda TBA. Reminder: that's tomorrow! -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jan 16 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jan 16 17:30:00 UTC 2018'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Mon, Dec 18 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Mon Dec 18 17:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Nov 21 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Nov 21 17:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Oct 17 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Oct 17 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Sep 19 at 16:30 UTC
On Wed, 13 Sep 2017 at 23:20:36 +0200, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Sep 19 16:30:00 UTC > 2017'` > (18:30:00 Berlin time). Reminder: that's tomorrow! > See https://pad.documentfoundation.org/p/infra for details; agenda TBA. Here is what we currently have in the pad: * Salt refactoring + G. didn't find time to review Brett's branch unfortunately, will try to make it happen before LibOCon + Refactoring of base/mail vs. tdf/postfix is blocking on rdm#2256 hence postponed to after the conference * LDAP/SSO + deployed LDAP-based auth on the wiki and silverstripe test instances + deployed per-service ACLs (groups) for fine-grained access control + deployed an internal access log to audit DIT modifications and auth attempts * Pootle migration * LibOCon preparation -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Sep 19 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Sep 19 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Aug 15 at 16:30 UTC
On Wed, 09 Aug 2017 at 23:09:26 +0200, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Aug 15 16:30:00 UTC > 2017'` > (18:30:00 Berlin time). Reminder: that's tomorrow! > See https://pad.documentfoundation.org/p/infra for details; agenda TBA. Here is what we currently have in the pad: * Salt refactoring + Testing salt states with Docker can be difficult due to lack of init system/service manager. + Refactoring testing progress: https://infratools.documentfoundation.org/infra/salt/issues/3 + Deduplication is pretty much done. + Brett has been creating issues on gitlab's issue tracker: Should it be on redmine instead? + ufw vs shorewall: Which is supported? * Revive AOO-svn script * Migrations + gimli migrated to our infra (vm201) * Mail setup refactoring + https://redmine.documentfoundation.org/issues/2256 + https://redmine.documentfoundation.org/issues/2257 -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Aug 15 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Aug 15 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, July 18 at 16:30 UTC
On Wed, 12 Jul 2017 at 23:46:33 +0300, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Jul 20 16:30:00 UTC > 2017'` > (18:30:00 Berlin time). Reminder: that's tomorrow! Got the Subject line right but forgot to update last announcement's date, sorry :-/ I never got around to write a script to mail out infra-calls before, but that mistake convinced me it was worth spending a few mins for that :-) > See https://pad.documentfoundation.org/p/infra for details; agenda TBA. Here is what we currently have in the pad: * Salt refactoring + Merged Brett's 'cleanup' branch to master (except the submodule integration: I merged it instead in order to preserve history) + TODO We should try to remove redundancy between 'base/' and 'tdf/' directories, for instance 'base/mail/' and 'tdf/postfix/' * Migrations + Root servers kermit, pumbaa, bilbo2, intrepid, saber, and host-20150218 are gone + PENDING gimli migrated to vm201, all services are now prod-ready except OpenGrok (reindexing due to 1.0 upgrade, been groking at full load since Thu Jul 13 19:30 UTC already, not sure when that will finish) + TODO migrate gandalf to our infra * charly rebooted on Friday at 12 CEST (dirty shutdown, cause still unknown). tdfvm's mapping VM → hyper needs to be updated so we can easily recreate transient VMs (instead of consulting libvirt logs…) * Deployed LDAP auth to our TestLink instance, now waiting a couple of weeks before proceeding with other services (to see if we need a schema update) -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, July 18 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jul 20 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details; agenda TBA. Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, June 20 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jun 20 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. Here what we currently have on the pad: * General news: + TDF & LO websites migrated to a fresh Debian 8 VM on our infra + rebooted hypers and VMs to load latest kernel & libc since the upgrade to 8.8 * Salt refactoring + Proposal: Merge github salt project into the gitlab project and delete gitlab's submodules + What OSes/versions are to be supported? + Gitlab+Docker CI testing goals: - Proposal: Add the gitlab runner user to the 'docker' group so sudo doesn't need to be invoked. * Debian 9 (codename Stretch) was released on June 17, 2017 \o/ + New baseline for future VMs (test the core stalt states first) + 4 machines currently running Debian 7 (codename Wheezy, under LTS until May 31, 2018): - vm150 (bugzilla, to be upgraded/migrated) - vm164 (officeshots) - vm147 (moztrap, deprecated) - galaxy (root server, deprecated) + Other Debian machines are running Jessie, oldstable until June 2018, the LTS until April 2020 * Pending refactoring of the default mail config rdm#2256 https://redmine.documentfoundation.org/issues/2256 * cloph's currenly reshapping the large raid10 array on berta into 10x 2-disks raid 1 to avoid super long md checks * pootle: + will deploy on a dedicated root server with SSDs at manitu + to compare perfs with upstream's AWS setup + then hopefully to be the prod instance * gustl: + RX FCS counter is still going wild every now and then, still unsure what is going on + manitu changed cable and switchport, need to agree on a time to change router port (can a pb with our NIC) Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, May 16 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue May 16 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Apr 18 at 16:30 UTC
On Fri, 14 Apr 2017 at 02:50:49 +0200, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Apr 18 16:30:00 UTC > 2017'` > (18:30:00 Berlin time). Reminder: That's tomorrow! -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Apr 18 at 16:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Apr 18 16:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
https://pad.documentfoundation.org migration, Sat Mar 25 00:00 UTC
Hi there, We'll migrate etherpad-lite from a legacy Ubuntu 12 host to a fresh Debian 8 VM. The service is already up and running (thanks Brett for that!), but we still need to copy the content from the different pads and update the DNS records. The remaining step is currently planed for Sat Mar 25 00:00 UTC (01:00 Berlin time). We will then shut down the service and copy the data offline, so *please shout ASAP* if you need to use the pad on Fri-Sat (European) night! We'll pick another migration window if needed. Moreover, we'll only copy the *current* content of each pad, trashing the revision history. Please shout if that's a problem for you, so we can investigate other solutions. Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Mar 21 at 17:30 UTC
On Wed, 15 Mar 2017 at 20:19:32 +0100, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Mar 21 17:30:00 UTC > 2017'` > (18:30:00 Berlin time). Reminder: that's tomorrow! -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Mar 21 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Mar 21 17:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Feb 21 at 17:30 UTC
On Fri, 17 Feb 2017 at 10:51:19 +0100, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Feb 21 17:30:00 UTC > 2017'` > (18:30:00 Berlin time). Gentle reminder: that's in 24h! (And 17:30:00 *UTC* does not necessarily mean 17:30:00 local time :-P Enter the above command in your favorite terminal to make the conversion.) > See https://pad.documentfoundation.org/p/infra for details and a preliminary > agenda. -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [libreoffice-projects] Infra call on Tue, Feb 21 at 17:30 UTC
On Fri, 17 Feb 2017 at 17:38:12 +0100, Heiko Tietze wrote: > Jitsi still lacks on screen sharing capabilities, which is a must for > the design team. Maybe you add this to your agenda. AFAICT there is no technical blocker and nothing to discus either, it's just that I had quite a few things on my plate since FOSDEM and didn't come back to it yet. It's it in my personal TODO, but I don't think it warrants an entry in the infra call agenda :-P -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Feb 21 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Feb 21 17:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Infra call on Tue, Jan 17 at 17:30 UTC
Hi, On Mon, 09 Jan 2017 at 14:38:00 +0100, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Jan 17 17:30:00 UTC > 2017'` > (18:30:00 Berlin time). That's tomorrow :-) -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Jan 17 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Jan 17 17:30:00 UTC 2017'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Reminder: Infra call on Tue, Dec 20 at 17:30 UTC
Hey, On Tue, 06 Dec 2016 at 14:02:16 +0100, Guilhem Moulin wrote: > The next infra call will take place at `date -d 'Tue Dec 20 17:30:00 UTC > 2016'` > (18:30:00 Berlin time). That's tomorrow :-) -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Infra call on Tue, Dec 20 at 17:30 UTC
Hi there, The next infra call will take place at `date -d 'Tue Dec 20 17:30:00 UTC 2016'` (18:30:00 Berlin time). See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
infra call tomorrow (Tue Nov 15) at 17:30 UTC
Hi there, Infra calls are now taking place every 3rd Tuesday each month at 18:30 Berlin time (17:30 UTC). The next one will take place tomorrow at `date -d 'Mon Nov 15 17:30:00 UTC 2016'`. See https://pad.documentfoundation.org/p/infra for details and a preliminary agenda. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
