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

Next release + working groups
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jul '21

08 Jul '21

Dear all, The next release will take place in about one month+ (refridge 11 Aug; freeze 15 Aug; release 18 Aug). There are a lot of issues labeled with milestone 4.3.0 (https://github.com/TEIC/TEI/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Gu…). I want to ask you to focus on those issues and tackle as many as we can before refrigeration. If you think you cannot tackle the issue before the next release, please remove the milestone 4.3.0 or change the milestone label to 4.4.0. In our meeting today we discussed to organize small working groups in July/begin of August. This is how it works: if you want to work on an issue (ticket or otherwise) in pairs or a small group, please ask for a potential "buddy" on the mailing list or on Slack to join you. Best, Martina

1 0

Call starts in 1 hour
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jul '21

08 Jul '21

Dear all, our call starts in one hour. This is the agenda: https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…<https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…> Best, Martina Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Montag, 5. Juli 2021 09:43 An: tei-council(a)lists.tei-c.org Betreff: Call on Thursday, July 8 Dear all, This is the agenda for our next regular Council call on Thursday, July 8 at 10:30am-12:00pm PDT, 1:30pm-3:00pm EDT, 6:30pm-8:00pm BST, 7:30pm-9:00pm CEST https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…<https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…> Please add issues you would like to discuss. Best, Martina

1 0

Call on Thursday, July 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 05 Jul '21

05 Jul '21

Dear all, This is the agenda for our next regular Council call on Thursday, July 8 at 10:30am-12:00pm PDT, 1:30pm-3:00pm EDT, 6:30pm-8:00pm BST, 7:30pm-9:00pm CEST https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31… Please add issues you would like to discuss. Best, Martina

1 0

Organisation of SVF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Jul '21

01 Jul '21

Dear all, Since we could not find a suitable date for the SVF2F meeting in July or August, I've set up a new Doodle for September/first half of October. Please fill in your possible dates. https://doodle.com/poll/ptp7wp5w8hes5tpm?utm_source=poll&utm_medium=link As always, the North American Group will start Friday evening, the European group will continue on Saturday morning, and we meet all together on Saturday afternoon (for the Europeans) / Saturday morning (for the North Americans). Best, Martina

1 0

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