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

Menus. Point release?
by Hugh Cayless 22 Jun '21

22 Jun '21

Hi All, You may or may not have noticed that the menus on the Guidelines pages no longer 100% match the menus on the rest of the website. That's because we've sorted out how to edit the website menus, but the Guidelines menus are static, generated from the website at build time. I've just committed a new version that grabs the menu structure live from the website API and incidentally also dispenses with the old UDM Javascript menu code—in our brave new world, you can do these things exclusively in CSS, so why not? My question is whether this warrants a patch release to get things lined up again. Or really whether this even rises to the level of a patch. Maybe it should stay 4.2.2, just with a different build tag. Or we could just wait until the next release :-). Hugh

2 1

upcoming Stylesheets meeting
by Bauman, Syd 21 Jun '21

21 Jun '21

We are scheduled to hold a Stylesheets meeting this coming Thu 24 Jun at 17:30Z for 1½ hours. That is * 10:30–12:00 PDT * 13:30–15:00 EDT * 18:30–20:00 BST * 19:30–21:00 CEST Martina — will you be sending out a Zoom (or whatever) link or shall I? Proposed agenda: 1. Ticket 444<https://github.com/TEIC/Stylesheets/issues/444>, which we have tried before, but for which Martin & I have a new proposed solution. 2. Ticket 399<https://github.com/TEIC/Stylesheets/issues/399>, which we have tackled in the past only to find there were sequalae to the obvious solution. One possible approach: if we have 6 or more people, we could split into 2 groups and tackle them simultaneously. I like that idea for reasons of efficiency; I don’t like it in that I would feel left out of ½ of the fun.

3 2

Meeting times: Council and Stylesheets call
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Jun '21

19 Jun '21

Dear all, at our last Council meeting we agreed that we want to start with our monthly Council and Stylesheet call 30 minutes earlier. I hope this is also fine for the Council members who were not present at this meeting, and for Martin and Nicholas who regularly attend the Stylesheets meeting. This means that we start at: 10:30am PDT, 1:30pm EDT, 6:30 BST, 7:30pm CEST. Our next Stylesheets call is on Thursday, June 24. Best, Martina

2 1

renamed Jenkins repo branch to main
by Peter Stadler 15 Jun '21

15 Jun '21

Dear all, just a quick note that I changed the branch name from master to main in the Jenkins repo [1]. Additionally, I merged the current dev branch into the (new) main branch since this branch was not building anymore due to an outdated Debian package. housekeeperly greetings Peter [1] https://github.com/TEIC/Jenkins

1 0

handling multiple slots of different durations of service
by Bauman, Syd 14 Jun '21

14 Jun '21

[For Janelle our Nominations Committee representative] Problem: There are 6 positions open on Council, 4 of which are for 3-year terms (the usual), and 2 of which are for 1-year terms (due to recent by-law change). Possible solutions, from the idiotic to the clever (but not necessarily in that order here) include: 1. Elect 6 people, randomly assign who gets 1- and who gets 3-year terms. 2. Hold separate elections in OpaVote (or whatever) as if they were entirely different positions. 3. Just elect 6 people, let Council decide which ones serve for how long. 4. Just elect 6 people, let them fight it out among themselves. 5. Elect 6 people, let them each blindly choose 1- or 3-year term based on ranking 6. Elect 6 people, let them each choose 1- or 3- year term based on ranking in discussion with each other. Since #5 and #6 are my suggestions, I will detail them a bit, below. Worth noting, though, that although #2 has the huge advantage that a nominee could decide in advance that she wants to stand for only 1 year, it simultaneously has the disadvantage that each nominee has to decide in advance how many years he wants to run for, and he might win or lose depending on who else decides to go for that number of years. More importantly, perhaps, running a separate election would likely be a big pain for those running the elections. Because we are using an instant run-off election or ranked-choice voting system, whoever is running the election knows who among the 6 people elected got the most votes, the 2nd most votes, etc. (Even if that information is not shared with the electorate.) Thus for suggestions #5 the highest ranked Councilor-elect gets to choose whether she wants one of the two 1-year or one of the four 3-year terms. Then the 2nd highest is asked if he wants the one remaining 1-year or one of the four remaining 3-year terms OR if he wants one of the two remaining 1-year or four remaining 3-year terms. If any 1-year terms remain, the third ranking is asked to choose. And so on, until there is no longer any choice (because only one term length remains available). In suggestion #5, each Councilor-elect is queried in private (probably via e-mail or phone call) in rank order. Suggestion #6 is the same, but to ask the question of each in order with all 6 of them in the same (virtual) room, so haggling can take place. (So someone who really only wants to commit to 1 year can maybe convince someone higher in the rankings who doesn’t care …)

3 2

Reminder: meeting start in 90 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Jun '21

10 Jun '21

Dear all, please have a look at the agenda for our meeting at 10am-11:30pm PDT/1pm-2:30pm EDT/6pm-7:30pm BST/7pm-8:30pm CEST - which is one hour earlier than usual: https://docs.google.com/document/d/1THZdj_acrUBpBejrs7MJA7eTtDtHGTZqAEa-T8i… Best, Martina

1 0

Tomorrow's meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Jun '21

09 Jun '21

Dear all, For those who didn't see the poll on slack about the meeting times tomorrow: Would it be possible for you to start the meeting an hour earlier (at 10am PDT / 1pm EDT / 6pm BST / 7pm CEST) so that Elisa and Janelle can join the whole meeting? Best, Martina

1 0

Next Council call: June 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '21

08 Jun '21

Dear all, This is the agenda for our next Council call on Thursday, June 10 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1THZdj_acrUBpBejrs7MJA7eTtDtHGTZqAEa-T8i… Since we could not agree on a new date that suits everyone, we will stick with Thursday for the time being. Best, Martina

2 2

Stylesheets meeting?
by Bauman, Syd 27 May '21

27 May '21

Martina — I forgot ask in last e-mail that you let us know where the Stylesheets meeting will take place. If I don't hear from you in ~2 mins (here or Slack), I will post a personal Zoom meeting invitation here.

4 4

Meeting in ~46.3 hours
by Bauman, Syd 27 May '21

27 May '21

We are scheduled for a Stylesheets meeting this coming Thu 27 May, 18:00/19:30Z. That means starting at * 11:00 PDT, * 14:00 EDT, * 19:00 BST, & * 20:00 CEST, and scheduled to run for 1½ hours. Agenda items I would like to cover, other suggestions welcome: * (~4 min) Quick review of P5subset updating plans * (~4 min) report on progress on automation thereof (PS) * (~4 min) Quick report on #496<https://github.com/TEIC/Stylesheets/pull/496> progress (either MH or NC) * (~1 hour) Ticket #327 <https://github.com/TEIC/Stylesheets/pull/327>

2 1

Stylesheets meeting: May 27
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 May '21

25 May '21

Dear all, This is the zoom link for our meeting on Thursday, May 27 at 11 am PDT / 2 pm EDT / 7 pm BST / 8 pm CEST: https://zoom.us/j/94174447570?pwd=eGJmNXdkYlZsVWhSMHdNVmdONjZyQT09 And here is a blank google doc to which Syd will hopefully add some exciting issues. https://docs.google.com/document/d/1wbrqKTXN3_8cw4VCmn3rEJicu6SnwiDBcKWpwS9… Best, Martina

1 0

xmllint issues
by BERMUDEZ SABEL Helena 23 May '21

23 May '21

Hi all, At the last Stylesheets meeting, we checked how the command "xmllint --format -" that is run when testing the HTML transformations adds the XML declaration to the output file (which was a bit counterproductive because the XSLT code was explicitly demanding the omission of the declaration). Now I’ve run into another problem that is also generated due to the xmllint command: it outputs XML entities when a literal string is expected. I run the script without xmllint and the output is the expected one so it seems that it is another of the modifications done by this program. This issue primarily affects the quotation marks that are added in the HTML output using CSS. See diff: 17c16 < content:"‘"; --- > content:"‘"; 20c19 < content:"’"; --- > content:"’"; 23c22 < content:"“"; --- > content:"“"; 26c25 < content:"“"; My guess is that this wasn’t an issue before because xmllint had as an input a file with the XML declaration. Now it finds a file whose first line is the HTML doctype declaration and thus adds these modifications. Considering that in the HTML transformation Saxon already has the command to indent the results, my proposal is to modify Test/Makefile and delete the "xmllint" command ONLY for the transformations to HTML. Would this be a viable solution? Best, H. Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel

3 4

Doodle for regular Council call
by Scholger, Martina (martina.scholger＠uni-graz.at) 13 May '21

13 May '21

Dear all, As discussed during the VF2F meeting, I've set up a doodle to coordinate the meeting times for the monthly Council call for the next couple of month. I'll try again with the second week of each month (2nd Mon/2nd Tue etc.). As soon as we figured out the dates for the Council call, I'll set up a doodle to coordinate the Stylesheets meeting. Please fill in the doodle by 2021-05-17. https://doodle.com/poll/h3v3kwctxztauz9r?utm_source=poll&utm_medium=link Best, Martina

2 1

This is a test
by Peter Stadler 12 May '21

12 May '21

… as requested by Martina Best Peter

1 0

Next call: Thu May 13
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 May '21

11 May '21

Dear all, This is the agenda for our next regular Council call on Thursday (May 13) at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1pxhmicmZMLMaOfNfDb0BCCLO9jvn0cKRpma91xt… Best, Martina

1 0

VF2F meeting, May 7 and 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 May '21

01 May '21

Dear Council, This is the agenda for our virtual F2F meeting on Friday and Saturday (May 7 and 8): https://docs.google.com/document/d/18ZqzRQVAEA6yShflaahqs092xegVDrZosbIIVyK… Please feel free to add more topics to the agenda. Best, Martina

1 0

Issue 178 branch built successfully
by Martin Holmes 22 Apr '21

22 Apr '21

For everyone who was at the Stylesheets group meeting today: It looks like our ticket #178 work was successful, so I believe it's OK for someone to merge that branch. The temporary Jenkins job succeeded, and I just ran Test2 locally without problems. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

reminder: upcoming Stylesheets meeting Thu 22 Apr 18:00Z
by Bauman, Syd 22 Apr '21

22 Apr '21

We have a Stylesheets meeting scheduled for this coming Thursday 22 April 21 at 18:00Z for 1½ hours. That is * 11:00 PDT * 14:00 EDT * 19:00 BST * 20:00 CEST I hope to post a list of topics 48 hours before the meeting starts. (I expect to post a list of topics 24 hours before the meeting starts. :-) I hope Martina will post the Zoom details and perhaps a Google Doc for us to use 24 hours before the meeting starts. (I expect Martina to post the Zoom details and perhaps a Google Doc for us to use 24 minutes before the meeting starts. :-)

3 2

Fwd: Travis CI: [27421] - OSS credits for Text Encoding Initiative (@TEIC)
by Peter Stadler 20 Apr '21

20 Apr '21

Hi all, fowarding this fyi. That means, Travis checks are currently working again for the TEI repos (you may have noticed the reappearance of the green check marks at the GitHub commits?) Yet we were only provided a total of 25k credits which will not last long. So I think we should move on to GitHub actions (next to our self hosted Jenkins servers). I’m volunteering to do so but will not get to it in the near future. So, if anyone else steps forward please go ahead! Best Peter > Anfang der weitergeleiteten Nachricht: > > Von: "Qasim Abdullah (Support)" <support(a)travis-ci.com> > Betreff: Travis CI: [27421] - OSS credits for Text Encoding Initiative (@TEIC) > Datum: 14. April 2021 um 22:23:18 MESZ > An: Peter Stadler <pstadler(a)mail.uni-paderborn.de> > Antwort an: Support <support(a)travis-ci.com> > > ##- Please type your reply above this line -## > from Travis CI has an update for your ticket, #27421 <https://support.travis-ci.com/hc/requests/27421>. If you'd like to add additional comments, please reply to this email: > > > > Qasim Abdullah (Travis CI) > Apr 14, 2021, 16:23 EDT > > Hello Peter, > > Please accept our sincere apologies for any inconvenience caused due to delays in processing your open-source credit request while we made improvements to the platform. > > Open source has always been and always will be at the core of what Travis CI stands for. After reviewing your open source qualifications, I am pleased to notify you that 25k credits were added to your Github Organisation "TEIC" allowing you to resume running OSS builds. When your credits begin running low again, please reach back out to the Support team. > > Credits Consumption Metric > OS. # CREDITS PER STARTED BUILD MINUTE > Linux. 10 > Experimental FreeBSD. 10 > Windows. 20 > MacOS. 50 > > > Please let us know if you have any questions! > > Thanks and happy building!, > > -- > Qasim > > Your Friends @Travis CI > > Test and Deploy with Confidence. > www.travis-ci.com <http://www.travis-ci.com/> > — > Travis CI GmbH, Rigaer Str.8, 10247 Berlin, Germany | GF/CEO: Randy Jacops | Contact: contact(a)travis-ci.org <mailto:contact@travis-ci.org> | Amtsgericht Charlottenburg, Berlin, HRB 140133 B | Umsatzsteuer-ID gemäß §27 a Umsatzsteuergesetz: DE282002648 > > > > > Peter Stadler > Mar 16, 2021, 11:17 EDT > > Hi Travis support, > > the Text Encoding Initiative was happily using Travis CI for automated testing of our Open Source software hosted on GitHub and we really enjoyed the seamless support – many thanks for that! Recently we were hit by the new(?) constraint on credits so I wanted to ask whether (and how) it’d be possible for us to obtain ~10,000 monthly credits? > > My account name is @peterstadler on GitHub and I’m asking for the @TEIC organisation. > > Many thanks in advance > and best regards > Peter > signature.asc > > Attachment(s) > signature.asc <https://support.travis-ci.com/attachments/token/w2bwTYU0a9oSxX3D9GV6anmkE/?…> > This email is a service from Travis CI. Delivered by Zendesk <https://www.zendesk.com/support/?utm_campaign=text&utm_content=Travis+CI&ut…>[5LKOVG-94G7]

1 0

oXygen plug-in 14.0.0 releaesd
by Bauman, Syd 20 Apr '21

20 Apr '21

Martina — Martin, Hugh, and I have just released the new oXygen plug-in 14.0.0 for 4.2.2 and 7.51.2 (both bleeding edge, which is automatic, and real one via GitHub). This can be announced. In the process Martin updated the ant build script to work with the new Humana server. Martin is planning to update TCW22 within the next few hours.

4 4

GPG Key Expiration
by Nicholas Cole 19 Apr '21

19 Apr '21

Dear Council, Just to let you know — as part of creating the P5 4.2.2 release, I needed to update the expiration date for the gpg key, in order to build the Debian Package. I’ve set it for 3 months hence, but obviously it can be changed to whatever the Council thinks is appropriate! Best wishes, Nicholas

2 1

New release: Guidelines 4.2.2 / (unchanged) Stylesheets 7.51.2
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Apr '21

19 Apr '21

Dear TEI Community, After release 4.2.1, an issue was noticed concerning the controlled value lists of certain type attributes. The list was not appearing in either the documentation output or schemas. Thus a followup version 4.2.2 of the Guidelines and a corresponding (but unchanged) version 7.51.2 of the Stylesheets has been released to fix the issue. The following change was made to the Guidelines: * Add a mode attribute with value add (#2128<https://github.com/TEIC/Stylesheets/issues/2128>) to each type attribute that overrides the att.typed class. Thanks to Syd Bauman, Helena Bermúdez Sabel, Hugh Cayless, Nicholas Cole, Martin Holmes, Janelle Jenstad, and Peter Stadler for discovering and fixing this issue and accompanying the release process. Please find the full release notes including the notes of the Guidelines versions 4.2.1 and 4.2.0 and the Stylesheets versions 7.51.1 and 7.51.0 here: https://tei-c.org/Vault/P5/current/doc/tei-p5-doc/readme-4.2.2.html All of the TEI Consortium's software projects are hosted at https://github.com/TEIC and issues or feature requests should be reported at the various project repositories there. The Guidelines are available from all the usual places (such as the TEI website http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html and the GitHub site https://github.com/TEIC/TEI/releases/tag/P5_Release_4.2.2) A new release of the TEI Stylesheets has been made in conjunction with the 4.2.2 release at https://github.com/TEIC/Stylesheets/releases/tag/v7.51.2. Furthermore, the Debian package has been updated at http://packages.tei-c.org/deb/. The TEI Guidelines and the Stylesheets are also available for download at https://sourceforge.net/projects/tei/files/. A documentation on how to update your oxygen is available at https://github.com/TEIC/oxygen-tei/blob/master/oxygen-tei-plugin.md. As always, we encourage you all to report bugs and make feature requests via the GitHub site at https://github.com/TEIC/TEI/issues. 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/

1 0

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