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

Git question
by James Cummings 18 Dec '15

18 Dec '15

Hiya, Is there a way to copy the changes I've made on one branch to another? Or move one branch (off another branch) to be tracking a different branch instead? (e.g. I made the 'processing-model' branch off of Lou's original lb42-pureodd branch and I want to move it to his current one.) Suggestions? Or do I have to go do all the changes again? -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

4 18

and now...
by Lou Burnard 15 Dec '15

15 Dec '15

If we're reaching consensus on the meta-question of how issues should be labelled, could we now collectively consider at least some of the urgent outstanding issues themselves? In particular, I am still waiting for an explicit green light from at least one other council member who has successfully built using the lb42-pure-odd-2 branch? Martin set up a Jenkins job to do this, but it seems to have fallen over at the penultimate hurdle, and I don;'t know enough about Jenkins to see why. If we get that, then I could maybe issue a pull request (whatever that is) and get this stuff merged in... If we're looking for jobs for new council members to cut their teeth on, I'd be delighted to propose trying to build this branch! Much more fun than fixing a tedious bit of prose. I'd also appreciate some feedback on my ticket proposing a new anyXML element... L

5 13

Reorganizing labels on GitHub
by Raffaele Viglianti 14 Dec '15

14 Dec '15

Dear all, Elli and I spent some time this morning going through the labels on the TEI repository and discussed a new, simpler, system for organizing our tickets. Here is a spreadsheet with current labels and their proposed new name: https://docs.google.com/spreadsheets/d/1VhBYft_85F6x8J0YpGvqn-ZfIHbXqk9j8QV… We propose to have 4 higher level label categories: *component* or *tool*, *type*, *priority*, and *status. * When creating a new issue, one label from each category should be chosen. For example a new ticket about a badly misguiding example for the the "div" element would probably get these labels: "Component: Core schema" "Type: Bug" "Priority: High" "Status: Needs Discussion" There are a couple of extra labels that don't fit this system: - "sf-automigrated": identifies tickets migrated from SF. We suggest to keep it. - "SIG": identifies tickets about SIG organization (maybe we need a category for less technical discussions, "meta"?). Then we have a couple of specific questions for you: - Should we keep labels specific to each chapter in the guidelines? (e.g. MS, ND, PH, etc). We think they should go away. But if we keep them we can get group them under "Component: Guidelines", e.g. "Component: Guidelines: MS". - "sf_creator-*" tickets were introduced to facilitate finding migrated tickets by their original SF creator. Since that information is also recorded in the text of the ticket, we think they should go away. Thoughts? Many thanks for your comments - after we make some decisions here, we will also check labels in the Spreadsheets repository and implement a similar system. Best, Raff

5 19

Building the PureODD branch
by Martin Holmes 13 Dec '15

13 Dec '15

Hi all (but mainly Lou and Hugh), I notice there's a pureodd branch for the Stylesheets. Should my Pure ODD P5 build on Jenkins be using that branch of the Stylesheets rather than the dev branch? Cheers, Martin

2 2

Pure ODD progress
by Lou Burnard 09 Dec '15

09 Dec '15

I am now at the stage of being able to generate web pages in the lb42-pureodd-2 branch. To get there, I have had to comment out of the makefile the two "EXTENDED" test files testp4compat.xsd and testi18n.xsd (the latter was already commented out in fact). Can anyone remember/reconstruct what these tests were intended to do? I am also now using Hugh's latest Stylesheets, so have some further comments to make on them: Firstly, what appears to be a bug: in the pureODD section, I see nothing at all inside the <content> element. e.g. in emph. This looks OK at http://teic.github.io/TEI/ref-emph.html but not in the version I have locally generated, so either the former is not up to date, or I have messed something up. Secondly, I still don't want to see class declarations inside that section Thirdly, I don't want to see element names clickable inside examples. This is not what we currently do; I find it distracting; and it's strictly speaking wrong, since example contents are not in the TEI namespace! :-) [this also doesn't happen in the github.io version]

4 13

anyone for @exclude ?
by Lou Burnard 08 Dec '15

08 Dec '15

Wandering the anyXML rabbit warren, I came upon a new side passage which may be worth considering. This is to define in pure ODD a new attribute @exclude on the <content element, the effect of which is to specify one or more elements which should be excluded from said content model. We could implement this in DTD land (if we still did DTDs) with an exclusion exception; in Relaxng of course it has to be a schematron rule. It would enable us to do two things we currently do rather obscurely (1) prevent <teix:egXML> from containing <teix:egXML> (2) prevent <s> from containing <s>. And there may well be others. Unless anyone can plausibly show that this is bonkers, I will create a ticket.

1 0

Contributors
by Hugh Cayless 06 Dec '15

06 Dec '15

Dear All, Thanks for the productive meeting earlier today. I’d said I wanted to broach the topic of keeping Contributors engaged over email, partly because it’s been a little contentious in the past and partly because I think it’s something that deserves more deliberation than we can give it in a single meeting. I’ll start by setting out how (as I understand it) things work now and then paint a picture of things as I’d like them to be. I mean the latter as something for you all to react to, so don’t hesitate to do so. I’d particularly like reactions from those of you who are new to Council. This is really going to be an ongoing conversation, I believe, and not something we can just fix. Martin has volunteered to be a champion for Contributors and I’m hoping that he and any other outgoing members who want to remain active participants will be vocal about what works and what doesn’t work for them. Council is a highly effective group that does a lot of good work, so we need to find a balance that doesn’t mess with our effectiveness and cohesiveness. The status quo: Engagement with TEI work happens via the TEI and Stylesheets repos on GitHub. Each of these has issue trackers, and there are two teams that have access to make changes to TEI, the Technical Council and "TEI Contributors". Incidentally, if the new folks will send me their github ids, I’ll add you to the Council team. The Tech Council team is for current Council members and the Contributors team is for a) former Council members who wish to remain active and b) anyone else we decide should have the ability to push directly to the TEI repo. This being GitHub, we can also take pull requests from people on neither team. Discussion of TEI stuff happens on this mailing list, on the issue trackers, in our monthly telecons, and in our Face to Face meeting. Only current Council members are on the mailing list, and people are removed as they cycle off Council. Only Council members attend the telecons and the F2F meetings, though occasionally "outside experts" are invited. Council tends to operate on consensus, though from time to time contentious issues are put to a vote. My ideal world: Contributors would be able to be as involved as they want to be in ongoing TEI development. That might include staying on or joining the mailing list, attending telecons, and even F2F meetings (though the TEI wouldn’t be able to pay for them unless they were formally invited of course). The main difference between Council Members and Contributors would be that the former have a vote when things come to a vote and would in general have more responsibility for development and maintenance. I feel that we don’t do enough to foster an active community of people who are TEI experts, and I think part of that is Council being a bit mysterious and exclusionary. It’s hard to get onto Council, especially if you’re not already part of a community of TEI users (so that you have name recognition in the elections) and people who leave have tended to just drift away (often leaving unfinished business). As I mentioned above, we’ve had a version of this discussion before, and I think mine was a minority view then, but I wanted to raise it again now to get the reactions of our incoming members and the perspectives of our outgoing members. What should we do? As you might have guessed, I have strong opinions, so I’m going to shut up for a while in the hope that a productive discussion develops without me driving it :-).

10 17

PDF and Pure ODD...
by Hugh Cayless 03 Dec '15

03 Dec '15

Tried this out, and decided to wait until we’ve got a version that’s current with the HEAD of dev. Right now it won’t build because of expired deprecated stuff that’s been fixed in the dev branch. Hugh

1 0

Telco this morning, right?
by Martin Holmes 03 Dec '15

03 Dec '15

According to my calendar, we have a telco in about 45 minutes. Is that right? Cheers, Martin

7 11

Agenda and Hangout
by Hugh Cayless 03 Dec '15

03 Dec '15

Hi all, Sorry for the delay. Moving offices is a headache. Agenda: https://docs.google.com/document/d/1f27Q0VLFN26oDNKgJ8hIXg97MF_9LeYavb1Wd9h… Hangout: https://talkgadget.google.com/hangouts/_/x3ri7iimwlh5ogr3t265zhe6n4a See you in 15 minutes!

1 0

LearnGit at Codecademy
by Raffaele Viglianti 02 Dec '15

02 Dec '15

Codecademy has just released a free interactive course for learning Git. Some council members may find it useful! It cleared some things up for me as well. (Also interesting how it has you write literature rather than code) https://www.codecademy.com/learn/learn-git Best, Raff

1 0

Telecon and updates
by Hugh Cayless 30 Nov '15

30 Nov '15

Dear All, I’ve made some progress on the Pure ODD XSLT. Please browse around http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> and be on the lookout for display bugs or things you’d like done differently. Although we had enough for a quorum in the poll for meeting times, we’d either be excluding new members, which I’d rather not do, or current members who really need to be there, so I’ve added some more dates at http://doodle.com/poll/wyuc3qiv9rkx4db6. Please update your availability when you get the chance. Whether we have a year-end release or not, I think we’re getting close to the time when we should go ahead and merge the Pure ODD branch. Thoughts? All the best, Hugh

6 7

Bugfix for Roma available for testing
by Martin Holmes 28 Nov '15

28 Nov '15

Hi all, A new Roma is here: <http://www.tei-c.org/Roma-4.18/> with my minor bugfix for the title element included, along with other things (I know not exactly what) that had been added since the last release found its way onto tei-c in 2013. If you have any experience with Roma at all, please give it a bit of a go to make sure nothing is broken. Cheers, Martin

3 4

Adding processing model to github
by James Cummings 26 Nov '15

26 Nov '15

Hiya, To the 'processing-model' branch, based on the 'lb42-pureodd' branch, I've added the specs of elements needed for the processing model, modified that for elementSpec, and added the draft prose to the TD chapter. Hurrah. (Feel free to edit and improve the prose.) I don't promise I've not broken anything and haven't yet added the cross-references to the guidelines text in the TD chapter. (But that is straightforward and I'll do so soon.) What I *haven't* added so far are the tests that Sebastian had written for the processing model because a) believe it or not I've never actually added tests to the TEI build system and so now ask for help in doing so and b) I'm not sure the tests Sebastian was doing are specifically the tests we want. In this case what we want are tests that test that our schemas are allowing/disallowing the various model* and related elements in the right place and used only in ways that they are allowed. Sebastian's tests actually test the parsing of these processing models and the output they generate. Is that what we want? Remember, what we're doing here is adding the ability for documenting processing models, not adding TEI Simple, or any particular implementation of doing things with that processing model documentation. For example, in the TEI-Simple repository there are two types of test in the build.xml ant file: The 'tests' target: https://github.com/TEIC/TEI-Simple/blob/master/build.xml#L197 validates the TEI Simple ODD against the processing-model schema, and validates various instances of TEI Simple against the TEI Simple schema. That doesn't actually test the processing model elements are used properly. The 'pm' target: https://github.com/TEIC/TEI-Simple/blob/master/build.xml#L259 first creates some TEI simple XSL from the processing model documentation in the TEI Simple ODD, then creates a variant of this from teipm-ms.odd (which was a test variant requested by Council demonstrating using it for Manuscripts), and then runs various test files through both those XSL in order to produce HTML. Again, this seems to be testing the processing of the documentation of processing models, rather than the elements. (e.g. we don't seem to test 'list' or 'person' in this way?). Could someone with more experience with the TEI test system either help me design some new tests or help me migrate some of these into the processing-model branch? Many thanks, -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Pure ODD display update
by Hugh Cayless 24 Nov '15

24 Nov '15

Dear all, I’ve been spending my time on getting the Pure ODD display working in the GLs generation. I’m getting closer, I think, though there are still some issues. Can you take a look at http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> (e.g. http://teic.github.io/TEI/ref-certainty.html <http://teic.github.io/TEI/ref-certainty.html>) and see if the Pure ODD display is what you were hoping for, and what bugs you can find. Issues I’m aware of are: RelaxNG display is displaying the result of evaluating data types rather than a link to the data type definition and "Used by" isn’t getting populated for macros and dataypes. What I’d really like to know is whether I’m on the right track or a different display is needed. This (unsurprisingly) turns out to be way more complicated than I’d hoped, and I haven’t even begun to work out how to alter the display for GLs output beyond HTML. This could take a while.

2 2

GitHub P6 label, anyone?
by Peter Stadler 24 Nov '15

24 Nov '15

I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes. Cheers Peter

5 5

brett's issues
by Lou Burnard 22 Nov '15

22 Nov '15

Apologies for the delay, but (as originally promised last week) I have now finished working through all of Brett's 24 issues with chapter PH. All but 7 of them involve minor and non-controversial corrections which I have duly made, and closed the tickets. The seven remaining however might benefit from a second look by someone with domain expertise. James? Hugh? They are really very minor points but this is a precariously organized chapter which shouldnt be deconstructed too much.

2 2

Nov/Dec Telecon
by Hugh Cayless 17 Nov '15

17 Nov '15

Dear All, I’ve been remiss in scheduling our next teleconference due to some rather unfortunate family business I won’t bore you with. The end of November is tricky anyway because of Thanksgiving in the U.S.. I’ve created a Doodle poll to try to schedule it here: http://doodle.com/poll/wyuc3qiv9rkx4db6. I’ve also been very slow to say welcome to our new members, Elisa Beshero-Bondar, Elli Mylonas, Martina Scholger, and Magdalena Turska, who I believe are now subscribed to the list. We’re very glad you’re here! We’d be very pleased if you can join in this meeting, though obviously your presence is optional. I’ll be putting together an agenda, but the main business will I think be whether to release v3.0.0 with Pure ODD before the end of the year. We’ll also have to say a sad goodbye to our departing members, Fabio, Stefanie, Martin, and Paul. I expect this will probably be the last meeting of the year, given that most of us will be out for a big chunk of December, so if we have trouble scheduling it, we can push it a bit later. All the best, Hugh

4 4

GitHub tickets and new council members
by Raffaele Viglianti 13 Nov '15

13 Nov '15

Hello, I'd like to start working on tidying up our labeling system on GitHub, as we discussed at the F2F meeting. We thought about involving one of the new members in this process - who should we pick? Should we send an open call? Have the new members already been added and are reading this email? We also talked about mentoring and I think Elli wasn't assigned a mentor because she knows the job well already - though maybe working on this could be a good way of getting her acquainted with our GitHub workflow? Raff

2 1

A decision we have to take on oxygen-tei
by Martin Holmes 11 Nov '15

11 Nov '15

We're faced with a rather difficult decision with regard to the oxygen-tei plugin. The Oxygen guys have introduced a lot of new features, especially relating to CSS usage in Author mode (as far as I understand it), and they've made a point of using jTEI as one of their examples. However, their new stuff only works on Oxygen 17.1. They've put it in a branch on oxygen-tei: <https://github.com/TEIC/oxygen-tei/tree/update_oxygen_17_1> Our plugin currently works on versions going back to 15.2. If we merge these exciting new changes, then people using older versions of Oxygen will suddenly get an update that breaks or won't install (I don't know exactly what will happen). However, if we don't update, we'll be in the rather odd situation that Oxygen's release will always be more advanced than our version of our plugin, which makes our plugin sort of pointless, since the main reason for it is to exist is to enable users to get a more up-to-the-minute version of the plugin. I'm tempted to say that it might be time to retire our "official" TEI release of the plugin entirely. We could offer a bleeding-edge preview release of the plugin, based on our dev branches, which we would us for testing and would encourage savvy users with a need to get the absolute latest-and-greatest to install; but otherwise we would just rely on Oxygen's steady release cycle to keep the majority of our users up to date. That would mean a brief lag between the time that we do a major release and Oxygen does, when users of Oxygen would have no easy way to get the latest-and-greatest P5 and Stylesheets. But it would make our lives simpler. Cheers, Martin

4 16

2.9.0 in Vault
by Hugh Cayless 09 Nov '15

09 Nov '15

Can everyone who’s able take a look at http://www.tei-c.org/Vault/P5/2.9.0/doc/tei-p5-doc/en/html/ <http://www.tei-c.org/Vault/P5/2.9.0/doc/tei-p5-doc/en/html/> It looks ok to me… Need to step away while I go pick the kids up, but should be able to resume in an hour if I don’t hear screams from anyone.

8 24

Fwd: [tei-board] submitting expenses
by Hugh Cayless 04 Nov '15

04 Nov '15

> Begin forwarded message: > > From: John Unsworth <unsworth(a)brandeis.edu> > Date: November 4, 2015 at 21:11:19 EST > To: tei-board(a)lists.tei-c.org > Cc: TEI Council <tei-council(a)lists.village.virginia.edu> > Subject: [tei-board] submitting expenses > > Hi folks, > > Here’s an updated form for submitting expenses. Kevin, could you use this to replace what’s at: > > http://www.tei-c.org/Admin/TEI_travel_form.pdf <http://www.tei-c.org/Admin/TEI_travel_form.pdf> > > Thanks, and let me know if you have questions. > > John > > > > _______________________________________________ > tei-board mailing list > tei-board(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-board

1 0

reimbursement for TEI Council in Lyon
by Syd Bauman 04 Nov '15

04 Nov '15

Am I correct that TEI-C will be reimbursing us for * travel to & from Lyon * meals from Sat 10-24 to lunch on Wed 10-28 (which we got from the conference folks, anyway) * hotel for Sat, Sun, Mon, Tue nights but not the rest of our expenses?

3 2

reminder
by Lou Burnard 04 Nov '15

04 Nov '15

Can someone remind me how I find out whether my local repo is up to date with the dev master? git status tells me if I am ahead of it, but not if I am behind. I can find out by doing a pull and seeing if something has changed, but of course by then it's too late.

2 2

Bretts comments
by Lou Burnard 04 Nov '15

04 Nov '15

I've just collected all the issues raised by Brett into a single document, and will work through it over the next day or two, applying all those (the majority) which seem to me uncontroversial typo corrections as a single modification. And will then close the related tickets.

1 0