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

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