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

Progress on labeling tickets
by Martin Holmes 11 Jun '20

11 Jun '20

Hi all, Today Elisa and I added all the labels we think appropriate for all tickets starting at the oldest and running up to #319. That seems to be half of the tickets, so we think our work is done. A few tickets got closed in the process. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

housekeeping: delete stale branches
by Peter Stadler 10 Jun '20

10 Jun '20

Dear all, here’s yet another(?) proposal for housekeeping: Both Stylesheets and Guidelines repo feature various stale branches which I would like to get rid off [1,2]. Some of those are prefixed with a Councilists name so I encourage everyone to look through his/her branches and eventually delete outdated/unused/forgotten branches. Some of the stale branches are even just behind dev without featuring any commits *ahead* of dev (e.g. the TEI/help branch). I think those can safely be removed and would do so in the next days if no one objects. This does include release branches which I’d also like to get rid of because IMHO they do not serve any purpose anymore (the important information is kept in the tags). Best Peter [1] https://github.com/TEIC/Stylesheets/branches/stale [2] https://github.com/TEIC/TEI/branches/stale [3] https://github.com/TEIC/TEI/tree/help

3 3

call in 10 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Jun '20

09 Jun '20

Dear all, Our call starts in 10 minutes: https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w… Best, Martina

1 0

Reminder: Council meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '20

08 Jun '20

Dear all, This is a reminder that our next Council meeting is tomorrow, June 9 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30 Please find the agenda here and add topics that we should discuss https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w…<https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w…> You can find the zoom link for the meeting in the google doc. Best, Martina

1 0

Next Council meeting: Tuesday, June 9
by Scholger, Martina (martina.scholger＠uni-graz.at) 05 Jun '20

05 Jun '20

Dear all, Our next Council meeting is on Tuesday, June 9 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30 Please find the agenda here and add topics that we should discuss https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w… You can find the zoom link for the meeting in the google doc. Best, Martina

1 0

P5/Utilities-1 and P5/Utilities
by Peter Stadler 04 Jun '20

04 Jun '20

Dear all, while working on some old TEI->LaTeX->PDF issues I stumbled (once again) across those two folders P5/Utilities-1 and P5/Utilities in the Guidelines repo. Can somebody shed some light on the difference of these folders? I’m especially interested in the file guidelines-latex.xsl which exists in both directories but only the one in Utilities seems to be used for building the PDF version of the Guidelines? Many thanks Peter

2 2

Noto fonts
by Peter Stadler 03 Jun '20

03 Jun '20

Hi Martin, I'm about to push some changes to the TEI repo that will set the Google Noto fonts as default for the PDF Guidelines (processed via LaTeX). That requires the fonts-noto-cjk package (on Debian) in the respective build environment. It is already included in our Jenkins Docker image but you might need to add that manually to your Jenkins? Just wanted to give you a warning (shortly) ahead of time ;) Best Peter

2 1

plan for Stylesheets, and versions, and tags, oh my!
by Syd Bauman 03 Jun '20

03 Jun '20

At one point we had a Stylesheets meeting planned for this Tue 02 Jun at 13:00Z. Various other plans have cropped up since. Basically, Elisa, Martin, Peter, and I have not finished the Stylesheets categorization project; although we have made good progress, we still have more to go, and would like to use that time slot. Furthermore, Peter has suggested (and I readily agree) that we, Council, need to talk about teidata.version. Thus my suggestion is 1. a 1-hour meeting at 13:00Z with as many Council members as will show up to discuss version numbering and (time permitting) Stylesheets 2. a 1-hour meeting at 14:00Z of PS & SB and MH & EB to do more Stylesheets labeling. I, for one, have another meeting at 15:00Z which I do not want to be late for.

10 11

Do we need better issues?
by Raffaele Viglianti 29 May '20

29 May '20

Hi all, After today's meeting, I started thinking about why we often end up in loops of discussion. Keeping in mind that this is a partial and personal view, I think that this happens for a few reasons: some are good (e.g. disagreement that needs to be worked out), some are ok (e.g. someone forms an opinion while missing a key piece of context --mea culpa), others are due to the ticket (e.g. it's verbose, it's unclear, it's too short, the discussion is long, etc.) To address the latter, I think we need to ask more of our submitters (including ourselves when creating issues). Each issue should state clearly what the problem is, show clear examples, and offer a solution. Many issues do (I think of the UVic ones are particularly exemplary, however extreme their requests may often appear to me :) ), but the style varies too much and it makes it time consuming for us to figure out what the real issue is and to reprise quickly on second iterations. I wonder if a strict issue template may help us here. GitHub allows to configure multiple templates <https://help.github.com/en/github/building-a-strong-community/using-templat…> (e.g. a bug report template could be default, with the possibility to switch to a feature request one, and perhaps others). Templates pre-populate an issue with headers and a description of what's required for consideration, thus at least encouraging a standardized way of formulating a bug report/feature request. Even if these templates were fairly simple we would still benefit. But I think we could go further and take inspiration from software design documents as a template, which will require the issue reporters to not just do their research, but present it properly too. The DocNow project at MITH creates such documents (publicly) to help discussion within the dev group, and as a crucial means to remind ourselves of why we set to do something (because we all work on dozens of projects and forget things). Here is a very good example <https://www.docnow.io/design/2019-05-21-conversation>. I think forcing this on submitters will weed out partially thought out requests, which will always result in us at least wasting time at best closing or getting back to the submitter, at worst engage in loopy "what if" discussions. We have plenty of issues, so I'm not worried about scaring people away. In fact, i wonder if more structure may even encourage less proficient users to contribute more meaningfully. Templates will also give us -- hopefully -- clearer requests with a proposal for a solution built-in. What do you think? Finally, if we did choose to use this GitHub feature, we should also look at their recommendations for adding a code of conduct <https://help.github.com/en/github/building-a-strong-community/adding-a-code…>. TEI's is hidden deep in the tei-c site <https://tei-c.org/about/code-of-conduct/> but we may want to bring it into the repository and close to the issue submitting process. Thanks for indulging me and I'm well prepared to be told that this in an unnecessary complication and that we should proceed as usual :) Best, Raff

6 6

labels for Stylesheets issues
by Syd Bauman 25 May '20

25 May '20

Martin and I came up with a proposed list of labels for Stylesheets issues today. My suggested schedule is that over the next week we review and tweak the list as needed. Then on or about Sun 17 May someone who has some color sense will go ahead and actually change the label values in GitHub. Then during the week of the 18th, flowing over to the week of the 25th as needed, the subgroups (SB, PS, MH, EB|MS) work on categorizing the 139 open issues with the new labels. The list proposed is not intended to be definitive. I expect it to be adjusted both now by Council, and then during the actual cataloging exercise. So take a loot at https://docs.google.com/spreadsheets/d/1TugARD1amG-ZeMPl2Fo-e88VXqirHawmOs5… and comment away.

6 15