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

Freeze announcement
by Helena Bermúdez Sabel 07 Jul '24

07 Jul '24

Dear all, We are officially in freeze: Please do not commit any changes to the dev branches until the release is finished. Best, H.

1 0

victims of version vagueness
by Bauman, Syd 25 Jun '24

25 Jun '24

I started working on the teidata.version = teidata.version.unicode | teidata.version.semver | teidata.version.calver | teidata.whatever system today. (In a branch I have not committed, let alone pushed.) Less than halfway through the process I ran into a (moderately embarrassing) problem. It turns out calVer<https://calver.org/> is not a calendar-based version numbering system as we had assumed during our recent discussions. It is rather a cheerleading document in favor of calendar-based versioning in general, with both a breakdown of the potential components such a version number might use, and a list of specific projects that use a calendar-based version numbering system (along with the pattern of aforementioned components that project uses). My first reaction is I have no idea what we should do about this. My second reaction is I can easily scope out a range of options, as follows. 1. Do nothing with calVer — drop it from the list of TEI datatypes-to-be. 2. Go whole-hog: For every system described by calVer, create a TEI datatype that validates it. E.g., the datatype for the Ubuntu system would be defined with something like <dataRef name="token" restriction="([4-9]|[1-9][0-9]|[1-9][0-9][0-9])\.(0[[0-9]|1[0-2])(\.[0-9]+)?"/> Datatypes could be named flatly, e.g. teidata.version.ubuntu, or could be named hierarchicly, e.g. teidata.version.calendar.ubuntu. 3. Something in between. (E.g., calVer divides systems into case studies, notables, and others; maybe do #2 but only for the case study ones.) I really don’t like #1, because, in general, this is a great way to do version numbering. I encourage everyone to scan the major portions of the calVer document, if not read the whole thing.

2 1

Next Stylesheets Meeting: June 24
by Helena Bermúdez Sabel 21 Jun '24

21 Jun '24

Dear all, The next Stylesheets meeting will take place on June 24th at 10am PDT / 1pm EDT / 5pm UTC / 7pm CEST. We will focus on the upcoming release, so if there is anything that you think needs to be tackled/discussed, please add it to the agenda: https://docs.google.com/document/d/1K2raVt7dB9ti_O7JMoRRnu0KJk1JZbblB2tPDfp… Best, Helena

1 0

Next Stylesheets Meeting (about testing infrastucture)
by Helena Bermúdez Sabel 24 May '24

24 May '24

Dear all, The next Stylesheets meeting will take place on May 27th at 10am PDT / 1pm EDT / 5pm UTC / 7pm CEST. Peter Stadler has kindly accepted to take the lead in this meeting, and do an overview of our testing infrastructure. Best, Helena

1 0

May Council Meeting changed to May 15, Buenos Aires travel doc
by Elisa Beshero-Bondar 09 May '24

09 May '24

Dear Council members, The Council meeting we’d planned for this Friday May 10 is now postponed to Wednesday May 15 at a new time: - 10:30am - noon Pacific time (Joey) - 1:30 - 3pm Eastern Time (Syd, Raff, Elisa) - 7:30 - 9pm CET (Sabine, Martina, Torsten, et al) It will be the usual Zoom link: https://psu.zoom.us/j/98850059066?pwd=UzhBL2NFc1lweWYzS2xZd2dqYVZpdz09 (Password: tei) I've also started a very rough Google Doc <https://docs.google.com/document/d/1EVwA5vbreWLUeyWJU286g43t4XKkIm2otkjjrtK…> to assist our travel planning to Buenos Aires. We're awaiting details on the locations of Council's meetings, but I think we'll have that very soon. Traditionally, Council members share arrival times / flight numbers (etc) here so we can look out for each other and try to meet at airports / stations as we arrive and depart. Please feel free to begin sharing your information here. We also have started using two new channels in Slack: * #f2f-planning * #tei-conference (where Torsten has begun discussing travel plans) One more thing! We need to determine dates for summer monthly meetings ahead of our trip to Buenos Aires, so please be thinking of good times of day and dates for our one 90-minute meeting per month. See you soon, and many thanks for all you do for the TEI! Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

CMC-SIG repo now a TEIC branch
by Bauman, Syd 15 Mar '24

15 Mar '24

I have created a new branch in the TEIC/TEI repo called “cmc”. It is a squashed fork of the TEI-CMC-SIG/TEI branch “cmc-features”. What this means (presuming I have done this right) is that most, if not all, further work on the new CMC chapter should be performed in the new branch. Harald and Michael do not have write access to that branch (I don’t think), so if they wish to commit a change they may have to either make a requests of someone who does, or commit to their TEI-CMC-SIG/TEI, in which case we would need to merge. Because there have been some updates to other parts of P5 (although none to CMC itself) in the past few weeks, I have generated new outputs (see below). In addition, Jenkins maintainers may want to make jobs for building the TEI cmc branch against the Stylesheets dev branch. * Guidelines: https://bauman.zapto.org/~syd/temp/CMC/Guidelines-web/en/html/index.html * Exemplars: https://bauman.zapto.org/~syd/temp/CMC/Exemplars/

1 0

Agenda for VF2F Fri 3/15 - Sat 3/16
by Elisa Beshero-Bondar 13 Mar '24

13 Mar '24

Dear Council, Here is a draft agenda for our VF2F this weekend <https://docs.google.com/document/d/1DeLuEw8p_ZVD9AM8HXX1-a3G9ycQXFsD-u6JD9t…>! Timing and Zoom link to access the VF2F are in the Google Doc. I've also posted the agenda in our Slack (to circulate at 8am EDT today!) Please feel free to add tickets or discussion items for the full Council session, or to prioritize particular tickets and issues that you want to make sure we address sooner rather than later! Also, please make sure I haven’t made timing mistakes for the meeting. Thanks, each of you, for making time for this important work session for Council! For those of you who can't join us, you'll still see lots of activity on the GitHub repos and in Slack, and I hope this VF2F gets us all moving productively on tickets and big issues, rolling toward our next release! Cheers, Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

TEI Council Upcoming VF2Fs, Modified Meeting schedule
by Elisa Beshero-Bondar 01 Mar '24

01 Mar '24

Greetings, TEI Council! We have a short virtual face-to-face (VF2F) meeting coming up on March 15/16. I'm traveling next week and won't be in a reliable place for internet the day of our scheduled Council call of March 8. I also think we don't really need this meeting with the VF2F. We need to work on our VF2F agenda, so I'll try to get a start on that and share it with the group for modification over the next couple of weeks. So let's cancel the meeting of March 8. If you'd like to use that 90 minutes this Friday to get together and work on a dedicated task or ticket, feel free to use my Council meeting Zoom at https://psu.zoom.us/j/98850059066?pwd=UzhBL2NFc1lweWYzS2xZd2dqYVZpdz09 I shall simply remove that March 8 meeting from our calendar. Cheers and see you in the middle of March! Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

Stylesheets meeting: change of date
by Helena Bermúdez Sabel 01 Mar '24

01 Mar '24

Dear all, We were meant to meet next Friday (March 23rd). However, I won't be able to chair the meeting this coming week, so I propose meeting on March 1st instead. If there is a preference for keeping the original date, maybe someone else can volunteer to chair the meeting? Apologies for this change. I will send the agenda in the following days. Best, Helena

5 6

monthly ticket triage
by Bauman, Syd 01 Mar '24

01 Mar '24

I performed ticket triage this morning. All issues and pull requests in the TEI and Stylesheets repos that are < 2 years old now have assignees except the Stylesheets issue I opened yesterday (Documentation file teixsl.xml needs updating #665<https://github.com/TEIC/Stylesheets/issues/665>). This issue could be a pretty sizeable task, since that document has not had any significant updates since 2015. That said, it is not huge: the document is only a bit over 2,500 words long. It has 6 or 7 major divisions and some 45 paragraphs. In principle I do not mind doing this myself. But my plate is already pretty full. Maybe we could divide and conquer, or maybe someone who wants to review how the Stylesheets work (for users) just wants to take it on?

2 1