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

housekeeping: delete stale branches
by Peter Stadler 10 Jun '20

10 Jun '20

Dear all, here’s yet another(?) proposal for housekeeping: Both Stylesheets and Guidelines repo feature various stale branches which I would like to get rid off [1,2]. Some of those are prefixed with a Councilists name so I encourage everyone to look through his/her branches and eventually delete outdated/unused/forgotten branches. Some of the stale branches are even just behind dev without featuring any commits *ahead* of dev (e.g. the TEI/help branch). I think those can safely be removed and would do so in the next days if no one objects. This does include release branches which I’d also like to get rid of because IMHO they do not serve any purpose anymore (the important information is kept in the tags). Best Peter [1] https://github.com/TEIC/Stylesheets/branches/stale [2] https://github.com/TEIC/TEI/branches/stale [3] https://github.com/TEIC/TEI/tree/help

3 3

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

09 Jun '20

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

1 0

Reminder: Council meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '20

08 Jun '20

Dear all, This is a reminder that our next Council meeting is tomorrow, June 9 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30 Please find the agenda here and add topics that we should discuss https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w…<https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w…> You can find the zoom link for the meeting in the google doc. Best, Martina

1 0

Next Council meeting: Tuesday, June 9
by Scholger, Martina (martina.scholger＠uni-graz.at) 05 Jun '20

05 Jun '20

Dear all, Our next Council meeting is on Tuesday, June 9 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30 Please find the agenda here and add topics that we should discuss https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w… You can find the zoom link for the meeting in the google doc. Best, Martina

1 0

P5/Utilities-1 and P5/Utilities
by Peter Stadler 03 Jun '20

03 Jun '20

Dear all, while working on some old TEI->LaTeX->PDF issues I stumbled (once again) across those two folders P5/Utilities-1 and P5/Utilities in the Guidelines repo. Can somebody shed some light on the difference of these folders? I’m especially interested in the file guidelines-latex.xsl which exists in both directories but only the one in Utilities seems to be used for building the PDF version of the Guidelines? Many thanks Peter

2 2

Noto fonts
by Peter Stadler 03 Jun '20

03 Jun '20

Hi Martin, I'm about to push some changes to the TEI repo that will set the Google Noto fonts as default for the PDF Guidelines (processed via LaTeX). That requires the fonts-noto-cjk package (on Debian) in the respective build environment. It is already included in our Jenkins Docker image but you might need to add that manually to your Jenkins? Just wanted to give you a warning (shortly) ahead of time ;) Best Peter

2 1

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