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

Stylesheets - hangouts link
by Scholger, Martina (martina.scholger＠uni-graz.at) 21 Jan '20

21 Jan '20

Dear all, This is the hangouts link for the Stylesheets meeting: https://hangouts.google.com/group/kuXq75FVLyU6w7nS7 Best, Martina

2 1

Stylesheets meeting tomorrw, Tue 20 Jan 14:00Z
by Syd Bauman 20 Jan '20

20 Jan '20

Sorry I'm late on this. (I try to post these 24 to 72 hours in advance.) As Martina just mentioned, we have a Stylesheets Group meeting scheduled for tomorrow, Tue 2020-01-21 14:00Z. timing ------ It will be: * 06:00 PST (Victoria) * 09:00 EST (New York) * 14:00 GMT (London) * 15:00 CET (Berlin) place ----- Martina will initiate a Google Hangouts session. topics ------ 0) Meeting time for next month. 1) Ticket 404.[1] 2) Ticket 403.[2] 3) Ticket 393.[3] 4) Ticket 399.[4] notes ----- [1] https://github.com/TEIC/Stylesheets/issues/404 [2] https://github.com/TEIC/Stylesheets/issues/403 [3] https://github.com/TEIC/Stylesheets/issues/393 [4] https://github.com/TEIC/Stylesheets/issues/399

1 0

Stylesheets meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 20 Jan '20

20 Jan '20

Dear all, Our next Stylesheets meeting is tomorrow: PST 6:00-7:30, EDT 9:00–10:30, GMT 14:00–15:30, CEST 15:00–16:30. I'll start the call (hangouts). Best, Martina Von meinem Huawei-Mobiltelefon gesendet

1 0

unihan call
by Scholger, Martina (martina.scholger＠uni-graz.at) 20 Jan '20

20 Jan '20

Dear all, In the last Council call on Thursday we agreed to organize a separate uniHan call. For those who want to participate: please fill in the doodle due Monday, Jan 20. https://doodle.com/poll/7izgnrr84fghp7xn Best, Martina

1 1

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 18 Dec '19

18 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

Stylesheets (and other) meeting time
by Syd Bauman 17 Dec '19

17 Dec '19

We agreed Stylesheets meetings should be 1st Tue of the month at 13:00Z. Two problems, the first with just Jan, the second more general. * I will be traveling on Tue 07 Jan; it is perhaps 50/50 I will be able to make the call, and if I do, I am likely to be a jet-lagged blithering idiot. (I am taking a red-eye from Boston to Leeds, UK overnight Mon 06 to Tue 07.) * The time is a bit of a problem for Martin. During daylight's saving time (Mar-Oct) it is 06:00, which is fine. But during standard time (Jan, Feb, Nov, Dec) 13:00Z is 05:00 PST. Thus we would not have Martin for the 1st hour of the Jan, Feb, Nov, or Dec meetings. Thoughts?

6 5

Council meeting times
by Scholger, Martina (martina.scholger＠uni-graz.at) 17 Dec '19

17 Dec '19

Dear Council, I've added our monthly Council meetings to the google calendar. We agreed that it should be the 2nd Tuesday of the month at: 9:00-10:30 (EST/EDT) / 14:00-15:30 (GMT/BST) / 15:00-16:30 (CET/CEST). Only the meeting on March 10 is affected by the switch to summer time, therefore the meeting will be at 9:00-10:30 (EDT) / 13:00-14:30 (GMT) / 14:00-15:30 (CET). Our next regular Council call is on Tuesday, January 14. Best, Martina

1 0

Is oxygen plugin message from tei-c.org incorrect?
by Elisa Beshero-Bondar 14 Dec '19

14 Dec '19

Dear TEI Councillors, Today I was showing Jessica Lu how to access the oXygen plugin from its supposedly canonical location tied to the latest release: https://www.tei-c.org/release/oxygen/updateSite.oxygen Or at least I *think* this is the correct site. Am I right about the URL? I'm writing up our documentation now for how the TEI community should install the oxygen plugin, having just walked Jessica through the process. The reason I'm suddenly uncertain about it is the message that pops up upon adding it, which warns the user, "Use this only if you are testing the plugin." Here's the message in full: DEVELOPMENT BUILD of the Oxygen TEI plugin based on the current trunk versions of TEI P5 and the TEI Stylesheets.Jenkins build number: 2019-07-18-143911. Use this only if you are testing the plugin. To avoid conflict with builtin framework, please ensure that you have gone to Preferences->Document Type Association in oXygen and deactivated all the TEI frameworks that have "External" in the storage columns. Is that the message that should be appearing with this plugin? It seems like the same message we see on the bleeding-edge plugin, and indeed it is: On installing the bleeding-edge plugin (from http://jenkins.tei-c.org/job/oxygen-tei-stable/lastSuccessfulBuild/artifact… ) the message is the same: "Use this only if you are testing the plugin. " I don't think we intend for those messages to be so much the same, do we? But I want to check with you all and make sure I have the right URLs for the plugins first. Should I open a ticket about this on the TEI oxygen plugin repo? On the verge of opening said ticket, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

2 3

Physical address for the TEI?
by Meaghan Brown 13 Dec '19

13 Dec '19

Does anyone happen to know the legal address for the TEI? I need it for bureaucratic reasons. Best, Meaghan -- Dr. Meaghan Brown

2 1

Doodle Poll Spring F2F
by Scholger, Martina (martina.scholger＠uni-graz.at) 12 Dec '19

12 Dec '19

Dear all, I apologize for this horrible doodle for planning our spring F2F meeting: https://doodle.com/poll/zaeh4k9kfu5wdhfp In our meeting on Tuesday we decided to do another doodle poll on times and decide for a place afterwards. The F2F meeting lasts 3 days (+ travel time). Please fill in the doodle as soon as possible. Best, Martina

1 0

standOff problem #1: content model of <teiCorpus>
by Syd Bauman 11 Dec '19

11 Dec '19

The current content model of <teiCorpus> is: teiHeader, ( ( model.resourceLike+, ( TEI | teiCorpus )* ) | ( TEI | teiCorpus )+ ) ) That is, you may *either* have a series of 1 or more <TEI> and <teiCorpus> elements, intermingled; OR you can have one or more of <facsimile>, <fsdDecl>, <sourceDoc>, and <text> elements intermingled followed by zero or more <TEI> and <teiCorpus> elements intermingled. This is exactly the same as saying teiHeader, model.resourceLike*, ( TEI | teiCorpus )* except that it requires at least one child <TEI>, <teiCorpus>, <facsimile>, <fsdDecl>, <sourceDoc>, or <text>. In the new <standOff> world, we have voted to make <TEI> a member of model.resourceLike. Thus we have to alter the content model of <teiCorpus> because as written it would be ambiguous (if a <TEI> is your first child after <teiHeader>, you don't know which branch of the content model you are in). It is not too difficult to solve the ambiguity problem: teiHeader, ( ( model.resourceLike+, ( teiCorpus, ( TEI | teiCorpus )* )? ) | ( teiCorpus, ( TEI | teiCorpus )* ) ) ) I am pretty confident this content model validates the same set of documents (and, perhaps as importantly, rejects the same set of documents) as the original content model (with <TEI> in model.resourceLike). I am not against using this content model. But it occurs to me that a) it is a bit cumbersome b) the set of documents permitted is already screwy c) it looks very different from the content model of <TEI>, which (in the new world order) <teiCorpus> is very similar to. One possible solution is to 1) add <teiCorpus> to model.resourceLike, too; and then 2) change content model of <teiCorpus> to match that of <TEI> (in the new standOff world): teiHeader, model.resourceLike+ This has the advantage of having a very clean, understandable content model for <teiCorpus> (and no ambiguity). It has the disadvantage that it allows for even more screwy things. E.g. <teiCorpus> <teiHeader> <standOff> <TEI> <facsimile> <TEI> <teiCorpus> <TEI> <facsimile> <TEI> <teiCorpus> <facsimile> </teiCorpus> It has the feature (which some will consider an advantage, others a disadvantage, I'm sure) that <TEI> and <teiCorpus> become the same thing. Just as an XSLT stylesheet can have an outermost element of <xsl:stylesheet> or <xsl:transform>, no difference, a TEI document will be able to have <TEI> or <teiCorpus> as an outermost element, no difference. Same goes at every level of nesting where one is allowed: so is the other, and it can have the same content. Personally, I still think putting <TEI> into model.resourceLike was probably a mistake, but once we've done that, I'm inclined to say throw <teiCorpus> in there, too.

7 10

CI for standOff
by Syd Bauman 11 Dec '19

11 Dec '19

Dear CI server maintainers -- Would it be possible to add the the "sydb-standOff" branch to one or more of the contiuous integration server lists of branches-to- build? I can build it locally, but am soon to send out mail asking that people look at the changes and play with the result. Having a CI copy would make that easier on folks. If not I can certainly put the build I generate up on the web somewhere.

3 2

Unihan etc.
by Martin Holmes 10 Dec '19

10 Dec '19

Hi all, Following today's discussion, I posted a brief summary on the pull request: <https://github.com/TEIC/TEI/pull/1901> Please read and feel free to edit/expand where necessary. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

Triangle SCI and possible Mellon grant
by Hugh Cayless 10 Dec '19

10 Dec '19

Hi all, I was supposed to send this a couple of weeks ago. My apologies. In October, Martina and I, along with several other folks, were at the Scholarly Communications Institute here in NC. Our group was focused on doing something about better internationalizing the TEI, including improving the translation process, introductory materials, etc. At the end, we were approached by Patricia Hswe, who’s a program officer at Mellon about possibly putting together a proposal to do some of this work. The following document is a kind of summary of our conclusions plus some ideas for how extra funding might help: https://docs.google.com/document/d/1TPuMHN4ZxklX5JlLo7HEFmEgTiUvuRD0cxDFE65… Patricia would like us to submit a prospectus, which would lead to a grant proposal if it is accepted. Your thoughts are, of course, welcome. So, interesting times! Hugh Sent from my phone.

1 0

delete git branch?
by Syd Bauman 10 Dec '19

10 Dec '19

I re-named the "nest_TEI_deprecate_teiCorpus" branch to "sydb_standOff". That really means, of course, that I copied it. If we delete the old one, is the history still kept in the new one? (Looking at [1] it looks like the history would be kept, and we can just delete the old one.) Notes ----- [1] https://github.com/TEIC/TEI/commits/sydb_standOff/P5/Source/Specs/TEI.xml

2 1

Next call: Tuesday, December 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Dec '19

09 Dec '19

Dear all, this is a reminder for our next call on Tuesday, December 10 (PST 6:00-7:30, EDT 9:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30) We will start with the discussion on uniHan and standoff since Martin will kindly be joining us and has to head off to work at 7. Please have a look at the agenda and add your topics: https://docs.google.com/document/d/10zJFdN-p2WxGFTiRC8dMySCKe8QQ043lam1WFxz… Best, Martina

3 3