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 issuehttps://github.com/TEIC/TEI/issues/2170. Yes, queries are (in some sense) supposed to be on TEI-L or in the GitHub discussion group thingieshttps://github.com/TEIC/TEI/discussions, 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?)
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
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 list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Responses interspersed among excerpts.
Thanks for calling attention to the newest issue.
Uhhh … you’re welcome?
Wouldn’t this get an “i18n” label and a “TEI: Guidelines and Documentation” label?
Yes, I think you are absolutely correct. As you can tell by my lovely (but mis-guided) response on the ticket itself, I completely missed the first sentence. (Well, to be more precise, all but the last 2 words of the 1st sentence … my screen had scrolled such that I thought the 1st two words of the entire post were “on 4.2.1” because of the way that first para was wrapped. Sigh.) Nonetheless, we still need the new labels, IMHO. 🙂
I wonder if your “meta” label could just be called “GitHub” …
Sounds quite reasonable. (I suppose the difference would be whether we would keep the same labels if we moved from GitHub to some other hosting. Since I have no idea, I think it does not matter, either “meta” or “GitHub” would be fine.)
I think straightforward queries should be moved to TEI-L at the first triage point and closed. If they're simple info requests they could be answered on the ticket directly, with a note asking the person to direct any follow-up to TEI-L, and then closed. The main thing is to get them out of the way quickly, I think. Cheers, Martin On 2021-08-14 7:22 a.m., Bauman, Syd 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 https://github.com/TEIC/TEI/issues/2170.
Yes, queries are (in some sense) supposed to be on TEI-L or in the GitHub discussion group thingies https://github.com/TEIC/TEI/discussions, 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 list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca
Makes sense to me! But I bet there are those among us who will say that mailing lists are ancient technology, and we should not be encouraging people to use one, let alone forcing them. ________________________________ I think straightforward queries should be moved to TEI-L at the first triage point and closed. If they're simple info requests they could be answered on the ticket directly, with a note asking the person to direct any follow-up to TEI-L, and then closed. The main thing is to get them out of the way quickly, I think.
Hi Syd,
I think if the TEI is to move away from mailing lists to something more modern (i.e. more transiently fashionable) such as Discord or whatever), that should be decision for the whole community to take.* But it doesn't make sense to mix random queries and discussions with tickets, partly because queries and discussions benefit the whole community, and everyone sees them when they show up on the mailing list. When someone raises a ticket, only a small subset of the community will even be aware of it.
*Personally I think mailing lists are excellent for our purposes, and it's no bad thing to encourage younger users to get familiar with them. But if we were to migrate to something else, I think it should be a complete migration, rather than fragmenting the community discussions across multiple platforms.
Martin Holmes
UVic Humanities Computing and Media Centre
mholmes@uvic.ca
________________________________
From: Tei-council
As I said, I’m with ya, mate. ________________________________ I think if the TEI is to move away from mailing lists to something more modern (i.e. more transiently fashionable) such as Discord or whatever), that should be decision for the whole community to take.* But it doesn't make sense to mix random queries and discussions with tickets, partly because queries and discussions benefit the whole community, and everyone sees them when they show up on the mailing list. When someone raises a ticket, only a small subset of the community will even be aware of it. *Personally I think mailing lists are excellent for our purposes, and it's no bad thing to encourage younger users to get familiar with them. But if we were to migrate to something else, I think it should be a complete migration, rather than fragmenting the community discussions across multiple platforms.
Regarding the original question: * a label for discussing labels or other github topics (maybe “meta” or “label”) I don’t think we should have a label for labels, „GitHub“ (as a label) is too constrained to me for which I like „meta“ better. Yet, I wonder if we need to label everything? (BTW, GitHub has the nice feature of filtering for ’no:label’ which will give you all those issues that we failed to label – for whatever reason) * a label for queries like the newest issue. That is quite common in many (GitHub) projects and is often labeled „question“. Cheers Peter
Am 15.08.2021 um 22:08 schrieb Bauman, Syd
: As I said, I’m with ya, mate.
I think if the TEI is to move away from mailing lists to something more modern (i.e. more transiently fashionable) such as Discord or whatever), that should be decision for the whole community to take.* But it doesn't make sense to mix random queries and discussions with tickets, partly because queries and discussions benefit the whole community, and everyone sees them when they show up on the mailing list. When someone raises a ticket, only a small subset of the community will even be aware of it.
*Personally I think mailing lists are excellent for our purposes, and it's no bad thing to encourage younger users to get familiar with them. But if we were to migrate to something else, I think it should be a complete migration, rather than fragmenting the community discussions across multiple platforms.
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
participants (4)
-
Bauman, Syd
-
Elisa Beshero-Bondar
-
Martin Holmes
-
Peter Stadler