Re: [tei-council] Whither TEI Sessions

It would be good to have an example of council working on finalising community proposals. Eg tickets for genetic edition, or for prrsonography, or changes to app content model. Or even maybe tei simple! Sent from my Honor Mobile -------- Original Message -------- Subject: Re: [tei-council] Whither TEI Sessions From: Raffaele Viglianti To: tei-council@lists.tei-c.org CC: Prompted by Elisa's suggestion, I did some digging and found two issues that I think may be representative of a slightly more elaborate process within the council: 1. A closed one: list/@type="unordered" is not recommended, but used often https://github.com/TEIC/TEI/issues/1099 (2012 - 2014) 2. And one still open: free-standing attributes -> class https://github.com/TEIC/TEI/issues/386 (2012 — ) Do you think these are useful examples? Can you think of better issues along these lines that are not overly complicated in their history? I've made a summary of these two issues on the slides that I'm putting together for the presentation (last two slides at the moment). Comments are welcome, but beware that the document is likely to change quickly: https://docs.google.com/presentation/d/1ucAIF3T7XPxcMZ-SJ3iWDEpLBZXFSWgnQmu7... Thanks! Raff On Wed, Sep 14, 2016 at 9:09 PM, Elisa wrote:

In thinking about this a little more, I wanted to share something of the intense debate and reflection we have been applying to difficult questions, and I thought of selecting one, maybe two recent cases that have really challenged us, to point out what factors tend to guide our thinking process and cause us perhaps to reopen a ticket. I think featuring a ticket in which TEI community members were/are involved might be a good case in point: "How do we deliberate?" would be my angle, I think.

What tickets might be good to feature in such a discussion?

Elisa

Typeset by hand on my iPad

...

On Sep 14, 2016, at 9:58 AM, Elisa Beshero-Bondar wrote:

Sounds like a great plan to me—though I imagine the release process will come up in conversation, and I will think about a pithy way of describing that (if possible)! :-)

Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu Development site: http://newtfire.org

...

On Sep 14, 2016, at 9:55 AM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:

I was planning on giving an overview of the council process around a ticket. The angle would be: "what happens when you think something is wrong with or missing from the TEI?" Basically describing the life of a bug report / feature request. I think that the fact that this kind of request can be submitted will be news to many. Both Elisa and I can pepper this with a more human account of our experience with this process and the council in general and conclude with some general remarks and questions form the audience. How does this sound? We could try and keep it around 10-15 minutes questions included?

I would not go into details for the release process instead, I think that's a bit less interesting to the general public and would take too much time from the hour.

On Wed, Sep 14, 2016 at 12:03 AM, Elisa Beshero-Bondar < ebbondar@gmail.com> wrote:

...

I’m okay with sharing 1) with Raff (if it’s okay with Raff), and it’ll help to have a sense of timing: How much time have we got? We can maybe each prepare a statement describing our experience of Council work—and I’m sure Raff’s is different from mine so far, so I think it’ll make for a good overview. Agreed that this is a good moment, perhaps after each of us has made a statement, to ask the audience what questions they have.

Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu mailto:ebb8@pitt.edu Development site: http://newtfire.org http://newtfire.org/

...

On Sep 13, 2016, at 9:25 PM, Hugh Cayless wrote:

We have volunteers for 1 (Raff, Elisa) and 2 (Lou). Any takers for 3? I can do it, but then someone else will need to moderate. I sympathize with James's feeling that he's already doing to much, and I share it!

As a reminder, the Google Doc is at https://docs.google.com/document/d/1E1SEMfxvhhm_ I9fAwFzOMXOl6mLy02o10aJWQt7BfhM/edit?usp=sharing

Raff and Elisa, are you comfortable sharing #1?

You'll have seen that Martin has a final draft of his white paper out. I think we'll need to address it one way of the other. If we're going to put out anything for comment to the wider TEI community, It should happen by the middle of next week, I'd say. Lou, if you wanted to make a case for the value of customization as a response to Martin's paper, I think that might be good. From my own perspective, customization wins, but maybe there are thousands of potential users out there who are put off by the complexity involved...

Raff and Elisa, it might be worth asking if there's anything people want to know about how Council works.

If I'm doing #3, I'll try to think of something... -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived