- Tei-council - lists.tei-c.org

call in 15 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 16 Jan '20

16 Jan '20

Dear all, Please click this link to join the call: https://meet.google.com/gxh-epwq-isq (thanks Hugh!) https://docs.google.com/document/d/1x51scPEkfUTSwdDGXxsJDLcjbjgpfVWEEDaH-18… Best, Martina

1 0

SSH access to the TEI server for the release technicians
by Peter Stadler 15 Jan '20

15 Jan '20

Dear all, can the release technicians please send me their public SSH keys so I can put them in place for logging in to the TEI server? Background: the infrastructure group decided that we’ll have a tei user (again) that will perform the release on the TEI server. For security reasons we’ll nuke the authorized_keys for that tei user after each release so only the current release technicians will have the proper permissions and can be held responsible ;) Best Peter

1 0

Reminder: Council call -- Jan 16
by Scholger, Martina (martina.scholger＠uni-graz.at) 15 Jan '20

15 Jan '20

Dear all, Our next Council meeting is scheduled for Jan 16, EDT 9:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30. Please feel free to add topics to the agenda: https://docs.google.com/document/d/1x51scPEkfUTSwdDGXxsJDLcjbjgpfVWEEDaH-18…<https://docs.google.com/document/d/1x51scPEkfUTSwdDGXxsJDLcjbjgpfVWEEDaH-18…> Best, Martina

2 1

Spring F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 13 Jan '20

13 Jan '20

Dear all, I had a final look at the doodle for the spring F2F meeting and unfortunately there is no ideal option where everyone would be available. The best option with three consecutive days in a row is May 1-3 (Friday to Sunday). Sadly, Vanessa cannot make it at those dates and Nicolas is not available for the Sunday, according to the doodle. Can the two of you look into it again please and see if you may be able to attend or if you would be available remotely? Best, Martina

1 0

Next Council call -- Jan 16
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Jan '20

09 Jan '20

Dear all, Since most of us agreed on moving the Council meeting from Tuesday, Jan 14 to Thursday, Jan 16 I can now confirm the new date: Our meeting is scheduled for Jan 16, EDT 9:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30. And this is the agenda: https://docs.google.com/document/d/1x51scPEkfUTSwdDGXxsJDLcjbjgpfVWEEDaH-18… Best, Martina

1 0

meetings and containers (was "Re: Stylesheets (and other) meeting time")
by Bauman, Syd 07 Jan '20

07 Jan '20

[Originally sent Mon, 23 Dec 2019 09:51:27 -0500, but bounced due to a networking problem here with my Northeastern machine. You may notice that this is not a true reply, just a new e-mail with a subject line that looks like it is a reply. Sigh. Note that I will likely have trouble sending e-mail for some time to come.] So, it sounds like we should move the January Stylesheets group meeting to Tue 21 Jan 20 at 14:00Z. That is: 06:00 PST 09:00 EST 14:00 GMT 15:00 CET (Do we have any other time zones represented on Council?) Unless I hear strenuous objections pretty soon, we will plan on that. I am likely to miss the Council meeting of Tue 14 Jan 20 14:00Z. (I will be traveling in London; depending on train schedules, my family, etc., I may be able to make it, but I am not counting on it.) Whether I make it or not, I hope the topic of keeping the Docker containers updated is discussed. My thoughts on this topic follow, in no particular order. * It is definitely important to keep the OS running in a Docker container up to date with security patches. It may not be as big a problem as Martin worries it is, especially if we are all vigilant in leaving a container running for the minimum amount of time necessary. But it is still important enough that we should have a process for doing it. * The solution is probably administrative, not technical. * It is probably unfair to insist that Peter and Hugh be solely responsible for doing this. (That said, if they don't object, I don't either. I would if it were only 1 person -- at least 2 people should know how to do everything that is even semi-important.) Could be a rotating responsibility. * My suggested administrative idea: Once a month, 1-24 hours *before* the Council meeting, the Docker maintainer or designee should update each container with the latest OS security patches. (Chair should send a reminder 48 hours before the meeting.) Immediately *after* the Council meeting each Council member should download and install the updated container. * Peter pointed out that doing such an update might break the build within the container. He's right, but that's no reason not to install security patches. It's a reason to fix the build process so it works on a properly updated system. Doing this on meeting day, I figure, gives us a higher chance of noticing a build fail, finding a fix, and promulgating the solution rapidly.

7 10

Update on F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Jan '20

06 Jan '20

Dear all, I wish you a happy and healthy new year! Looking at the doodle for our spring F2F meeting it seems to be almost impossible to get all of us together at one time for three days in a row. The two most promising time periods are May 18 to 22 and April 30 to May 4 I would ask everyone to check the doodle and their calendars again until Wednesday with these dates in mind and see if you could organize to make it even if you didn't pick that date before: https://doodle.com/poll/zaeh4k9kfu5wdhfp Best, Martina

1 1

Council list archive is broken
by Martin Holmes 03 Jan '20

03 Jan '20

Hi Luis, The Council list archive here: <http://lists.lists.tei-c.org/mailman/listinfo/tei-council> is currently broken, because the server has HSTS turned on, but there's no valid cert for the subdomain lists.lists.tei-c.org. lists.tei-c.org works fine, but the archive itself is on lists.lists. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

2 3

Docker containers and user permissions
by Martin Holmes 19 Dec '19

19 Dec '19

Hi all, I've just been experimenting a bit further with the docker containers, and come across something that I've found in the past, which can cause problems on *NIX systems. By default, when you run a docker container, you end up as the root user in the container. That means that when you run a build process, if you save the output to a directory that's actually on your host filesystem, those files and folders may be owned by root, and you'll then have to use sudo to remove them. What I've done in the past is to use a run command like this: docker run --user $(id -u) --name tei -v /home/mholmes/WorkData/tei:/tei -it -e TZ=America/Vancouver teic/teidev-docker which runs the docker container and logs you in with the same user id that you have on your host system (in my case 1001); that means that when files are saved from a build process, they belong to you. In some cases, you'll end up logged in with a prompt like this: I have no name!@e08387ca074c:/tei/ which means that there is no user in the container with the same uuid as your user on the host system, but that doesn't matter; files will be saved under the correct user id, so on your host system they'll belong to you, not to root. (They may have group root, but that doesn't matter if you own them.) This just makes it easier to examine and clean up any products from the build process that remain on your host filesystem. You can actually create a parallel user with the same name and uid as your own in the docker container if you like, but that will get blown away every time you remove the container, of course. Incidentally, on the issue of vulnerable docker containers, I'm not alone in being worried: <https://www.techrepublic.com/article/docker-containers-are-filled-with-vuln…> The assumption that nothing malignant can get into your docker container, and that nothing can escape from it into your host system, is I think flawed: <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14271> and in particular, if actions in the container are running as root, I believe you are running a risk. I think it's important that docker containers are regularly updated by their maintainers, but I also do run apt update and apt dist-upgrade or the equivalent as root in the container if it's one I'm keeping around. That does of course risk breaking the container's ability to do the build processes if some software the build is dependent on is updated in an unexpected way, but we want to know that anyway so we can fix it. And updating your container is no different from updating one of the live Jenkins servers, which is something I do with my server religiously every day. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

workshop "Building the TEI Guidelines locally"
by Peter Stadler 18 Dec '19

18 Dec '19

Dear all, tomorrow we’ll be having our little workshop on how to build the TEI Guidelines (and Stylesheets) locally and although I’m quite late, may I ask you to prepare your computers by installing Docker (Community Edition) [1] and download (aka ‚pull‘) the teic/jenkins image? That is, once you have Docker installed (and the Docker daemon is running; you can tell when the little Docker whale stops loading in your system tray) you simply hit `docker pull teic/jenkins` on the command line. This will take some minutes (depending on your connection) since the image is about 800 MB! Oh, and of course you will need to have a clone of the TEI [2] and the Stylesheets repo [3] on your machine. Best Peter [1] https://docs.docker.com/v17.09/engine/installation/ [2] https://github.com/TEIC/TEI [3] https://github.com/TEIC/Stylesheets

2 2