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

time to announce new release
by Bauman, Syd 12 Apr '21

12 Apr '21

Martina — Nick and I have finished the GitHub and SourceForge releases of 4.2.2 and 7.51.2. (Nick is still working on the Debian packages; Martin & Peter will do oXygen next week.) So it is time for step 22, which I think is up to you or Hugh, right? Update the list of previous releases of P5, which is found at https://tei-c.org/guidelines/p5/#section-2.If you have editing privileges on the TEI WordPress on tei-c.org, add the new release to the top of the release table. If not, ask one of the other Council members who does (currently Martina Scholger and Hugh Cayless) to make the change.

4 6

on ticket 2049 step 2
by Bauman, Syd 12 Apr '21

12 Apr '21

With 8 people (7 from Council) voting, there are only 2 places left that need discussion on the question of whether <altIdent> should be an allowable child. 1. <language>, which is not in the tagdocs module and does not currently have an <altIdent> child. It does have its own @ident. 2. <paramSpec>, which is in the tagsdocs module and does currently have an <altIdent> child. It gets @ident via the att.identifiable class. Please let’s discuss these two on the ticket<https://github.com/TEIC/TEI/issues/2049>, where I have posted a summary<https://github.com/TEIC/TEI/issues/2049#issuecomment-817394059> of step (2) decisions so far. I hope to post my own opinions later tonight, but need a break first, so I may not get to it.

1 0

The Never-ending 4.2 release!
by Nicholas Cole 11 Apr '21

11 Apr '21

Dear Council, Still with my release-manager hat on (!), Syd and Helena have noticed that a folder has been missing from recent releases of TEI. This is going to need another point release to fix. Fortunately, term doesn’t start again here for another two weeks, so I’ve actually got plenty of time to work on this in the coming days. Would some time on Monday or Wednesday suit people, for example? Syd, if you have time, perhaps we could hack away at a fix on Monday and then do the .3 release on Wednesday? We should probably also write a test to catch this kind of thing... Best wishes, Nicholas

7 13

Fwd: AW: link rot
by Lou Burnard 11 Apr '21

11 Apr '21

Actually, on further investigation, it seems that all I need to change is the explicit reference to "index.xml" http://www.tei-c.org/Guidelines/P5/#previous works just as it used to. -------- Forwarded Message -------- Subject: Re: AW: [Tei-council] link rot Date: Sun, 11 Apr 2021 12:28:42 +0100 From: Lou Burnard <lou.burnard(a)retired.ox.ac.uk> To: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Dear Martina Thanks for the quick response. I will tweak my tuto accordingly. It seems a shame that the ability to link to a specific part of this (rather long) page has been removed, but I guess thems the breaks. best Lou On 11/04/2021 12:21, Scholger, Martina (martina.scholger(a)uni-graz.at) wrote: > Dear Lou, > > this is the link to the table: https://tei-c.org/guidelines/p5/ > > Best, > Martina > > -----Ursprüngliche Nachricht----- > Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von > Lou Burnard > Gesendet: Sonntag, 11. April 2021 13:19 > An: tei-council(a)lists.tei-c.org > Betreff: [Tei-council] link rot > > There used to be a useful table listing the dates and version numbers > of all TEI P5 releases at > http://www.tei-c.org/Guidelines/P5/index.xml#previous > <http://www.tei-c.org/Guidelines/P5/index.xml#previous> > > But now it seems to have disappeared. Could you either put it back or > tell me where it's gone?My ODD chaining tutorial is broken without it. > > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

link rot
by Lou Burnard 11 Apr '21

11 Apr '21

There used to be a useful table listing the dates and version numbers of all TEI P5 releases at http://www.tei-c.org/Guidelines/P5/index.xml#previous <http://www.tei-c.org/Guidelines/P5/index.xml#previous> But now it seems to have disappeared. Could you either put it back or tell me where it's gone?My ODD chaining tutorial is broken without it.

2 1

Today's release preparations
by Martin Holmes 09 Apr '21

09 Apr '21

Hi all, Today Janelle, Martina, Nick, Syd and I in various combinations got this far with the new release: - Created new point-release branches for the TEI and Stylesheets repos. - Cherry-picked the fix commit into the P5 branch. - Added new release notes for this P5 release, and updated the two VERSION files. - Built the P5 branch in various places and confirmed it was good. - Took the p5subset from that branch and put it into the Stylesheets point-release branch. - Built the stylesheets and fixed all the many issues in tests resulting from the new p5subset. - Merged both these branches into the respective -released branches. Those branches are now building on the Jenkinses, eg: <https://jenkins.tei-c.org/view/TEI%20stable/> and when all those builds are complete, we'll have products we can use to create the release itself. The plan is for some of us to reconvene tomorrow if possible (Nick, Syd says he's available to help if you can arrange times). Anyone is of course welcome to ride along with the rest of the release process to learn how it works. I believe we will be starting from point 13, "Log into TEI server and run the tei-install.sh script", on TCW22: <https://teic.github.io/TCW/tcw22.html> Some time next week, once the release is done, Hugh and I should get together with anyone else who wants to learn the process and do the Oxygen plugin release, updating point 23 in TCW22 as we go. Anything I've missed? Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

Call today
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Apr '21

08 Apr '21

Dear all, This is the agenda for our meeting today (11am PDT / 2pm EDT / 7pm BST/ 8pm CEST) https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… and the zoom link https://us02web.zoom.us/j/82014974946?pwd=OVZXbTNkU1kyWGhEOUR3VWh0WUF3dz09 Best, Martina Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Dienstag, 6. April 2021 16:25 An: tei-council(a)lists.tei-c.org Betreff: Next meeting: April 8 Dear all, This is the agenda for our next Council meeting on Thursday, April 8 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… Please add discussion topics to the agenda. I think we should discuss the point release issue at this meeting. Best, Martina

1 0

Fairly urgent bug in recent releases
by Martin Holmes 06 Apr '21

06 Apr '21

Hi all, Janelle and I came across a bad problem with releases starting at 4.0.0, which means that valLists for the @type attribute in 21 elements are missing from both the Guidelines pages and the schemas. There's a bug here: https://github.com/TEIC/TEI/issues/2128 and a PR with a full fix here: https://github.com/TEIC/TEI/pull/2129 Both Syd and I think this is bad enough to warrant an interim release. Could anyone with a free moment take a look at the bug and the PR, and review or comment? Also, could you weigh in on whether you agree that it deserves a quick release? Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

6 8

Next meeting: April 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Apr '21

06 Apr '21

Dear all, This is the agenda for our next Council meeting on Thursday, April 8 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… Please add discussion topics to the agenda. I think we should discuss the point release issue at this meeting. Best, Martina

1 0

Council meetings missing from google calendar
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Apr '21

01 Apr '21

Dear all, Jessica brought to my attention that the dates for the regular Council meetings are missing in our shared google calendar (even the past meetings). I don't know how this could have happened. I have added the dates again, our next meeting will be on Thursday next week, April 8. Best, Martina

1 0

Stylesheets meeting today, Thu 25 Mar
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 Mar '21

25 Mar '21

Dear all, please find the google doc for our Stylesheets meeting here: https://docs.google.com/document/d/1Qolxk9yzIAtqofcu7szuPArOuv1koy6g-bjhM1r… Meeting times: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) Zoom link: https://zoom.us/j/95354913465?pwd=ODZpVUxFVmJjWnlIZnBnaCtIVnFadz09 Best, Martina Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Bauman, Syd Gesendet: Mittwoch, 24. März 2021 04:09 An: tei-council(a)lists.tei-c.org Betreff: Re: [Tei-council] upcoming Stylesheets meeting, Thu 25 Mar Topics for discussion, in no particular order: * 2-minute update on Saxon 9 -> Saxon 10 (MH) * Did we have more to discuss or work on for PR #327<https://github.com/TEIC/Stylesheets/pull/327>? (I forget) * Close issue #272<https://github.com/TEIC/Stylesheets/issues/272> and create new ticket for @mode? * Didn't we fix #482<https://github.com/TEIC/Stylesheets/issues/482>? * Issues we have started delving into, but have not solved: * Issue #327<https://github.com/TEIC/Stylesheets/issues/237>, generating an element or attr that has the same local-name as a TEI element or attr * Issue #402<http://We%20need%20a%20volunteer%20to%20write%20a%20test%20ODD>, on @mode: we need a volunteer to write a test ODD * Issue #399<https://github.com/TEIC/Stylesheets/issues/399>, <code> being dropped from <desc> * Issues that have had a lot of work done, but still are not fixed: * Issue #444<https://github.com/TEIC/Stylesheets/issues/444>, <desc> getting dropped * Issue #102<https://github.com/TEIC/Stylesheets/issues/102>, for which we now have test output, and I finally sort of understand the problem * Issue #424<https://github.com/TEIC/Stylesheets/issues/424>,@ns causing pain ________________________________ We are scheduled to meet (on Zoom, right Martina?) this coming Thu 25 Mar 21 at 19:00Z for 1½ hours. Due to daylight saving time mis-match, this meeting time will be different for some people, most likely for this meeting only. Times are: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) I plan to post a suggested agenda 24+ hours before the meeting starts. (So if you want something on the agenda, let me know now.)

2 1

upcoming Stylesheets meeting, Thu 25 Mar
by Bauman, Syd 24 Mar '21

24 Mar '21

We are scheduled to meet (on Zoom, right Martina?) this coming Thu 25 Mar 21 at 19:00Z for 1½ hours. Due to daylight saving time mis-match, this meeting time will be different for some people, most likely for this meeting only. Times are: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) I plan to post a suggested agenda 24+ hours before the meeting starts. (So if you want something on the agenda, let me know now.)

2 2

git me this
by Bauman, Syd 23 Mar '21

23 Mar '21

I have on my local HD a copy of a fork one of our repos.[1] The interesting bit of this repo is in its dev branch. But sadly, its dev branch is somewhat behind our dev branch. So I would like to merge our dev branch in. How do I do that? I.e., how do I specify that I want the git merge command to use our repo’s dev branch (not the current repo’s dev branch, which would be silly, as I am on the current repo’s dev branch) as the upstream? Note [1] https://github.com/sanskrit-coders/Stylesheets.git to be precise, but that detail does not matter.

2 4

p5subset.xml and TCW22
by Martin Holmes 12 Mar '21

12 Mar '21

Hi all, Syd, Nick and I were looking at the Stylesheets repo this morning and we realized that the version of p5subset.xml in its source subfolder had not been updated for quite a long time. That means the Stylesheets tests were running against an old version of the Guidelines. When we decided to put p5subset.xml into the Stylesheets repo, the purpose was to avoid the circularity problem that causes an inability to build each repo against the other. That's been successful, but the corollary was that we should regularly update the p5subset.xml in the Stylesheets repo so that we caught new issues resulting from changes to the Guidelines in good time. That hasn't happened. We added an updated p5subset.xml this morning, and there were a LOT of test issues to fix, although none of them were significant. We've added two new steps to TCW22 so that at the beginning of the freeze or refrigeration period[1], an up-to-date p5subset.xml is added, meaning that almost everything will get fixed at that point; and then later, once the release-X.X.X branch of P5 is building, the p5subset.xml from that gets added into the release-X.X.X branch of the Stylesheets, so that our release is actually coordinated (the states of the two repos match), prior to the release. In the process, we also noticed that lots of the instructions about creating the release-X.X.X branch were written to apply ONLY to the TEI repo, but the same steps also have to happen for the Stylesheets repo, so we've made that more explicit. In our regular Friday meetings, the three of us are going to make a point of updating p5subset.xml so we don't get so far out of sync again. Anyone else is also free to update it any time of course. Cheers, Martin [1] TCW22 doesn't adequately distinguish these two phases; we should fix that. -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

minute assist
by Bauman, Syd 11 Mar '21

11 Mar '21

Janelle — The “minute assist” task is not about taking minutes during the meeting (in theory we all chip in on that), but rather is about helping the Chair whip the notes taken during the meeting into publishable minutes. Martina typically does this by transferring them to another GoogleDoc, making “suggestion” changes there, and then asking the minute assist person to review those changes and make any of her or his own. (Other Chairs have done it differently in the past, but that’s not important right now. :-) If that means you do not have time to do minute assist for this month, just say so. I spent much less time than expected last week on the minute assisting of the SVF2F, so would not mind doing this one.

1 0

call in 30 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Mar '21

11 Mar '21

Dear all, Our call starts in 30 minutes: https://docs.google.com/document/d/1qcs0bVOjgm0ae7x7ZRMEMvlsipZ4FXzBNJXe5Oj… Best, Martina Martina Scholger Centre for Information Modeling Austrian Centre for Digital Humanities University of Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Chair of the TEI Technical Council | http://www.tei-c.org/ Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/

3 2

Next call: Thursday, March 11
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Mar '21

09 Mar '21

Dear all, Our next TEI Council meeting is scheduled for Thursday, March 11 at 11am-12:30pm PST/2pm-3:30pm EST/7pm-8:30pm GMT/8pm-9:30pm CET. Please add discussion topics to the agenda: https://docs.google.com/document/d/1qcs0bVOjgm0ae7x7ZRMEMvlsipZ4FXzBNJXe5Oj… The zoom link is in the google doc. Best, Martina

1 0

Deb packages key signing broken?
by Martin Holmes 07 Mar '21

07 Mar '21

Hi all, My Jenkins server says: Err:9 https://packages.tei-c.org/deb/binary ./ Release.gpg The following signatures were invalid: EXPKEYSIG 19CF3E497B9824DC TEI Council (GPG key for signing Debian packages) <council(a)tei-c.org> [...] W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.tei-c.org/deb/binary ./ Release: The following signatures were invalid: EXPKEYSIG 19CF3E497B9824DC TEI Council (GPG key for signing Debian packages) <council(a)tei-c.org> W: Failed to fetch https://packages.tei-c.org/deb/binary/./Release.gpg The following signatures were invalid: EXPKEYSIG 19CF3E497B9824DC TEI Council (GPG key for signing Debian packages) <council(a)tei-c.org> Did the packages get signed correctly, or has the key expired? Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

3 3

what we’re up to
by Bauman, Syd 05 Mar '21

05 Mar '21

Martin, Nick, and I are halfway through updating the repos to use Saxon 10. We have finished the Stylesheets repo, which was probably the easier one. It has been checked in as the “saxon10” branch. We expect to do the TEI repo soon (unless someone else jumps on this interminable task). We expect to issue a PR for each repo, assigned to the same person (any volunteers?), at roughly the same time. Probably a good idea that each of the repos be merged at roughly the same time, too. (I think there shouldn’t be any circularity problem from this change, but just in case, having them both get to Mr. Jenkins in the same cycle sounds like a good defense.) I just realized there are no tickets for this, so I plan to create issues now.

1 0

Stylesheets meeting Thu 04 Mar
by Bauman, Syd 04 Mar '21

04 Mar '21

We have a Stylesheets meeting scheduled for tomorrow (likely today by the time you read this), Thu 04 Mar, 19:00Z to 20:30Z. That is * 11:00 PST * 14:00 EST * 19:00 GMT * 20:00 CET for 1½ hours. Agenda: 1. Update to 7.51.1, i.e. issue #488, PR #489 (Syd & Martin) 2. Issues surrounding yesterday’s release of TEI framework for oXygen (Hugh & Martin) 3. Detailed review of PR #327 (Peter) 4. Review of PR #462 (Syd)

3 2

TEI release directory structure
by Peter Stadler 01 Mar '21

01 Mar '21

Hi all, apologies for sending to both groups, but this issue is kind of between Council and infrastructure group, so I thought I’d be better to include both. The issue I see is about the „release“ directory structure, i.e. the stuff at https://tei-c.org/release/ Currently, on the Huma-Num server, „release“ is just a symlink pointing at "Vault/P5/current“ – this caused frequent errors with the Stylesheets release missing due to missing CSS files for building ePubs. It was hacked around by copying Stylesheets to P5 or symlinking Stylesheets into P5. Since the structure under „release“ seems to mimic the "/usr/share/doc“ and „/usr/share/xml“ structure known from Debian systems – and this is the place where the TEI Debian packages are installed by default – I think the *original* setup might have looked like an apache Webserver simply serving its local „/usr/share“ directory under „release“ to the outside. At the latest with the ADHO server crash, this setup got lost and we have a semi-functioning release directory now. IMHO, with our current infrastructure, the proper setup would be to (hard) create the directory „release/doc“ and „release/xml/tei“ and create symlinks within these directories to the respective directories in the Vault: release/doc * tei-p5-doc —> ../../Vault/P5/current/doc/tei-p5-doc * tei-p5-exemplars —> ../../Vault/P5/current/doc/tei-p5-exemplars * tei-xsl —> ../../Vault/Stylesheets/current/doc/tei-xsl release/xml/tei: * Exemplars —> ../../../Vault/P5/current/xml/tei/Exemplars * Test —> ../../../Vault/P5/current/xml/tei/Test * custom —> ../../../Vault/P5/current/xml/tei/custom * odd —> ../../../Vault/P5/current/xml/tei/odd * schema —> ../../../Vault/P5/current/xml/tei/schema * stylesheet —> ../../../Vault/Stylesheets/current/xml/tei/stylesheet * xquery —> ../../../Vault/P5/current/xml/tei/xquery release/oxygen —> Vault/P5/current/oxygen Does that make sense? Anything I’m missing? And of course, I’m curious about some more history that Lou(?) or James(?) might be able to share? Best Peter

3 2

Stylesheets meeting is scheduled for this Thu 04 Mar 19:00Z
by Bauman, Syd 01 Mar '21

01 Mar '21

If I understand correctly, we are scheduled to hold a Stylesheets meeting this coming Thursday, 04 March at 19:00Z to 20:30Z. That is * 11:00 PST * 14:00 EST * 19:00 GMT * 20:00 CET for 1½ hours. I am expecting we will spend a little time reviewing the fix for the 4.2.1 release, and intend to post here an actual agenda with a ticket or two to work on by at least 24 hours before the meeting. I am hoping Martina will also post the details of how to get to the meeting here at least a few hours before the meeting. Looking forward!

1 0

Slight borkitude in moduleRef content model display
by Martin Holmes 25 Feb '21

25 Feb '21

Hi all, Just clicking around in the various types of Guidelines outputs, and I noticed this: <https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html> Take a look at the content model. It's the same in the ebook; it's slightly different but I think also borked in the PDF (p. 1402). I don't think it's urgent, because it was the same in 4.1.0. I'll raise a ticket and start investigating. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

2 3

Version 4.2.0 released
by Nicholas Cole 25 Feb '21

25 Feb '21

Dear Council, The Release team is happy to report that with the exception of the Oxygen Plugin, the build and release of P5 4.2.0 and Stylesheets 7.51.0 has been done. The release notes need some moderately extensive updating, and I will be making some suggested changes and a pull request later today / tomorrow. Very best wishes, Nicholas, Meaghan, and Peter.

3 3

GPG Key
by Nicholas Cole 23 Feb '21

23 Feb '21

Dear Council, Just to note that the current expiration date for the TEI GPG key is the second of next month. This can be extended, of course, without problem, but I’m not sure whose task that is. Best wishes, Nicholas

2 3