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

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