Hi Syd,Thanks for calling attention to the newest issue. Wouldn’t this get an “i18n” label and a “TEI: Guidelines and Documentation” label? As I look at the passage + example in 4.2.1, I can see why it’s confusing for someone who is not a native speaker of English. And that makes me think we might want to revise the Guidelines as we respond to the good question. (I found myself wondering about the difference between a “subheading” and a “detail heading” and whether the word “detail” is necessary there.)
Isn’t any ticket a “query”? This one simply asks for clarification, so it’s not a feature request or an outright request to improve the writing. But it’s about the Guidelines, isn’t it? So that seems reasonable—we could be promoted to do something or just reply to explain and help the translator.
Recently Peter mentioned some changes in our TEI GitHub organization. I wonder if your “meta” label could just be called “GitHub” and apply to queries/ideas/proposals about labels, repos , etc.?
Elisa
Elisa Beshero-Bondar, PhD (she/they)
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
Typeset by hand on my iPhone
On Aug 14, 2021, at 10:23 AM, Bauman, Syd <s.bauman@northeastern.edu> wrote:
We need (at least) 2 more labels for the TEI repo:
- a label for discussing labels or other github topics (maybe “meta” or “label”)
- a label for queries like the
newest issue.
Yes, queries are (in some sense) supposed to be on TEI-L or in the GitHub
discussion group thingies, but if users put them in as an issue, we should be able to tag it as such. (Or perhaps we should move it to a discussion place and close it?)
_______________________________________________Tei-council mailing listTei-council@lists.tei-c.orghttp://lists.lists.tei-c.org/mailman/listinfo/tei-council