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

plan for Stylesheets, and versions, and tags, oh my!
by Syd Bauman 03 Jun '20

03 Jun '20

At one point we had a Stylesheets meeting planned for this Tue 02 Jun at 13:00Z. Various other plans have cropped up since. Basically, Elisa, Martin, Peter, and I have not finished the Stylesheets categorization project; although we have made good progress, we still have more to go, and would like to use that time slot. Furthermore, Peter has suggested (and I readily agree) that we, Council, need to talk about teidata.version. Thus my suggestion is 1. a 1-hour meeting at 13:00Z with as many Council members as will show up to discuss version numbering and (time permitting) Stylesheets 2. a 1-hour meeting at 14:00Z of PS & SB and MH & EB to do more Stylesheets labeling. I, for one, have another meeting at 15:00Z which I do not want to be late for.

10 11

Do we need better issues?
by Raffaele Viglianti 29 May '20

29 May '20

Hi all, After today's meeting, I started thinking about why we often end up in loops of discussion. Keeping in mind that this is a partial and personal view, I think that this happens for a few reasons: some are good (e.g. disagreement that needs to be worked out), some are ok (e.g. someone forms an opinion while missing a key piece of context --mea culpa), others are due to the ticket (e.g. it's verbose, it's unclear, it's too short, the discussion is long, etc.) To address the latter, I think we need to ask more of our submitters (including ourselves when creating issues). Each issue should state clearly what the problem is, show clear examples, and offer a solution. Many issues do (I think of the UVic ones are particularly exemplary, however extreme their requests may often appear to me :) ), but the style varies too much and it makes it time consuming for us to figure out what the real issue is and to reprise quickly on second iterations. I wonder if a strict issue template may help us here. GitHub allows to configure multiple templates <https://help.github.com/en/github/building-a-strong-community/using-templat…> (e.g. a bug report template could be default, with the possibility to switch to a feature request one, and perhaps others). Templates pre-populate an issue with headers and a description of what's required for consideration, thus at least encouraging a standardized way of formulating a bug report/feature request. Even if these templates were fairly simple we would still benefit. But I think we could go further and take inspiration from software design documents as a template, which will require the issue reporters to not just do their research, but present it properly too. The DocNow project at MITH creates such documents (publicly) to help discussion within the dev group, and as a crucial means to remind ourselves of why we set to do something (because we all work on dozens of projects and forget things). Here is a very good example <https://www.docnow.io/design/2019-05-21-conversation>. I think forcing this on submitters will weed out partially thought out requests, which will always result in us at least wasting time at best closing or getting back to the submitter, at worst engage in loopy "what if" discussions. We have plenty of issues, so I'm not worried about scaring people away. In fact, i wonder if more structure may even encourage less proficient users to contribute more meaningfully. Templates will also give us -- hopefully -- clearer requests with a proposal for a solution built-in. What do you think? Finally, if we did choose to use this GitHub feature, we should also look at their recommendations for adding a code of conduct <https://help.github.com/en/github/building-a-strong-community/adding-a-code…>. TEI's is hidden deep in the tei-c site <https://tei-c.org/about/code-of-conduct/> but we may want to bring it into the repository and close to the issue submitting process. Thanks for indulging me and I'm well prepared to be told that this in an unnecessary complication and that we should proceed as usual :) Best, Raff

6 6

labels for Stylesheets issues
by Syd Bauman 25 May '20

25 May '20

Martin and I came up with a proposed list of labels for Stylesheets issues today. My suggested schedule is that over the next week we review and tweak the list as needed. Then on or about Sun 17 May someone who has some color sense will go ahead and actually change the label values in GitHub. Then during the week of the 18th, flowing over to the week of the 25th as needed, the subgroups (SB, PS, MH, EB|MS) work on categorizing the 139 open issues with the new labels. The list proposed is not intended to be definitive. I expect it to be adjusted both now by Council, and then during the actual cataloging exercise. So take a loot at https://docs.google.com/spreadsheets/d/1TugARD1amG-ZeMPl2Fo-e88VXqirHawmOs5… and comment away.

6 15

meeting in 30 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 May '20

19 May '20

Dear all, Our meeting starts in 30 minutes. Please find the zoom meeting link in the google doc: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU… Best, Martina -----Ursprüngliche Nachricht----- Von: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Gesendet: Samstag, 16. Mai 2020 21:16 An: tei-council <tei-council(a)lists.tei-c.org> Betreff: Meeting on Tuesday Dear all, In our last meeting we agreed to continue one more time with reviewing issues from the VF2F on Tuesday, May 19 at 9:00 EDT, 14:00 BST, 15:00 CEST. Please find the zoom meeting link in the google doc: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU… Best, Martina Von meinem Huawei-Mobiltelefon gesendet

1 0

Meeting on Tuesday
by Scholger, Martina (martina.scholger＠uni-graz.at) 16 May '20

16 May '20

Dear all, In our last meeting we agreed to continue one more time with reviewing issues from the VF2F on Tuesday, May 19 at 9:00 EDT, 14:00 BST, 15:00 CEST. Please find the zoom meeting link in the google doc: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU… Best, Martina Von meinem Huawei-Mobiltelefon gesendet

1 0

Council meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 May '20

11 May '20

Dear all, For the Council meeting tomorrow (9:00 EDT, 14:00 BST, 15:00 CEST) we continue with our tickets review in the VF2F google doc: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU…<https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU…> The link to the zoom meeting is the same - see beginning of the document. Best, Martina

1 0

reuse TEITechnicalCouncil user at GitHub as DockerHub build bot
by Peter Stadler 07 May '20

07 May '20

Dear all, you might have received a notification from GitHub that I added the docker-pkp-ojs repo to the TEIC realm at GitHub. Next, I wanted to integrate with DockerHub for automated builds but DockerHub changed something (already some time ago) in that step that makes it necessary to re-connect a GitHub account with DockerHub. They recommend to use a dedicated service user for that rather than using an individuals account because otherwise the whole TEI group/organization at DockerHub would get access to that individuals repositories. Makes sense … So, I’m now looking for a service account I could use and found the existing user TEITechnicalCouncil – which is not really needed, methinks? The only caveat I see is that this user is currently in the group „owners“ and has admin access to all repositories. We should downgrade that user but that might have side effects? If I was to create a new account at GitHub I’d need an email-address that is not already registered with GitHub. So, it'd probably result in two new accounts which seems a bit messy to me. Any objections to downgrading the TEITechnicalCouncil user and turning that into a bot? If I do not receive any objections I will proceed in that direction. Best Peter

4 4

Meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 04 May '20

04 May '20

Dear all, For our Council meeting tomorrow (9:00 EDT, 14:00 BST, 15:00 CEST) I propose that we continue with our tickets review in the VF2F google doc: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU… The link to the zoom meeting has not changed (see beginning of the document). Best, Martina

1 0

Virtual F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 30 Apr '20

30 Apr '20

Dear all, Our Council meeting is just around the corner. Please find the schedule and agenda for our virtual F2F meeting here: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU…<https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU…> The Zoom-Link for the meeting is in the document. Meeting Times: Friday, May 1 all 09:00-13:00 EDT 14:00-18:00 GMT 15:00-19:00 CEST Saturday, May 2 European break-outs 9:00-12:00 GMT 10:00-13:00 CEST all 09:00-13:00 EDT 14:00-18:00 GMT 15:00-19:00 CEST American break-outs 15:00-18:00 EDT Sunday, May 3 all 09:00-13:00 EDT 14:00-18:00 GMT 15:00-19:00 CEST Looking forward to seeing you tomorrow! Best, Martina

1 0

Virtual F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 24 Apr '20

24 Apr '20

Hi all, this is the preliminary schedule for our virtual F2F meeting next week: https://docs.google.com/document/d/1tIA1pWABSJlL9KfCwK6t6zwVXm762LNAbvs45YU… Please feel free to comment on that. You can find the Zoom-Link in the Google Doc Meeting Times: Friday, May 1 all 09:00-13:00 EDT 14:00-18:00 GMT 15:00-19:00 CEST Saturday, May 2 European break-outs 9:00-12:00 GMT 10:00-13:00 CEST all 09:00-13:00 EDT 14:00-18:00 GMT 15:00-19:00 CEST American break-outs 15:00-18:00 EDT Sunday, May 3 all 09:00-13:00 EDT 14:00-18:00 GMT 15:00-19:00 CEST I'll have a look at the Guidelines and Stylesheeet issues and will add a table with issues that 'need discussion' soon. Best, Martina

1 0

Fresh assignments
by Peter Stadler 22 Apr '20

22 Apr '20

Dear Council friends, being in charge of ticket triage for this month I assigned a bunch of fresh tickets to members of this group. I tried to find appropriate matches for teams of liaisons but please bear with me if you might find that particular ticket, well, not suited … That said, you don’t have to ‚solve‘ those issues, just sheperd them and find someone to do it ;) So currently, for the TEI repo all tickets have someone assigned while for the Stylesheets there are more than 100 open issues without any assignment [1]. Here, I only assigned the most recent tickets that were not created by Council members (including Martin and Lou) themself. Cheers Peter [1] https://github.com/TEIC/Stylesheets/issues?q=is%3Aissue+is%3Aopen+no%3Aassi…

1 0

procrastination = analysis of Google chars
by Syd Bauman 15 Apr '20

15 Apr '20

I just did a fast-and-lousy analysis of the URLs of 78 of our GoogleDocs. In particular, I looked at the 40-character random-gobbledy-gook looking part after “/document/d/”. Call it “rgg”. Interestingly (to me, at least) each one is an NMTOKEN (in SGML parlance; in XML that is an Nmtoken (production [7]), or in W3C regex that means would match "\c{40}", or more precisely "[A-Za-z_-]{40}"). None are NAMES (or Names, production [5]), because they *all* start with the character ‘1’. Thus they all match the regular expression "1[A-Za-z_-]{39}". Using Unicode general category symbols, the frequency of character occurrences is as follows. 1409 Lu 1358 Ll 564 Nd 54 Pd 47 Pc Remember that each rgg starts with ‘1’. So if we factor those out, we get a frequency set of 1409 Lu [A-Z] 1358 Ll [a-z] 486 Nd [0-9] - ^1 78 I1 ^1 # I made that symbol up; it's for Initial 1 54 Pd - 47 Pc _ If characters are assigned randomly, we would expect the frequencies of Lu and Ll to be roughly equal, and roughly 2.6 times that of Nd; further, we would expect Pd and Pc (as single characters each) to occur 1/10th as often as Nd, and 1/26th as of Lu or Ll. And, on eyeballing them, those values are not far from expected. (For example, 54 * 26 is 1404, which falls in the 1358–1409 range.) But not all that close, either. (For example, 2.6 × the higher number for Nd is 1466, somewhat higher than Lu; but 2.6 × the lower number for Nd is 1264, somewhat lower than Ll.) But my guess is that another few hundred URLs would be needed to be more confident. (I am not a statistician, though.) Raw frequencies: 135 1 75 E 67 J 66 C 65 e 64 s 61 V 60 Z 58 4 58 B 58 D 58 h 58 M 58 n 57 d 57 g 57 G 57 k 57 l 56 b 56 P 56 Q 55 6 55 K 55 X 55 y 54 - 54 a 54 H 54 w 54 Y 53 A 53 j 53 t 53 v 53 x 52 L 52 N 51 f 49 0 49 8 49 q 49 W 48 7 48 F 48 p 48 U 47 _ 47 3 47 I 47 u 46 O 46 r 45 2 45 o 45 R 44 c 43 T 42 z 41 9 41 i 41 m 37 5 36 S OK. Back to what I should have been doing, which is review the minutes Martina asked me to look at yesterday.

1 0

council meeting in 50 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 14 Apr '20

14 Apr '20

Dear all, Our call starts in 50 minutes, sorry I added the wrong time (for the Europeans) in my last email. We start at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30. I set up a zoom meeting, the meeting link is https://zoom.us/j/188592360?pwd=dTJ3TUxqaVhXS3ZMdEFHT0dNVEErQT09 Please find the agenda here: https://docs.google.com/document/d/1p_FKVqTkdaJe7asuyk4ybT5s95u-OTuEwR5Gkha…<https://docs.google.com/document/d/1p_FKVqTkdaJe7asuyk4ybT5s95u-OTuEwR5Gkha…> Martina

1 0

Next Council meeting: April 14
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Apr '20

09 Apr '20

Dear all, our next regular Council meeting is on Tuesday, April 14 at EST 09:00-10:30, GMT 13:00-14:30, CEST 14:00-15:30. I set up a zoom meeting, the meeting link is https://zoom.us/j/188592360?pwd=dTJ3TUxqaVhXS3ZMdEFHT0dNVEErQT09 Please find the agenda here: https://docs.google.com/document/d/1p_FKVqTkdaJe7asuyk4ybT5s95u-OTuEwR5Gkha… Have a nice Easter weekend! Martina

1 0

GitHub group permissions
by Peter Stadler 08 Apr '20

08 Apr '20

Dear all, (some of) you might have received a notification from GitHub about changed group/team permissions. That was me … I was just looking through our repositories and added the Council team to most of the repos (where missing) and granted us the „maintain“ role (while removing individuals from those repos). That should be more permissive as it was before but I don’t see any reason why Council members should not (by default) have the maintain role for repositories maintained by the TEIC. Cheers Peter

1 0

upcoming Stylesheets meeting, Tue 07 Apr 13:00Z
by Syd Bauman 07 Apr '20

07 Apr '20

We are planning to meet this coming Tue 1t 13:00Z. That's * 06:00 PDT * 09:00 EDT * 14:00 BST * 15:00 CEDT I'd like to take a look at two tickets, if we have time. 1) 326 (https://github.com/TEIC/Stylesheets/issues/326) Martina has yet to suggest a fix, but perhaps we should tackle this as a group. Martin & I think this fits in well with respect to our discussion last Tue, as the hard part of this is most likely finding the (various) place(s) where the @xml:id needs to be converted to @id. (The conversion itself is, almost assuredly, quite easy.) 2) 323 (https://github.com/TEIC/Stylesheets/issues/323) Georg has already provided a possible fix, so this may be as easy as putting his suggestion in place. I presume we're meeting on Google Hangouts, but someone tell me if y'all prefer Zoom.

2 1

Thank you!
by Scholger, Martina (martina.scholger＠uni-graz.at) 02 Apr '20

02 Apr '20

Dear Council, I got the lovely picture of our dinner at my house delivered yesterday. I’m delighted and will pick a place of honor for it. I still remember the wonderful evening we had – and I still find pieces of tin foil from the confetti cannon whenever I am in the garden 😊 I hope to see you all in real life again soon. Thank you so much! Best, Martina

1 0

Re: [Tei-council] Main tei-c site is down
by James Cummings 02 Apr '20

02 Apr '20

Thanks Peter (and Martin for a separate email). A symlink or similar was the kind of thing I was envisioning (though then the upgrade process needs to change it, right?). Sorry I can't make this IG meeting but do still intend to return! Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Peter Stadler Sent: Thursday, April 02, 2020 17:17 To: James Cummings Cc: Luis Meneses; Hugh Cayless, Ph.D.; tei-council(a)lists.tei-c.org Subject: Re: [Tei-council] Main tei-c site is down Hi James, maybe someone has answered off list already? Anyway, there’s a infrastructure group meeting scheduled for tonight and I just added the issue to the agenda. Thanks for the heads up! Best Peter > Am 31.03.2020 um 20:10 schrieb James Cummings <James.Cummings(a)newcastle.ac.uk>: > > Just to ask, is that not likely to break again at next PHP upgrade? Is there a way to point at the location of the 'default current php'. (I believe there is for some things in ubuntu, hence why I ask). > > > Many thanks, > James > > -- > Dr James Cummings, James.Cummings(a)newcastle.ac.uk > Senior Lecturer in Late-Medieval Literature and Digital Humanities > School of English, Newcastle University > From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Luis Meneses <ldmm(a)uvic.ca> > Sent: 31 March 2020 17:53 > To: Peter Stadler <pstadler(a)mail.uni-paderborn.de> > Cc: Hugh Cayless, Ph.D. <hugh.cayless(a)duke.edu>; tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> > Subject: Re: [Tei-council] Main tei-c site is down > > Hi All, > > I am just sat on my desk at home and saw this email and the notices from the downtime. > It looks like the PHP update was the culprit. > > Many thanks to Hugh for fixing this! > > Best, > -Luis > > > > On Mar 31, 2020, at 7:02 AM, Peter Stadler <pstadler(a)mail.uni-paderborn.de> wrote: > > > > Hugh already fixed it by replacing `unix:/run/php/php7.0-fpm.sock` with `unix:/run/php/php7.3-fpm.sock` in the files at /etc/nginx/sites-enabled/ – right? > > > > Cheers > > Peter > > > >> Am 31.03.2020 um 15:48 schrieb Martin Holmes <mholmes(a)uvic.ca>: > >> > >> Hi Luis, > >> > >> The tei-c.org site is down, along with the wiki, although the Guidelines still seem to be up. > >> > >> Cheers, > >> Martin > >> _______________________________________________ > >> Tei-council mailing list > >> Tei-council(a)lists.tei-c.org > >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council

3 2

Main tei-c site is down
by Martin Holmes 02 Apr '20

02 Apr '20

Hi Luis, The tei-c.org site is down, along with the wiki, although the Guidelines still seem to be up. Cheers, Martin

4 4

zoom
by Scholger, Martina (martina.scholger＠uni-graz.at) 31 Mar '20

31 Mar '20

https://zoom.us/j/452506393 Mag. Dr.phil. Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at<https://informationsmodellierung.uni-graz.at/> | https://gams.uni.graz.at<https://gams.uni.graz.at/> Institut für Dokumentologie und Editorik e.V. | https://i-d-e.de<https://i-d-e.de/> Chair of the TEI Technical Council | http://tei-c.org

1 0

Stylesheets tutorial meeting
by Syd Bauman 31 Mar '20

31 Mar '20

Reminder: our stylesheets tutorial meeting is scheduled for tomorrow, Tue 25 Feb at 14:00Z. That is: * 06:00 PST * 09:00 EST * 14:00 GMT * 15:00 CET I presume we will meet on Google Hangouts. Please have a local working copy of the Stylesheets repo[1] checked out (whether within Docker or not does not matter, I don't think). We will be relying on a few slides[2], a pair of images[3], and the mapping wiki page[4]. Notes ----- [1] https://github.com/TEIC/Stylesheets.git [2] Martin's anatomy_of_a_transformation [3] https://www.wwp-test.northeastern.edu/outreach/seminars/_utils/gfx/tei_odd_…, https://www.wwp-test.northeastern.edu/outreach/seminars/_utils/gfx/tei_odd_… [4] https://wiki.tei-c.org/index.php?title=Mapping_ODD_processing

3 5

next call: Tuesday, Feb 11
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Mar '20

23 Mar '20

Dear all, our next Council call is on Tuesday, February 11 (EDT 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30). Please add topics to the agenda: https://docs.google.com/document/d/1hlKcKJJqW-LV0_-Q3rZQJqBxXySk_fA8qEJWlAu… We do not have a clear result for the F2F meeting location yet - so please fill in the doodle if you haven't done so far: https://doodle.com/poll/vpncpziivf4fcfn6 Best, Martina

7 14

Stylesheets meeting Tue 17 Mar 13:00Z
by Syd Bauman 16 Mar '20

16 Mar '20

We are planning to meet for ~1.5 hours this coming Tue 17 Mar at 13:00Z. That's * 06:00 PDT * 09:00 EDT * 13:00 BST * 14:00 CEDT I presume we are meeting on Google Hangouts unless someone tells me otherwise. Agenda ------ * Double-check logistics of Stylesheets orientation meeting, currently scheduled for Tue 31 Mar at 13:00Z. (Can someone put that on the Google Calendar?) * Check-in on previous progress (mostly 'cause I forget) * Ticket #396 [1] * Ticket #408 [2] As always, feel free to propose other agenda items. Notes ----- [1] https://github.com/TEIC/Stylesheets/issues/396 [2] https://github.com/TEIC/Stylesheets/issues/408

2 1

call in 10 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Mar '20

10 Mar '20

Dear all, our call starts in 10 minutes: https://docs.google.com/document/d/1sTII6OoW8O9jx_1Bns897Q_E63or2GDhZbxJygf… Best, Martina

1 0

Next call: Tuesday, 10 March
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Mar '20

08 Mar '20

Dear all, This is the agenda for our next Council call on Tuesday (EST 09:00-10:30, GMT 13:00-14:30, CEST 14:00-15:30). https://docs.google.com/document/d/1sTII6OoW8O9jx_1Bns897Q_E63or2GDhZbxJygf… For the Europeans - please note that we start an hour earlier than usual since the States already changed to summer time. Best, Martina

1 0

crossing fingers for Paderborn
by Syd Bauman 08 Mar '20

08 Mar '20

Checking https://wwwnc.cdc.gov/travel/notices and https://travel.state.gov/content/travel/en/international-travel/Internation… things still look good for our face-to-face. Hoping it stays that way.

1 0

UA waiving changing fees
by Raffaele Viglianti 06 Mar '20

06 Mar '20

Dear US-based colleagues, United Airlines announced that they will be waiving changing fees for flights booked in march. They fees will be waived for 12 months. I'll look into taking advantage of this for the F2F trip, if costs are reasonable from DC. Hopefully other airlines will follow, but let's hope we just get to see each other in May! Link below. Raff https://news.united.com/pub/sf/FormLink?_ri_=X0Gzc2X%3DYQpglLjHJlTQGmg3uzf6…

4 3

I hate to bring this up, but...
by Hugh Cayless 27 Feb '20

27 Feb '20

We should perhaps be thinking about contingency plans for the F2F, in case we're hit by travel restrictions related to Covid-19. I'm not suggesting calling it off at this stage, but we should be aware of the risks. I'll note that Facebook tells me Elena Pierazzo is under 2 weeks quarantine at home after returning from Italy. So it's far from impossible. And that said, I will almost certainly not be able to make it in person. If things go according to plan, my wife will be in the middle of radiation therapy then. (It's ok—her prognosis is excellent, given what we know right now, but I'm not going to leave for several days under those conditions.) I'd like to participate remotely to the extent I can. Hugh

3 4

Fwd: TEI Question
by Elisa Beshero-Bondar 24 Feb '20

24 Feb '20

Dear Council colleagues, Can any of you shed light on this interesting question? Are we indeed using the words "licence" and "license" inconsistently in the Guidelines vs. the website? Best, Elisa ---------- Forwarded message --------- From: Sarah Ketchley <ketchley(a)uw.edu> Date: Sun, Feb 23, 2020 at 9:09 PM Subject: TEI Question To: Elisa Beshero-Bondar <ebb8(a)pitt.edu> Hi Elisa, I hope you are well! I have a question about spelling on the TEI website and in its guidelines. One of my eagle-eyed students in the Intro to DH class I’m currently teaching questioned the spelling of the TEI element < licence <https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-licence.html>>. My immediate response was that it was based on British English, but then I started digging around the website, and came to the ‘Licensing page’ : https://tei-c.org/guidelines/licensing-and-citation/ where the noun is spelled ‘license’. Any insights on this?! Sorry to throw a left-fielder at you! best Sarah [image: Newbook Digital Texts] Dr. Sarah Ketchley / Egyptology | Digital Humanities ketchley(a)uw.edu University of Washington Department of Near Eastern Languages & Civilization M220D Denny Hall www.emmabandrews.org www.sarahketchley.com www.newbookdigitaltexts.org [image: Twitter] <https://htmlsig.com/t/000001CSRE2Z> [image: Facebook] <https://htmlsig.com/t/000001CP3HD8> [image: LinkedIn] <https://htmlsig.com/t/000001CP21K7> [image: Github] <https://htmlsig.com/t/000001CMN2AT> -- 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

3 2

Debian 9 -> Debian 10
by Luis Meneses 21 Feb '20

21 Feb '20

Hi All, I received an email from Joel at Huma-num about migrating two of our servers (web server and svn server) to Debian 10. I am including the translated message below. In this case, the migration path is an easy one since Huma-num is offering to do it for us. I will ask Joel for a timeframe when this will happen, but the transition should be transparent for us. Best, ----- -Luis Translation (courtesy of https://translate.google.ca) You are in charge of the administration of one or more virtual machines under Linux Debian 9, which run on our infrastructure. Debian 9 support for the Debian project has expired. All that remains is community support in "best effort" mode. We therefore invite you to plan the migration to Debian 10, which is as always easy, and must be almost transparent in a large part of the cases. We can of course help you to accompany you in this migration: - we do it - you validate in the process that everything works, and correct any concerns if necessary. NB: an easy and quick backtrack is always possible if in the last hours you have not changed the data contained in your virtual machine. This via the snapshot mechanism of our NetApp file server. ----- -Luis

2 2

on the content of <mapping>
by Syd Bauman 19 Feb '20

19 Feb '20

There are 21 examples of <mapping> in the _Guidelines_, and 5 different methods of representing the content thereof. (Although three of these methods are variants of the same idea.) The content model of <mapping> is macro.xtext, thus it can have only character data or <g>. Of the 21 of them, the desired mapping is represented in the content as: * straight character content in 15 (1 of those is multi-character, the rest are single characters); * numeric character references[1] in 3 (1 of those is multi-character, the others are single characters); * a <g> element in 1; and * the standard Unicode representation[2] in 2, i.e. they match "U\+[0-9A-F]{4,6}". The first three are variations of the same theme: the *content* of <mapping> *is* the character to which the character or glyph being defined should be mapped (whether expressed as character data, NCR(s), <g>(s), or some combination thereof). The last is entirely different. I think we can all agree that <mapping>U+00B5</mapping> means that the character or glyph currently being defined should be mapped to a single character µ = µ = µ = <g ref="#micro"/>, NOT a sequence of 6 characters U+00B5 = U+00B5. (Note that in the examples in _Guidelines_, the Unicode standard notational convention is used for all <mapping type="PUA">, and no other types of <mapping>.) But, as far as I know *nowhere* is this (the use of Unicode standard notation) mentioned in the _Guidelines_. Although I may be wrong about this, I do not think it would ever make sense to map a <char> onto a literal string "U+0123" (or "V=3456"). Furthermore, I think use of Unicode notation is a *really* good idea, *especially* if the character being represented is in the PUA; furthermore I suspect that the intention of whoever wrote this in the past was just that: Unicode standard convention should be used rather than actually putting PUA characters in a document instance. Thus I think the right solution is to: a) Have a _suggest values include_ list for mapping/@type (after all, we have it in the prose, sort of). b) Add some prose to 5.2 (#D25-20) that explains that in general "U+0123" notation may be used instead of "ģ" or "ģ", and that if the mapping is to the PUA area, this is the (vastly) preferred method. c) If anyone thinks it important to be able to map to absolutely arbitrary strings, then pick some value of @type (say "exact") for which use of "U+0123" would actually map to the string "U+0123". Notes ----- [1] Of course, they occur with "&" instead of an actual ampersand if you are reading the source. [2] Per the Unicode Standard Appendix A, "Notational Conventions".

2 3

guidance on last char of each <desc>
by Syd Bauman 18 Feb '20

18 Feb '20

labels: * TEI: Guidelines & Documentation * Priority: Low * CouncilResponsibility I had intended to submit a ticket on this topic, but after a bit of research realize I don't know what the ticket should say. So I'm asking for guidance from y'all -- what should we do about the following issue? IIRC, in general a <desc> should be 1 sentence that does not start with a capital letter, but does end in a full stop. By my count there are 10,475 <tei:desc> elements in the _Guidelines_. (That's not counting the 228 that are inside <egXML>; they are <teix:desc> elements that probably should be addressed, too.) Of those, 7689 end in a full stop,[1,2] and the other 2786 do not. That's a lot. Of course some of them should not end in full stop (e.g., those that end in ".)" or those that should not be a <desc> at all like the gloss of the value "group" of the @org attribute of <attList>). But most, I suspect, should. What to do? I submit that a) 2786 is way too many for manual intervention b) there are a bunch that end in screwy characters that probably need to be looked at (e.g., '>', superscript digits, '*') c) I am utterly unqualified to deal with non-English cases One thought is to divvy them up by language, so that (for example) I only have to deal with English, and ask for help for the other languages (perhaps ask Peter or Martina to deal with the German cases, Martin the Japanese, Raff the Italian, Alejandro the Spanish). Each language would be much more manageable on its own, I suspect. At least, the English certainly would be. There are only 9 categories: 1424 . 404 [a-z] 15 ) 2 [superscript digit] 2 [A-Z] 1 5 1 … 1 " 1 ; After some spot-checking, I would not be surprised if it made sense to automatically insert a period after all the [a-z] and ')' cases, leaving only 8 cases (in 6 categories) to be examined by hand. Thoughts? In case you want to see them (clicking on a column headings sorts): * All of them: https://bauman.zapto.org/~syd/temp/4TEICouncil/last_of_the_descs/lotd.xhtml * Only those that end in something other than full stop: https://bauman.zapto.org/~syd/temp/4TEICouncil/last_of_the_descs/lotdnfsonl… * Only those that are in English: https://bauman.zapto.org/~syd/temp/4TEICouncil/last_of_the_descs/lotend.xht… * Only those that are in English and do not end in full stop: https://bauman.zapto.org/~syd/temp/4TEICouncil/last_of_the_descs/lotendnfso… Notes ----- [1] I get bizarrely different results with different counting methods, not sure why. [2] 1002 are U+3002, IDEOGRAPHIC FULL STOP, mostly in zh-TW, but 57 in ja 1370 are U+FF0E, FULLWIDTH FULL STOP, most if not all in ja 5317 are U+002E, FULLSTOP, in lots of other languages

1 0

Travis check failures
by Martin Holmes 14 Feb '20

14 Feb '20

Hi all, I haven't really been involved in the setup of the Travis checks, so I don't really know what they're doing. Ron has made a pull request which I'd like to approve: <https://github.com/TEIC/Stylesheets/pull/420/> (I don't see anything wrong with it), but the Travis checks are failing. I can't see how to tell what checks have failed or why they've failed. When I ask Travis to re-run the checks, it shows "Re-running checks", but never seems to complete. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

2 2

model.resource
by Peter Stadler 14 Feb '20

14 Feb '20

Hy Syd (hold you responsible), I have to admit that this slipped my notice in the last days but now that I do, I believe renaming model.resourceLike to model.resource was a bad idea. There’s even no deprecation for this class so all the customizations will suddenly break (this is how I noticed) for people using this class for e.g. hooking in other stuff … Just wanted to be the first to complain ;) Best Peter

5 5

Stylesheet BIBL ptrs mess up test?
by Syd Bauman 13 Feb '20

13 Feb '20

I don't get this. I just tried a local `make test` in Stylesheets (setting the DEFAULTSOURCE to my local 'dev' copy of p5subst), and it failed because of an expected results error. But I personally copied over the expected results file in question yesterday or the day before. The diff failure is: result: ! defined in <ref target="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/BIB.html#XSLT2">6.2. </ref>.</p> exptected result: ! defined in <ptr target="#XSLT2"/>.</p> and 1/2 dozen others exactly like that. I.e., w/ full URI instead of just bare name identifier. What gives? Has anyone changed anything that should have anything to do with this? Is it something on my local system? (That's a rhetorical question.) Could one of the CI maintainers kick off the Stylesheets-dev-against-TEIP5-dev job?

4 12

Freeze! Don't push to the dev branch of TEI or Stylesheets
by Elisa Beshero-Bondar 13 Feb '20

13 Feb '20

Dear Council: I'm at last creating the release branches for 3.7.0, so please don't push to dev for a moment until I send the "all clear"! Elisa -- Elisa Beshero-Bondar, PhD Associate Professor of English University of Pittsburgh at Greensburg Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu

4 6

test issue #1625
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Feb '20

11 Feb '20

Hi all, does anyone have time to test this issue? https://github.com/TEIC/TEI/issues/1625. It would be great if we could close this issue. Thanks! Best, Martina

2 1

Documentation
by Hugh Cayless 11 Feb '20

11 Feb '20

Hi All, I've been looking at implementing a slightly more robust documentation-publishing scheme for things like TCWs using Travis to automatically publish stuff pushed to the Documentation repo on GitHub Pages (and maybe in future to the website as well). We moved the TCW (Technical Council Working papers) docs over to https://github.com/TEIC/Documentation, but there is also https://github.com/TEIC/TEI/tree/dev/Documents, and in fact some of the content at http://teic.github.io/TCW/ and https://github.com/TEIC/teic.github.io/tree/master/TCW comes from the latter. So not everything in the TCW directory is a TCW, nor is everything listed in our GitHub Pages TCW site from the TCW directory. In short, it's a shambles :-). I would like to organize all this in a more sensible and intuitive way. So I have questions: 1) What documents should we surface? There's a lot of stuff in the TEI/Documents folder that's old (obsolete? Of historical interest?). 2) Should we try to merge all the documentation? We moved the TCWs out of TEI for reasons that may no longer pertain. Or we could move all the stuff in TEI/Documents out into the Documentation repo. What do we think? Hugh

1 1

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

11 Feb '20

Dear all, our call starts in 15 minutes. Agenda: https://docs.google.com/document/d/1hlKcKJJqW-LV0_-Q3rZQJqBxXySk_fA8qEJWlAu… To join the video meeting, click this link: https://meet.google.com/qti-toyw-hek Best, Martina

1 0

no longer using sydb-standOff
by Syd Bauman 11 Feb '20

11 Feb '20

Jenkins and Travis maintainers -- You can remove the syd-standOff branch jobs from the CI servers at your leisure.

2 1

Nicholas -- where are you?
by Syd Bauman 10 Feb '20

10 Feb '20

Checking in, Nicholas -- is everything OK? Haven't heard from you in some time. If all is OK, please hurry up and accept the invitation to join the TEIC GitHub group. And get in touch so we can arrange orientation conversations.

3 4

release branch - tomorrow?
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Feb '20

10 Feb '20

Hi Elisa and Raff, I was just talking to Syd and we found some (small) issues in standOff and unihan that he will look into later today. Could you please wait with building the release branch until after our call tomorrow morning/afternoon? Best, Martina

2 1

release notes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Feb '20

10 Feb '20

Dear Council, Please have a look at the release notes and feel free to add and modify. Please pay special attention to the standOff and uniHan issue. https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… Best, Martina

1 0

standoff
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Feb '20

08 Feb '20

Hi Syd, I am currently working on the release notes and found some things in standoff: 1. <standOff> is defined in the textstructure module but the fourth bullet point in textstructure says that it is defined in the linking module and refers to section 16.9.2 The standoff Container, see https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… 1. In the <standOff> spec * The description of an element in <desc> usually starts with a lower-case letter (functions as a container ...) * There should be a reference to the GLs in the element description, eg. to SA.html#SASOstdf Best, Martina

1 0

Refridge
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Feb '20

06 Feb '20

Dear Council, We are in the middle of the “refridge phase” which means that we are getting really busy 😊 Please don’t commit major changes to the schema (except if they have been tested in a branch like standoff and unihan); minor changes (wording, typos, examples) are fine. Freeze is on Monday, which means no more changes can be done in the dev branch after that. There are 35 open issues labeled with “milestone 3.7.0” https://github.com/TEIC/TEI/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Gu… Please remove the milestone from those issues, that won’t go into the upcoming release. Best, Martina

2 2

change in date of next Stylesheets meeting
by Syd Bauman 04 Feb '20

04 Feb '20

100% of the people at today's Stylehseets meeting cannot make the next scheduled date, Tue 03 Mar 20. Thus we would like to move it to Tue 17 Mar 20 (St. Patrick's Day). I have already changed it on the Google Calendar. (Didn't know I had that power! :-) But if there are objections ...

1 0

Stylesheets meeting?
by Raffaele Viglianti 04 Feb '20

04 Feb '20

Hi all, I see on the calendar that there's a stylesheets meeting tomorrow (Tues) at 9am EST, but haven't heard any concrete plans yet. Is it happening? Raff

4 4

time to merge in <standOff>, eh?
by Syd Bauman 03 Feb '20

03 Feb '20

With great thanks to Peter, Martin, and Martina the changes have been reviewed. I've addressed almost all the issues mentioned (still hoping someone can come up with better wording than "makes explicit the multiplicity of the collection"). Mr. Jenkins is happy with the sydb-standOff branch, and it builds fine locally on my machine here. (Not perfectly, but no worse than the dev branch.)-: So I think perhaps it is time to wrap in the sydb-standOff branch into dev, yes? Any objections?

3 2

F2F meeting location
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Feb '20

03 Feb '20

Dear all, We have three magnificent options for our F2F meeting and need to make a decision. Peter offered to host us in Paderborn, Nicolas in Oxford, and Magdalena in Warsaw. Thanks to all of you for your willingness to host us! Please fill in the (anonymous) doodle poll by Monday, Feb 3: https://doodle.com/poll/vpncpziivf4fcfn6 Best, Martina

1 1

Internationalization working group proposal
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Feb '20

03 Feb '20

Dear all, as discussed in our last call, we (the group who met at the Scholarly Communication Institute in Chapel Hill to discuss "TEI and internationalization") want to establish a working group on "Internationalization (I18n)". Please find our proposal in this google doc: https://docs.google.com/document/d/1EyAWLkKF5oBeueSoNaES3NGeA2f_AGLtn8Kx9hb… It would be great if we could get a "go ahead" from the Council members this week. In case of your approval, is there any other formality that we have to observe or could we consider it as an official charge then? Best, Martina

1 0

upcoming Stylesheets meeting
by Syd Bauman 03 Feb '20

03 Feb '20

We are planning to meet this coming Tue 04 Feb 14:00Z.[1] I am betting we will use the same Google Hangouts we have been for awhile,[2] but Martina will tell us. (Right, Martina?) Agenda ------ * anything required for release? * next meeting * ticket 403 * tickets 266 & 267 * ticket 370 Notes ----- [1] That's 06:00 PST 09:00 EST 14:00 GMT 15:00 CET Am I missing anyone's time zone? [2] https://hangouts.google.com/group/MCM1LEBUz2Kj9osA9

1 0

checking out <standOff>
by Syd Bauman 02 Feb '20

02 Feb '20

Stuff that's been done: * changed model.resourceLike to model.resource, and removed <TEI> from it * added new model.describedResource, which contains only <TEI> and <teiCorpus> * changed content models of <TEI> and <teiHeader> as discussed * created new <standOff> and model.standOffPart (to SA) * tweaked various bits of prose, e.g. the <remarks> for <settingDesc>, to talk about new <standOff> * updated the beginning of DS * changed prose and an example or two in CC where it talks about major structures for corpora to allow for nested <TEI> * tweaked prose in FS where free-standing <fsdDecl> is mentioned * tweaked prose in MS where <person> is discussed * changed an example in CO to show <standOff> * added a paragraph to DR about using <standOff> for a <castList> * changed prose and an example or two in ND to accommodate <standOff> * tweaked prose in PH to mention that <listTranspose> could be in <standOff> * tweaked beginning of SA, and added an entire new subsection later on, to discuss <standOff> - NOTE: left a stub "Placement of Stand-off Markup and Contextual Information" section that I haven't figured out if it should be kept or deleted, pr new subsection should be moved into it, or what * tweaked TS to remove implication that <listPerson> must be in <particDesc> (although for typical transcriptions of speech it may well be) What I think should be done next is each member of Council should pick one changed chapter and do a quick comparison of it between branch sydb-standOff and dev, reading the changed portions to see if they're OK.[1] In addition, a few people should read the <standOff> tagdoc and play with the schemas. So here is a checklist: https://docs.google.com/document/d/17S_W5vHzJZ_vCQw-Ze6SbOebqfz5KHq0xR9wauB… Please sign up for at least 1 chapter. Note that each chapter or tagdoc name is a link to the sydb-standOff version thereof. It would be good if all the reviews could be done by early Fri morning 24 Jan my time (EST). Notes ----- [1] For me the easiest way to do this is to put the dev and sydb-standOff versions of the HTML in two tabs in one window and pop back and forth between them. But to each his or her own. (But do note that there have been whitespace changes to some of the source files, so GitHub's compare functionality may not be ideal.)

3 3

Nicholas in GitHub?
by Raffaele Viglianti 30 Jan '20

30 Jan '20

Hi Nicholas, Could you let us know your GitHub account so we can add you to the TEI Council group and start assigning you tickets? :) Thanks! Raff

2 3

Taking stock, going into refrigeration pre-release?
by Elisa Beshero-Bondar 29 Jan '20

29 Jan '20

Hi all-- Just checking in with everyone as we're heading into refrigeration. I know we have some tickets in a molten or even "on fire" state just now, and wondering if we need to revisit our refrigeration and release dates? 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

1 0

git merging into fork
by Syd Bauman 28 Jan '20

28 Jan '20

So, I wanna do at least a little due diligence on Unihan. @duncdrum has forked TEI, and issued a PR of his "unihan-phase2" branch into the main TEI 'dev' branch. I'd like to create a (local) test copy of the TEI repo that has both the 31 new commits to TEI:dev since @duncdrum last merged, and the PR. I do *not* want this to signal accepting the PR into our branch. Seems to me there are two approaches, neither of which I know how to do off the top of my head: 1) from my local copy of duncdrum:TEI:unihan-phase2 somehow merge in TEIC:TEI:dev 2) from my local copy of TEIC:TEI:dev somehow merge in duncdrum:TEI:unihan-phase2 I don't care which I do, so long as there is no affect to the GitHub versions of this stuff. Any suggestions?

2 1

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

27 Jan '20

Dear all, This is the hangouts link for our uniHan call today: https://hangouts.google.com/call/vp1RDBzAabItP-WtiZHfAEEI (10:00-11:15 PST, 13:00-14:15 EST, 19:00-20:15 CET) Best, Martina

2 2

unihan meeting on Monday
by Scholger, Martina (martina.scholger＠uni-graz.at) 27 Jan '20

27 Jan '20

Dear all, Our uniHan-meeting is on Monday, Jan 27 from 10:00-11:15 PST, 13:00-14:15 EST, 19:00-20:15 CET (Syd will join us 15 min later, Raff needs to run to another meeting at 2pm). Please have a look at the original uniHan issue https://github.com/TEIC/TEI/issues/1805 and the pull request from Duncan https://github.com/TEIC/TEI/pull/1901 FYI, here are the minutes from the calls last year: https://docs.google.com/document/d/1XfhG5VBwYsMulp1T-BF3sDES6dtr04_Q9MuJCO3… https://docs.google.com/document/d/1JsEaZU1H7EJMwXJmNgRLjOZoJOg6AHzMcDM41zb… Best, Martina

2 1

Stylesheets tutorial -- doodle
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Jan '20

23 Jan '20

Dear all, In our last Stylesheets meeting we agreed to organize a Stylesheets tutorial meeting in the week February 17 to 21 for our new members and all who are interested to get started with editing the Stylesheets (e.g. where to find the files; dependencies; tests etc.). Please fill in the doodle: https://doodle.com/poll/w85u435vbcm5rfhc Best, Martina

1 0

fixing expected results
by Syd Bauman 22 Jan '20

22 Jan '20

Martin and Peter (and Martina and Jessica) -- When I run a `make test` in my local Stylesheets/ to find the diff errors, which version of TEI Guidelines should I be working against? (I.e., which one does Mr. Jenkins use? I can't duplicate the error whether I use my copy of dev or Vault/P5/current/xml/tei/odd/p5subset.xml.)

3 3

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 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

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) 10 Dec '19

10 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

Spring F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Dec '19

10 Dec '19

Dear all, yet again we have a number of great locations to choose from for our next spring F2F meeting. To get an idea about our preferences I ask you to fill in the doodle before our call tomorrow: https://doodle.com/poll/xaf3f4exhy6geyqf Best, Martina

4 3

oxygen-tei framework fix
by Martin Holmes 05 Dec '19

05 Dec '19

Hi all, Those of you on the Stylesheets call on Tuesday will remember that we discovered in the course of it that Syd's TEI for TEI Customizations template/ODD was available in the TEI P5 framework in Oxygen but not in the TEI ODD framework. I raised a ticket for that at the time, and I just figured it out and fixed it: <https://github.com/TEIC/oxygen-tei/issues/39> I put an explanation of the problem on the ticket, because we're sure to stumble over this again. If you're using the bleeding-edge version of the plugin, you should now be able to update and see Syd's thing in the TEI ODD framework options. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

2 1

Re: [Tei-council] release dates, some findings
by James Cummings 05 Dec '19

05 Dec '19

No objections to that. For the record some of these may have been instances where we had done a full release, realised that there was some corrigible error (in the build/release process), and then manually or otherwise did a re-release without changing the actual date of release. That is, we did the release, announced it, noticed an important error (like the non-English pages having not generated properly) and then silently fixed it without mentioning it publicly. ;-) There were also instances where stumbling blocks in the release meant that it went over midnight in the timezone where the build was happening. Not saying we shouldn't update the webpages to match the XML reality, just explaining. (Now off strike, but working to contract.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Peter Stadler <stadler(a)edirom.de> Sent: 29 November 2019 06:39 To: TEI Council <tei-council(a)lists.tei-c.org> Subject: [Tei-council] release dates, some findings for the record: While working through the Guidelines releases for the Zenodo ingest I discovered and fixed some inconsistencies regarding release dates at [1]. A few dates differed from what is mentioned in the respective release notes, so I fixed it to match the release notes. Lastly, one release note has the wrong date [2] which I already fixed in the xml [3]. I propose to adjust the date in the html version in the vault, as well, which I’ll do as soon as I get access to the vault. Best Peter [1] https://tei-c.org/guidelines/P5/ (table: „Version Date of Release (& Release Notes)“) [2] https://tei-c.org/Vault/P5/current/doc/tei-p5-doc/readme-3.2.0.html [3] https://github.com/TEIC/TEI/commit/9150346745c0057d74a20d0a36bcbbb09260d865

2 1

missing council reports
by Lou Burnard 04 Dec '19

04 Dec '19

To be exact: reports for the following years are missing: 2003, 2004, 2005, 2006, 2007, 2014 I have the first three.

1 0

vault.tei-c.org
by Peter Stadler 04 Dec '19

04 Dec '19

Dear all (Council and infrastructure group), here’s yet another update on the move to humanum: In our strive to separate out concerns and services we added another subdomain vault.tei-c.org where you can find – drumroll!" – the Vault. The data stems from a mounted volume which also feeds the ’traditional’ host at https://tei-c.org/Vault/. So, at present this is purely an additional service for us to test and sort things out. The vault.tei-c.org is run by an nginx docker container and the service description can be found in the infrastructure repo [1]. I already added CORS and some mime types for XML files – if anything is missing, drop me a line! Looking at the vault I found that the last three releases of the Stylesheets were missing at [2]. I just added them (as you can see from the timestamp) and updated the symlinks to „current“ and „current-old“. Second, I fixed the release date for 3.2.0 in the respective readme files (as I promised in my last mail). Looking at the P5 releases in the vault [3] I see „current-broken“, "current.03.04.2019“, and „X.X.X“. Is this in use by anyone? I suspect these are just leftovers from the migration which I’d like to delete. And there’s is a hidden „.svn“ folder which looks like it could be deleted as well. If no-one objects, I’ll do so. Best Peter [1] https://github.com/TEIC/infrastructure/tree/master/humanum [2] https://tei-c.org/Vault/Stylesheets/ or https://vault.tei-c.org/Stylesheets/ [3] https://vault.tei-c.org/P5/

3 6

Stylesheets meeting tomorrow, Tue 03 Dec 14:00Z
by Syd Bauman 03 Dec '19

03 Dec '19

Sorry I'm late on this. (I try to post these 24 to 72 hours in advance.) We have a Stylesheets Group meeting scheduled for this coming Tue 2019-12-03 14:00Z. timing ------ It will be: * 06:00 PST (Victoria) * 09:00 EST (New York) * 14:00 GMT (London) * 15:00 CET (Berlin) place ----- I am expecting we will use Google Hangouts. (I *think* I have my Google Hangouts life working. :-) topics ------ Main topics are the carry-over from last month: 1) Ticket 393.[1] 2) Ticket 399.[2] Martin has posted where he thinks the problem is on the ticket. If he's right (and I have no reason to believe he isn't), I'm not sure I like his proposed solution. So this may require some discussion. notes ----- [1] https://github.com/TEIC/Stylesheets/issues/393 [2] https://github.com/TEIC/Stylesheets/issues/399

5 5

Re: [Tei-council] Stylesheets meeting tomorrow, Tue 03 Dec 14:00Z
by James Cummings 02 Dec '19

02 Dec '19

I might be late to this. (I'm not counting TEI things as 'work' for the purposes of the UCU strike in HE here in the UK -- protesting the ongoing theft if our pensions, precarious contacts, absolutely gender pay gap. However I'll have to commute back home from the picket line rather than go to my office.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Sent: Monday, December 2, 2019 4:30:13 PM To: Bauman, Syd <s.bauman(a)northeastern.edu> Cc: TEI Council <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] Stylesheets meeting tomorrow, Tue 03 Dec 14:00Z Hi all, Unfortunately I will have to miss this again. My dept scheduled an all-hands meeting for tomorrow at 10am. Raff On Mon, Dec 2, 2019 at 11:28 AM Syd Bauman <s.bauman(a)northeastern.edu<mailto:s.bauman@northeastern.edu>> wrote: Sorry I'm late on this. (I try to post these 24 to 72 hours in advance.) We have a Stylesheets Group meeting scheduled for this coming Tue 2019-12-03 14:00Z. timing ------ It will be: * 06:00 PST (Victoria) * 09:00 EST (New York) * 14:00 GMT (London) * 15:00 CET (Berlin) place ----- I am expecting we will use Google Hangouts. (I *think* I have my Google Hangouts life working. :-) topics ------ Main topics are the carry-over from last month: 1) Ticket 393.[1] 2) Ticket 399.[2] Martin has posted where he thinks the problem is on the ticket. If he's right (and I have no reason to believe he isn't), I'm not sure I like his proposed solution. So this may require some discussion. notes ----- [1] https://github.com/TEIC/Stylesheets/issues/393 [2] https://github.com/TEIC/Stylesheets/issues/399 _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

release dates, some findings
by Peter Stadler 29 Nov '19

29 Nov '19

for the record: While working through the Guidelines releases for the Zenodo ingest I discovered and fixed some inconsistencies regarding release dates at [1]. A few dates differed from what is mentioned in the respective release notes, so I fixed it to match the release notes. Lastly, one release note has the wrong date [2] which I already fixed in the xml [3]. I propose to adjust the date in the html version in the vault, as well, which I’ll do as soon as I get access to the vault. Best Peter [1] https://tei-c.org/guidelines/P5/ <https://tei-c.org/guidelines/P5/> (table: „Version Date of Release (& Release Notes)“) [2] https://tei-c.org/Vault/P5/current/doc/tei-p5-doc/readme-3.2.0.html [3] https://github.com/TEIC/TEI/commit/9150346745c0057d74a20d0a36bcbbb09260d865

1 0

bad link; contact on footer; contact info
by Syd Bauman 22 Nov '19

22 Nov '19

1. On page https://tei-c.org/guidelines/p5/, section "Get and install a local copy": a) The link "can be downloaded from GitHub" should be to https://github.com/TEIC/TEI/releases/latest, no? (It is currently to just https://github.com/TEIC, which seems at least lame, if not rude.) b) The "instructions" link (to https://tei-c.org/guidelines/p5/get.xml) cannot be found; brings you to nice "Oops! That page can’t be found." page. c) The "http://www.tei-c.org/release/" link (to https://tei-c.org/release/) cannot be found, whether you follow the link or the link text; in both cases brings you to an ugly 404 page. 2. On that same page, and I suspect most every other WP-generated page on the site, the footer has 3 links (Twitter button, Code of Conduct, Contact/Feedback) and the string "membership campaign". a) There should be more whitespace separating "Code of Conduct" from the Twitter button on its R and the link on its L. b) On "Contact/Feedback": I personally am not fond of using a solidus where a simple conjunction or disjunction (i.e. "and" or "or") would do. c) But note that the page linked to by "Contact/Feedback" (https://tei-c.org/about/contact/) does not mention the word "feedback". (Except in the footer where it links to itself.) d) The words "membership campaign" are not a link. Looks like it's supposed to be some sort of Javascript button, but it does not do anything for me (in either Firefox or Chromium). 3. On that contact page (https://tei-c.org/about/contact/) our postal address a) has no line breaks, and b) still gives John Unsworth's address -- is that correct?

1 0

Re: [Tei-council] Next F2F meeting
by James Cummings 21 Nov '19

21 Nov '19

Hi Martina and Council, I'd be happy to have you here in Newcastle, though presumably there would be a council meeting here shortly before the TEI2021 conference and while we have repeated venues before (notably in Oxford for financial savings when Lou, Sebastian, and I were all there), you should bear that in mind when deciding. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: Thursday, November 21, 2019 9:48:30 AM To: nicholas.cole(a)history.ox.ac.uk <nicholas.cole(a)history.ox.ac.uk>; Magdalena Turska <magdalena(a)existsolutions.com>; Vanessa Juloux <vanessajuloux(a)gmail.com>; James Cummings <James.Cummings(a)newcastle.ac.uk> Subject: Next F2F meeting Dear all, In our last call on Tuesday we were talking about where and when to do our next spring F2F meeting. Please have a look at the minutes and comment on our options or send me an email. @Magda and @James: we added Warsaw and Newcastle with a question mark – after that was on last year’s list, but no pressure. Please find the minutes here: https://docs.google.com/document/d/10MiLHVis5aecLue8OsthiA-LMfyaP_7QbPnG6M9… Best, Martina

1 0

Re: [Tei-council] Hands on session: Local Build Processes
by James Cummings 21 Nov '19

21 Nov '19

Oh I didn't look at the time! I might be able to pop into that after I've commuted home. Silly me! Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of James Cummings <James.Cummings(a)newcastle.ac.uk> Sent: Thursday, November 21, 2019 9:13:53 AM To: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at>; tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] Hands on session: Local Build Processes I would be there to help but will be teaching an intensive 1-day XSLT workshop that day. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: Thursday, November 21, 2019 9:04:20 AM To: tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: [Tei-council] Hands on session: Local Build Processes Dear all, our hands on orientation session for TEI Local Build Processes will be on Wednesday, December 18. 19:00Z–21:00Z (i.e., 11:00–13:00 PST, 14:00–16:00 EST, 19:00–21:00 GMT, 20:00–22:00 CET). Best, Martina

1 0

Re: [Tei-council] Hands on session: Local Build Processes
by James Cummings 21 Nov '19

21 Nov '19

I would be there to help but will be teaching an intensive 1-day XSLT workshop that day. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: Thursday, November 21, 2019 9:04:20 AM To: tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: [Tei-council] Hands on session: Local Build Processes Dear all, our hands on orientation session for TEI Local Build Processes will be on Wednesday, December 18. 19:00Z–21:00Z (i.e., 11:00–13:00 PST, 14:00–16:00 EST, 19:00–21:00 GMT, 20:00–22:00 CET). Best, Martina

1 0

Hands on session: Local Build Processes
by Scholger, Martina (martina.scholger＠uni-graz.at) 21 Nov '19

21 Nov '19

Dear all, our hands on orientation session for TEI Local Build Processes will be on Wednesday, December 18. 19:00Z-21:00Z (i.e., 11:00-13:00 PST, 14:00-16:00 EST, 19:00-21:00 GMT, 20:00-22:00 CET). Best, Martina

1 0

nominations for Council chair
by Syd Bauman 20 Nov '19

20 Nov '19

We will elect the 2020 Council Chair at our Dec meeting.[1] At our Nov meeting yesterday only 1 person (MS, incumbent) was nominated to run for Council Chair. If anyone would like to submit a nomination for Chair, including self nominations, please do so by Tue 03 Dec. (Send e-mail to this list or to MS.) New members-to-be (MB, NC, JL): * Reminder -- the archives of this list are public. * You cannot actually submit a nomination or vote. But if there is someone you think should be nominated say so, and almost assuredly someone else will nominate her or him for you. BTW, we have never discussed this, but as far as I'm concerned someone whose term starts in Jan *is* eligible to run for Chair, even if not eligible to vote. (Someone whose term ends in Dec is not currently eligible to run, but is eligible to vote.[2]) It is probably a very bad idea for someone who has never served on Council to be its Chair, but it is allowed. And, e.g., if James Cummings is elected to Council again some years from now, this allows Council to decide he should step right back into the Chair's seat. Notes ----- [1] Which meeting I think will be Tue 10 Dec 14:00Z (06:00 PST, 09:00 EST, 14:00 GMT, 15:00 CEST -- do we have any other time zones represented?). If I'm wrong on that, please let me know or I will miss it. [2] Note that if no one who will be on Council in 2020 were willing to run, the Bylaws III.3 have an alternate mechanism that allows nomination of non-Councilors. But since MS is willing to run, this does not come into play.

1 0

Next meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Nov '19

19 Nov '19

Dear all, This is a reminder for our next Council call tomorrow, November 19 at EST 9:00-10:30, GMT 14:00-15:30, CET 15:00-16:30. Please add topics that you want to discuss to the agenda: https://docs.google.com/document/d/10MiLHVis5aecLue8OsthiA-LMfyaP_7QbPnG6M9… Elli will start the call and add the hangouts meet link to the Google Doc just before we start. Best, Martina

3 2

Reminder: Intro to Local Build Processes: Special Council Hangout
by Elisa Beshero-Bondar 18 Nov '19

18 Nov '19

Greetings, Council (cc :Martin) Want to help me set the date for this special Council hangout? (see below). Only six of us responded to the poll, and while of course we don't all need to be there, I'd hoped we might get a few more of us together for this. Here's a link to the scheduling poll: https://doodle.com/poll/savvhuaszhqg4tw6 If more of you respond before our Council meeting on Tuesday perhaps we can finalize the date and the hour then. Thanks! Elisa ********************************************** Dear TEI Council colleagues, During today's Stylesheets meeting, those Council members present (me, Martina, Hugh, Syd, and James) agreed that we'd like to organize a special meeting for Council members (new and current) to learn how to run build processes locally for both the TEI Guidelines and the TEI Stylesheets, and also to learn how these processes mutually depend on each other. I agreed to get us started to organize it. For this meeting to work, we'll need the people who are experienced and comfortable with local builds to be present (and also to coordinate a bit in advance to help organize how we proceed)--we're looking at Hugh, Peter, Raff, and Martin. :-) We'll prepare a Google Doc for shared writing to improve and update our documentation on local build processes. We're not thinking anyone should have to do this with Jenkins running locally--but we should probably talk about if/when that's a good idea. And we're really wanting this to be a hands-on practice and documentation session of Guidance that Every Council Member can Access to do local builds when needed. When? A fine day in December for about two hours: We thought December would be an appropriate month for this for reasons of it being a time of transition as new members are joining us and in the process of learning more about how the TEI works, and also because it's a moment when for those of us on teaching semesters, we can find a little more time to spend with reconfiguring things on our computers to get things working properly. We also don't want to impose too much on people's holiday time. For right now, we thought we'd start with a fairly narrow window of days, December 18, 19, and 20, and I've opened up a wide range of possible two-hour blocks. Would you respond to the Doodle Poll we've set up to arrange this special meeting? https://doodle.com/poll/savvhuaszhqg4tw6 For the new Council members joining us: Those of us mentoring you will probably want to do an orientation session or two a little ahead of this meeting to help prepare you. Let's start talking about that soon. :-) Thanks, everyone! -- Elisa Beshero-Bondar, PhD Associate Professor of English University of Pittsburgh at Greensburg Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu

3 2