On Mon, May 25, 2020 at 9:58 AM Peter Stadler <pstadler@mail.uni-paderborn.de> wrote:

Sorry for being late to the party. Just two comments:
a) re "to/from X“: Although subcategorizing is sometimes helpful (as Elisa pointed out) I think most of the time the broader category will suffice (and won’t blow up the total amount of labels). So, I’m in the team Martin/Syd here :)
b) i18n: I’m somewhat hesitant to put that much ‚burden‘ on a group that just formed itself (and which is not an ‚official‘ body of the TEIC). I’d prefer to name the label simply „i18n“, i.e. remove the „group:“ prefix.

Best
Peter

> Am 18.05.2020 um 23:53 schrieb Martin Holmes <mholmes@UVIC.CA>:
>
> Good question! I think we probably also need a label for "documentation" somwhere in the mix; I don't think that particular ticket is a meta issue (i.e. an issue about issues themselves).
>
> How about target: documentation?
>
> Cheers,
> Martin
>
> On 2020-05-18 1:39 p.m., Scholger, Martina (martina.scholger@uni-graz.at) wrote:
>> Hi Martin and all,
>> Thanks for the explanation. I'm sure the hordes will arrive any day now : )
>> I added/modified the labels. Please feel free to change the colors if you don't like them or if they don't make sense.
>> I wonder if we can delete the label "Release Process" and add the label "meta" to this issue: https://github.com/TEIC/Stylesheets/labels/Release%20Process.
>> Best,
>> Martina
>> -----Ursprüngliche Nachricht-----
>> Von: Martin Holmes <mholmes@uvic.ca>
>> Gesendet: Sonntag, 17. Mai 2020 20:03
>> An: Scholger, Martina (martina.scholger@uni-graz.at) <martina.scholger@uni-graz.at>; Elisa Beshero-Bondar <ebbondar@gmail.com>
>> Cc: TEI Council <tei-council@lists.tei-c.org>
>> Betreff: Re: AW: [Tei-council] labels for Stylesheets issues
>> Hi Martina,
>> I like all your suggestions.
>> Re "Council Responsibility": IIRC, this arose out of the ancient dreadm whereby hoards of enthusiastic non-Council folks would emerge from the community and take ownership of the maintenance of various areas of the stylesheets repo, leaving only a few core areas to be the responsibility of the Council. I don't think that will ever happen, but there are things such as the Cocoa conversion and the custom profiles which I think it would be reasonable for Council to ignore in favour of higher-priority work. I think it would be reasonable to require that all tickets end up with one of the resp: values:
>> resp: council
>> resp: stylesheetsGroup (i.e. Council's job, but suitable for learning and teaching)
>> resp: helpWanted (i.e. anybody who cares about this should probably do it themselves)
>> Cheers,
>> Martin
>> On 2020-05-17 10:52 a.m., Scholger, Martina
>> (martina.scholger@uni-graz.at) wrote:
>>> Dear Martin and Syd,
>>>
>>> thanks for putting this together!
>>>
>>> I added another column to record how the current labels relate to the
>>> suggested ones. It is for the person who adds/renames the current
>>> labels (I volunteer for that).
>>>
>>> I like to suggest three more labels which we recently added to the TEI
>>> repo:
>>>
>>> i18n (or maybe better Group: i18n)
>>>
>>> Group: Infrastructure
>>>
>>> Status: pending (e.g. for issues where we asked the original proposer
>>> or someone else to provide an example or further explanation)
>>>
>>> I wonder if your suggested ‘resp: council’ corresponds with the
>>> current ‘Council Responsibility’? We also have the label
>>> CouncilResponsibility in the TEI repo and I was wondering how exactly that is defined.
>>>
>>> Best,
>>>
>>> Martina
>>>
>>> *Von:*Tei-council <tei-council-bounces@lists.tei-c.org> *Im Auftrag
>>> von *Elisa Beshero-Bondar
>>> *Gesendet:* Freitag, 15. Mai 2020 18:34
>>> *An:* Martin Holmes <mholmes@uvic.ca>
>>> *Cc:* TEI Council <tei-council@lists.tei-c.org>
>>> *Betreff:* Re: [Tei-council] labels for Stylesheets issues
>>>
>>> Martin and all— Right, it won't matter for *assigning* the ticket, but
>>> it would be helpful later when reviewing one's assigned tickets. I was
>>> imagining this as an optional, handy classifier once you have a pile
>>> of these to work on. Sometimes it just isn't clear from a quick scan
>>> of the issue which direction the conversion needs to go, and in those
>>> cases, when you've made a determination and then need to go back and
>>> work on it some unspecified while later, it might just help to know at
>>> a glance which direction this is going.
>>>
>>> Thanks,
>>>
>>> Elisa
>>>
>>> On Fri, May 15, 2020 at 12:21 PM Martin Holmes <mholmes@uvic.ca
>>> <mailto:mholmes@uvic.ca>> wrote:
>>>
>>> Hi Elisa,
>>>
>>> Having thought about this myself, I don't think it's going to help
>>> either; although the direction of the conversion is important for what
>>> approach you need to take, it's not important from the point of view of
>>> what you need to know; and the Stylesheets tickets need to be triaged
>>> and assigned based on skills needed (among other things). Is there
>>> anybody who would take a TEI-to-docx ticket but refuse a docx-to-TEI
>>> ticket?
>>>
>>> Does anyone else have any opinions on the ticket categories? The
>>> list is:
>>>
>>> <https://docs.google.com/spreadsheets/d/1TugARD1amG-ZeMPl2Fo-e88VXqirH
>>> awmOs5vcSJyBb0/edit#gid=0>
>>>
>>> Cheers,
>>> Martin
>>>
>>> On 2020-05-09 7:00 a.m., Elisa Beshero-Bondar wrote:
>>> > Having worked on one of these a year ago, it made a pretty big
>>> difference to clarify the direction of the conversion because a) it
>>> wasn’t immediately clear on the ticket and b) it made a big
>>> difference in how we had to proceed. I think having the capacity to
>>> mark that might be helpful even if it isn’t always used. Just two
>>> more labels after all.
>>> >
>>> > Elisa
>>> >
>>> > Sent from my iPhone
>>> >
>>> >> On May 9, 2020, at 9:48 AM, Syd Bauman
>>> <s.bauman@northeastern.edu <mailto:s.bauman@northeastern.edu>> wrote:
>>> >>
>>> >> Certainly a system with over 50 labels can stand 2 more. But
>>> I'm not
>>> >> sure it would be helpful. The point of labelling (at least, when it
>>> >> comes to all those conversions) is to flag what kind of expertise is
>>> >> needed to address the issue. So Councilor A can look at the
>>> >> high-priority open ticket list and quickly see that ticket
>>> “output is
>>> >> invalid” is about DOCX, and think “I know absolutely nothing about
>>> >> DOCX” to himself and skip it; whereas Councilor B can look at the
>>> >> same ticket and think to herself “I’m trying to learn the XML format
>>> >> underlying DOCX, maybe I’ll give this one a try”. Doesn’t strike us
>>> >> as particularly useful to separate out whether conversion is to or
>>> >> from DOCX, it is the required expertise in DOCX that we were
>>> thinking
>>> >> should be flagged.
>>> >>
>>> >>> Typing on my phone, I see it converted my directional “from TEI”
>>> >>> suggestion into quote marks. I meant two right angle brackets for
>>> >>> that.
>>> >>>
>>> >>> I suppose we could just have, with any conversion, another bank of
>>> >>> labels (just two):
>>> >>> from TEI
>>> >>> to TEI
>>> >> _______________________________________________
>>> >> Tei-council mailing list
>>> >> Tei-council@lists.tei-c.org <mailto:Tei-council@lists.tei-c.org>
>>> >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council
>>> > _______________________________________________
>>> > Tei-council mailing list
>>> > Tei-council@lists.tei-c.org <mailto: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 <mailto:mholmes@uvic.ca>
>>> _______________________________________________
>>> Tei-council mailing list
>>> Tei-council@lists.tei-c.org <mailto:Tei-council@lists.tei-c.org>
>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council
>>>
>>>
>>> --
>>>
>>> Elisa Beshero-Bondar, PhD
>>> until April 30, 2020: Director, Center for the Digital Text |
>>> Associate Professor of English University of Pittsburgh at Greensburg
>>> | Humanities Division
>>> 150 Finoli Drive
>>> Greensburg, PA 15601 USA
>>>
>>> after July 1, 2020: 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
>>>
>>> stable e-mail address until July: ebbondar@gmail.com
>>> <mailto:ebbondar@gmail.com>
>>>
>>> Development site: https://newtfire.org <https://newtfire.org/>
>>>
>> --
>> -------------------------------------
>> Humanities Computing and Media Centre
>> University of Victoria
>> mholmes@uvic.ca
>
> --
> -------------------------------------
> Humanities Computing and Media Centre
> University of Victoria
> mholmes@uvic.ca
> _______________________________________________
> Tei-council mailing list
> Tei-council@lists.tei-c.org
> http://lists.lists.tei-c.org/mailman/listinfo/tei-council